public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
To: Sergio Paracuellos <sergio.paracuellos@gmail.com>
Cc: Tiezhu Yang <yangtiezhu@loongson.cn>,
	Xuefeng Li <lixuefeng@loongson.cn>,
	"open list:MIPS" <linux-mips@vger.kernel.org>,
	linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] MIPS: Do not define pci_remap_iospace() under MACH_LOONGSON64
Date: Thu, 9 Dec 2021 10:21:08 +0100	[thread overview]
Message-ID: <20211209092108.GA6981@alpha.franken.de> (raw)
In-Reply-To: <CAMhs-H-3FRV2hDKbRR=A2M2fsaengTtTBF7HxCnrtGi=fziK-A@mail.gmail.com>

On Wed, Dec 08, 2021 at 02:47:56PM +0100, Sergio Paracuellos wrote:
> > -#endif
> > -
> >  #ifdef CONFIG_PCI_DRIVERS_LEGACY
> >
> >  /*
> > diff --git a/arch/mips/pci/pci-generic.c b/arch/mips/pci/pci-generic.c
> > index 18eb8a453a86..d2d68bac3d25 100644
> > --- a/arch/mips/pci/pci-generic.c
> > +++ b/arch/mips/pci/pci-generic.c
> > @@ -47,6 +47,7 @@ void pcibios_fixup_bus(struct pci_bus *bus)
> >         pci_read_bridge_bases(bus);
> >  }
> >
> > +#ifdef pci_remap_iospace
> >  int pci_remap_iospace(const struct resource *res, phys_addr_t phys_addr)
> >  {
> >         unsigned long vaddr;
> > @@ -60,3 +61,4 @@ int pci_remap_iospace(const struct resource *res, phys_addr_t phys_addr)
> >         set_io_port_base(vaddr);
> >         return 0;
> >  }
> > +#endif
> 
> I agree this is cleaner than the CONFIG_MACH_LOONGSON64 ifdef stuff. I
> have tested this changes in mt7621 ralink platform and all seem to
> work, so in case you want to include this, feel free to add my:

thank you for testing.

> Tested-by: Sergio Paracuellos <sergio.paracuellos@gmail.com>
> Acked-by: Sergio Paracuellos <sergio.paracuellos@gmail.com>
> 
> Thomas, if you prefer me to send this as a more formal PATCH, please
> let me know.

Thiezhu already did, I'll add your tags the new patch.

Thomas.

-- 
Crap can work. Given enough thrust pigs will fly, but it's not necessarily a
good idea.                                                [ RFC1925, 2.3 ]

  reply	other threads:[~2021-12-09  9:26 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-17  9:03 [PATCH] MIPS: Do not define pci_remap_iospace() under MACH_LOONGSON64 Tiezhu Yang
2021-12-07 17:06 ` Thomas Bogendoerfer
2021-12-08 13:47   ` Sergio Paracuellos
2021-12-09  9:21     ` Thomas Bogendoerfer [this message]
2021-12-09  9:34       ` Sergio Paracuellos

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20211209092108.GA6981@alpha.franken.de \
    --to=tsbogend@alpha.franken.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mips@vger.kernel.org \
    --cc=lixuefeng@loongson.cn \
    --cc=sergio.paracuellos@gmail.com \
    --cc=yangtiezhu@loongson.cn \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox