From: Andrew Morton <akpm@linux-foundation.org>
To: Niklas Schnelle <schnelle@linux.ibm.com>
Cc: Arnd Bergmann <arnd@kernel.org>,
Heiko Carstens <hca@linux.ibm.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/1] kgdb: Handle HAS_IOPORT dependencies
Date: Wed, 3 Apr 2024 13:02:43 -0700 [thread overview]
Message-ID: <20240403130243.41a65a767f03fd7c4d8dabf8@linux-foundation.org> (raw)
In-Reply-To: <20240403132547.762429-1-schnelle@linux.ibm.com>
On Wed, 3 Apr 2024 15:25:46 +0200 Niklas Schnelle <schnelle@linux.ibm.com> wrote:
> Hi Andrew,
>
> This is a follow up in my ongoing effort of making inb()/outb() and
> similar I/O port accessors compile-time optional. Previously I sent this
> as a treewide series titled "treewide: Remove I/O port accessors for
> HAS_IOPORT=n" with the latest being its 5th version[0]. With a significant
> subset of patches merged I've changed over to per-subsystem series. These
> series are stand alone and should be merged via the relevant tree such
> that with all subsystems complete we can follow this up with the final
> patch that will make the I/O port accessors compile-time optional.
>
> The current state of the full series with changes to the remaining
> subsystems and the aforementioned final patch can be found for your
> convenience on my git.kernel.org tree in the has_ioport_v6 branch[1] with
> signed tags. As for compile-time vs runtime see Linus' reply to my first
> attempt[2].
Thanks.
I'm not fully understanding the timing. Am I correct in believing that the 44
other patches are not dependent upon this one? And that this patch is not
dependent upon those 44?
next prev parent reply other threads:[~2024-04-03 20:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-03 13:25 [PATCH 0/1] kgdb: Handle HAS_IOPORT dependencies Niklas Schnelle
2024-04-03 13:25 ` [PATCH 1/1] kgdb: add HAS_IOPORT dependency Niklas Schnelle
2024-04-03 20:02 ` Andrew Morton [this message]
2024-04-03 20:10 ` [PATCH 0/1] kgdb: Handle HAS_IOPORT dependencies Arnd Bergmann
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=20240403130243.41a65a767f03fd7c4d8dabf8@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=arnd@kernel.org \
--cc=hca@linux.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=schnelle@linux.ibm.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