linux-kernel - Re: [PATCH 0/1] kgdb: Handle HAS

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-Id: <3dd44bdf-7950-4822-ac7c-97fc1bdcf5d7@app.fastmail.com>
Date: Wed, 03 Apr 2024 22:10:48 +0200
From: "Arnd Bergmann" <arnd@...nel.org>
To: "Andrew Morton" <akpm@...ux-foundation.org>,
 "Niklas Schnelle" <schnelle@...ux.ibm.com>
Cc: "Heiko Carstens" <hca@...ux.ibm.com>, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 0/1] kgdb: Handle HAS_IOPORT dependencies

On Wed, Apr 3, 2024, at 22:02, Andrew Morton wrote:
> On Wed,  3 Apr 2024 15:25:46 +0200 Niklas Schnelle  <schnelle@...ux.ibm.com> wrote:
>> 
>> 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].
>
> 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?

Correct, there is just one last patch that depends on everything
else going in first.

      Arnd