From: Nathan Chancellor <nathan@kernel.org>
To: "Nicolas Schier" <nsc@kernel.org>,
"Arnd Bergmann" <arnd@arndb.de>,
"Thomas Weißschuh" <thomas.weissschuh@linutronix.de>
Cc: linux-kernel@vger.kernel.org, linux-kbuild@vger.kernel.org
Subject: Re: [PATCH v2 0/5] uapi: fix remaining kconfig leaks in UAPI headers
Date: Wed, 21 Jan 2026 16:21:09 -0700 [thread overview]
Message-ID: <20260121232109.GA985170@ax162> (raw)
In-Reply-To: <aXC1sL5V9oqzT0ey@derry.ads.avm.de>
On Wed, Jan 21, 2026 at 12:17:04PM +0100, Nicolas Schier wrote:
> On Mon, Jan 12, 2026 at 08:58:28AM +0100, Thomas Weißschuh wrote:
> > A few UAPI headers still contained references to kconfig symbols.
> > Clean them all up and afterwards remove the now useless exception
> > machinery in headers_install.sh.
> >
> > Intended to be routed through the kbuild tree.
Based on [1], I am going to assume that Arnd will be picking this up via
the asm-generic tree but if you want me to take it via kbuild-next, just
let me know.
[1]: https://lore.kernel.org/20260112114744-21ac730f-68b4-4f92-9ac0-f4dc6c5bb880@linutronix.de/
Cheers,
Nathan
prev parent reply other threads:[~2026-01-21 23:21 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-12 7:58 [PATCH v2 0/5] uapi: fix remaining kconfig leaks in UAPI headers Thomas Weißschuh
2026-01-12 7:58 ` [PATCH v2 1/5] ARC: Always use SWAPE instructions and enable ARCH_USE_BUILTIN_BSWAP Thomas Weißschuh
2026-01-21 11:10 ` Nicolas Schier
2026-01-21 12:06 ` Thomas Weißschuh
2026-01-12 7:58 ` [PATCH v2 2/5] ARM: uapi: Drop PSR_ENDSTATE Thomas Weißschuh
2026-01-12 7:58 ` [PATCH v2 3/5] nios2: uapi: Remove custom asm/swab.h from UAPI Thomas Weißschuh
2026-01-12 7:58 ` [PATCH v2 4/5] x86/uapi: Stop leaking kconfig references to userspace Thomas Weißschuh
2026-01-12 7:58 ` [PATCH v2 5/5] scripts: headers_install.sh: Remove config leak ignore machinery Thomas Weißschuh
2026-01-12 10:42 ` [PATCH v2 0/5] uapi: fix remaining kconfig leaks in UAPI headers Arnd Bergmann
2026-01-12 10:49 ` Thomas Weißschuh
2026-01-21 11:17 ` Nicolas Schier
2026-01-21 23:21 ` Nathan Chancellor [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=20260121232109.GA985170@ax162 \
--to=nathan@kernel.org \
--cc=arnd@arndb.de \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nsc@kernel.org \
--cc=thomas.weissschuh@linutronix.de \
/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