On Thu, Sep 02, 2021 at 12:15:12PM +0200, Sergio Paracuellos wrote: > On Thu, Sep 2, 2021 at 11:15 AM Greg KH <gregkh@xxxxxxxxxxxxxxxxxxx> wrote: > > > > On Sun, Aug 29, 2021 at 05:14:27PM +0200, Sergio Paracuellos wrote: > > > On Fri, Aug 27, 2021 at 11:01 AM Greg KH <gregkh@xxxxxxxxxxxxxxxxxxx> wrote: > > > > > > > > On Sun, Aug 22, 2021 at 06:10:05PM +0200, Sergio Paracuellos wrote: > > > > > We have increase IO_SPACE_LIMIT for ralink platform to get PCI IO resources > > > > > properly handled using PCI core APIs. To align those changes with driver > > > > > code we have to set 'ioport_resource' end limit to IO_SPACE_LIMIT to avoid > > > > > errors. > > > > > > > > > > Signed-off-by: Sergio Paracuellos <sergio.paracuellos@xxxxxxxxx> > > > > > > > > Acked-by: Greg Kroah-Hartman <gregkh@xxxxxxxxxxxxxxxxxxx> > > > > > > Thanks. Since I am planning to move 'mt7621-pci' from staging to > > > 'drivers/pci/controller' and send v3 after the next merge window, I > > > prefer this patch to go through the staging tree. For the other two I > > > don't have any preference and it is ok for me to go through mips or > > > pci trees. So, Bjorn and Thomas is up to you if you are ok with the > > > changes. > > > > Yes, I would need acks for the other patches in the series if this is to > > come through the staging tree. > > Yes, I know it. Let's wait for Thomas and Bjorn preference for those > remaining two. I've sent my acked-by for the MIPS patch. Thomas. -- Crap can work. Given enough thrust pigs will fly, but it's not necessarily a good idea. [ RFC1925, 2.3 ]
