From: "Arnd Bergmann" <arnd@arndb.de>
To: "Philipp Stanner" <pstanner@redhat.com>,
"kernel test robot" <lkp@intel.com>,
"Bjorn Helgaas" <helgaas@kernel.org>,
"Hanjun Guo" <guohanjun@huawei.com>, "Neil Brown" <neilb@suse.de>,
"Kent Overstreet" <kmo@daterainc.com>,
"Jakub Kicinski" <kuba@kernel.org>,
"Niklas Schnelle" <schnelle@linux.ibm.com>,
"Uladzislau Koshchanka" <koshchanka@gmail.com>,
"John Sanpe" <sanpeqf@gmail.com>,
"Dave Jiang" <dave.jiang@intel.com>,
"Masami Hiramatsu" <mhiramat@kernel.org>,
"Kees Cook" <keescook@chromium.org>,
"David Gow" <davidgow@google.com>,
"Herbert Xu" <herbert@gondor.apana.org.au>,
"Shuah Khan" <skhan@linuxfoundation.org>,
"wuqiang.matt" <wuqiang.matt@bytedance.com>,
"Yury Norov" <yury.norov@gmail.com>,
"Jason Baron" <jbaron@akamai.com>,
"Andrew Morton" <akpm@linux-foundation.org>,
"Ben Dooks" <ben.dooks@codethink.co.uk>,
"Danilo Krummrich" <dakr@redhat.com>
Cc: oe-kbuild-all@lists.linux.dev,
"Linux Memory Management List" <linux-mm@kvack.org>,
linux-kernel@vger.kernel.org, linux-pci@vger.kernel.org,
Linux-Arch <linux-arch@vger.kernel.org>,
stable@vger.kernel.org
Subject: Re: [PATCH v3 5/5] lib, pci: unify generic pci_iounmap()
Date: Tue, 05 Dec 2023 15:43:36 +0100 [thread overview]
Message-ID: <cdb1188d-7379-45e2-b2ce-ffdfb21b644a@app.fastmail.com> (raw)
In-Reply-To: <8ec1ae92206c090c79a9ab9586bd17349798b08f.camel@redhat.com>
On Tue, Dec 5, 2023, at 15:34, Philipp Stanner wrote:
> Alright, so it seems that not all architectures provide ioport_unmap().
> So I'll provide yet another preprocessor guard in v4. Wohooo, we love
> them...
Right, I think CONFIG_HAS_IOPORT_MAP is the symbol you
need to check here. There are a few targets that have inb/outb
but can't map them to __iomem pointers for some reason,
as well as more that have neither CONFIG_HAS_IOPORT nor
CONFIG_HAS_IOPORT_MAP.
Arnd
prev parent reply other threads:[~2023-12-05 14:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20231204123834.29247-6-pstanner@redhat.com>
2023-12-05 10:44 ` kernel test robot
2023-12-05 14:34 ` Philipp Stanner
2023-12-05 14:43 ` Arnd Bergmann [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=cdb1188d-7379-45e2-b2ce-ffdfb21b644a@app.fastmail.com \
--to=arnd@arndb.de \
--cc=akpm@linux-foundation.org \
--cc=ben.dooks@codethink.co.uk \
--cc=dakr@redhat.com \
--cc=dave.jiang@intel.com \
--cc=davidgow@google.com \
--cc=guohanjun@huawei.com \
--cc=helgaas@kernel.org \
--cc=herbert@gondor.apana.org.au \
--cc=jbaron@akamai.com \
--cc=keescook@chromium.org \
--cc=kmo@daterainc.com \
--cc=koshchanka@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-pci@vger.kernel.org \
--cc=lkp@intel.com \
--cc=mhiramat@kernel.org \
--cc=neilb@suse.de \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=pstanner@redhat.com \
--cc=sanpeqf@gmail.com \
--cc=schnelle@linux.ibm.com \
--cc=skhan@linuxfoundation.org \
--cc=stable@vger.kernel.org \
--cc=wuqiang.matt@bytedance.com \
--cc=yury.norov@gmail.com \
/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