From: Stafford Horne <shorne@gmail.com>
To: Bjorn Helgaas <helgaas@kernel.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
Arnd Bergmann <arnd@arndb.de>,
Bjorn Helgaas <bhelgaas@google.com>,
linux-pci@vger.kernel.org, linux-arch@vger.kernel.org
Subject: Re: [PATCH] asm-generic: Support NO_IOPORT_MAP in pci_iomap.h
Date: Sat, 30 Jul 2022 05:44:36 +0900 [thread overview]
Message-ID: <YuRGtBef7KMTqg0i@antec> (raw)
In-Reply-To: <20220729170449.GA463615@bhelgaas>
On Fri, Jul 29, 2022 at 12:04:49PM -0500, Bjorn Helgaas wrote:
> On Sat, Jul 23, 2022 at 06:22:48AM +0900, Stafford Horne wrote:
> > When building OpenRISC PCI which has no ioport_map we get the following build
> > error.
> >
> > lib/pci_iomap.c: In function 'pci_iomap_range':
> > CC drivers/i2c/i2c-core-base.o
> > ./include/asm-generic/pci_iomap.h:29:41: error: implicit declaration of function 'ioport_map'; did you mean 'ioremap'? [-Werror=implicit-function-declaration]
> > 29 | #define __pci_ioport_map(dev, port, nr) ioport_map((port), (nr))
> > | ^~~~~~~~~~
> > lib/pci_iomap.c:44:24: note: in expansion of macro '__pci_ioport_map'
> > 44 | return __pci_ioport_map(dev, start, len);
> > | ^~~~~~~~~~~~~~~~
> >
> > This patch adds a NULL definition of __pci_ioport_map for architetures
> > which do not support ioport_map.
> >
> > Suggested-by: Arnd Bergmann <arnd@arndb.de>
> > Signed-off-by: Stafford Horne <shorne@gmail.com>
>
> Appended to my pci/header-cleanup-immutable branch for v5.20, thanks!
Thanks, I did have this in the PCI series on my OpenRISC fot-next branch. I
will just rebase that on the pci/header-cleanup-immutable branch to avoid having
the patch there two times.
Also, your updated subject on the commit is much better.
-Stafford
> > ---
> > The Kconfig I am using to test this is here:
> > https://github.com/stffrdhrn/linux/commits/or1k-virt-4
> >
> > include/asm-generic/pci_iomap.h | 2 ++
> > 1 file changed, 2 insertions(+)
> >
> > diff --git a/include/asm-generic/pci_iomap.h b/include/asm-generic/pci_iomap.h
> > index 5a2f9bf53384..8fbb0a55545d 100644
> > --- a/include/asm-generic/pci_iomap.h
> > +++ b/include/asm-generic/pci_iomap.h
> > @@ -25,6 +25,8 @@ extern void pci_iounmap(struct pci_dev *dev, void __iomem *);
> > #ifdef CONFIG_NO_GENERIC_PCI_IOPORT_MAP
> > extern void __iomem *__pci_ioport_map(struct pci_dev *dev, unsigned long port,
> > unsigned int nr);
> > +#elif !defined(CONFIG_HAS_IOPORT_MAP)
> > +#define __pci_ioport_map(dev, port, nr) NULL
> > #else
> > #define __pci_ioport_map(dev, port, nr) ioport_map((port), (nr))
> > #endif
> > --
> > 2.36.1
> >
prev parent reply other threads:[~2022-07-29 20:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-22 21:22 [PATCH] asm-generic: Support NO_IOPORT_MAP in pci_iomap.h Stafford Horne
2022-07-29 17:04 ` Bjorn Helgaas
2022-07-29 20:44 ` Stafford Horne [this message]
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=YuRGtBef7KMTqg0i@antec \
--to=shorne@gmail.com \
--cc=arnd@arndb.de \
--cc=bhelgaas@google.com \
--cc=helgaas@kernel.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).