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 v3 1/3] asm-generic: Support NO_IOPORT_MAP in pci_iomap.h
Date: Tue, 26 Jul 2022 06:25:42 +0900 [thread overview]
Message-ID: <Yt8KVnwgzHFZbtQv@antec> (raw)
In-Reply-To: <20220725171059.GA5779@bhelgaas>
On Mon, Jul 25, 2022 at 12:10:59PM -0500, Bjorn Helgaas wrote:
> On Mon, Jul 25, 2022 at 11:07:35AM +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>
>
> FWIW,
>
> Acked-by: Bjorn Helgaas <bhelgaas@google.com>
Thank you,
> I assume this will go via some other tree; let me know if otherwise.
Yes I plan to send this along with the other patches via the OpenRISC tree.
-Stafford
next prev parent reply other threads:[~2022-07-25 21:25 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-25 2:07 [PATCH v3 0/3] OpenRISC support for virt platform with PCI Stafford Horne
2022-07-25 2:07 ` [PATCH v3 1/3] asm-generic: Support NO_IOPORT_MAP in pci_iomap.h Stafford Horne
2022-07-25 17:10 ` Bjorn Helgaas
2022-07-25 21:25 ` Stafford Horne [this message]
2022-07-25 2:07 ` [PATCH v3 2/3] openrisc: Add pci bus support Stafford Horne
2022-07-29 3:37 ` Guenter Roeck
2022-07-29 5:50 ` Stafford Horne
2022-07-29 6:10 ` Guenter Roeck
2022-07-29 7:54 ` Stafford Horne
2022-07-25 2:07 ` [PATCH v3 3/3] openrisc: Add virt defconfig Stafford Horne
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=Yt8KVnwgzHFZbtQv@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).