From: "Arnd Bergmann" <arnd@arndb.de>
To: "Linus Torvalds" <torvalds@linux-foundation.org>
Cc: Linux-Arch <linux-arch@vger.kernel.org>,
linux-kernel@vger.kernel.org,
"Niklas Schnelle" <schnelle@linux.ibm.com>,
"Palmer Dabbelt" <palmer@dabbelt.com>,
"Thomas Huth" <thuth@redhat.com>
Subject: Re: [GIT PULL] asm-generic updates for 6.4
Date: Tue, 25 Apr 2023 22:13:15 +0100 [thread overview]
Message-ID: <e15befc1-2b38-4824-8112-31f6cfe3dd41@app.fastmail.com> (raw)
In-Reply-To: <CAHk-=wiwZ4pR=nqhdzPs2kpHPhmL=Dcy_-N4Ly3nvgUJPE-9FQ@mail.gmail.com>
On Tue, Apr 25, 2023, at 20:27, Linus Torvalds wrote:
> On Mon, Apr 24, 2023 at 2:16 PM Arnd Bergmann <arnd@arndb.de> wrote:
>>
>> These are various cleanups, fixing a number of uapi header files to no
>> longer reference CONFIG_* symbols, and one patch that introduces the
>> new CONFIG_HAS_IOPORT symbol for architectures that provide working
>> inb()/outb() macros
>
> Strange. I was sure we had this, but you're right, we only had HAS_IOMEM.
>
> And then we had that HAS_IOPORT_MAP which was kind of related.
>
> Anyway, the new HAS_IOPORT looks like something we should always had
> had, I have no complaints, I was just expressing surprise that it
> wasn't already there ;)
Yes, we've discussed this over a long time, and thankfully Niklas has
a nice series that we should be able to complete soon. There was an
older series he did a few years ago that you Nak'ed because it silently
turned outb/inb operations into nops on architectures without PIO
capabilities. The coming series is what we did in response to that,
and it's clearly the right solution, it's just tedious to work out
the exact details for how to deal with individual drivers that
can work both with and without PIO support, e.g. i8250 uarts.
Arnd
next prev parent reply other threads:[~2023-04-25 21:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-24 21:15 [GIT PULL] asm-generic updates for 6.4 Arnd Bergmann
2023-04-25 19:27 ` Linus Torvalds
2023-04-25 21:13 ` Arnd Bergmann [this message]
2023-04-25 19:44 ` pr-tracker-bot
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=e15befc1-2b38-4824-8112-31f6cfe3dd41@app.fastmail.com \
--to=arnd@arndb.de \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=palmer@dabbelt.com \
--cc=schnelle@linux.ibm.com \
--cc=thuth@redhat.com \
--cc=torvalds@linux-foundation.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).