public inbox for linux-kbuild@vger.kernel.org
 help / color / mirror / Atom feed
From: David Disseldorp <ddiss@suse.de>
To: "Thomas Weißschuh" <thomas.weissschuh@linutronix.de>
Cc: linux-kbuild@vger.kernel.org
Subject: Re: [PATCH v2 1/2] scripts: headers_install: filter ignored configs via sed
Date: Mon, 12 Jan 2026 22:14:28 +1100	[thread overview]
Message-ID: <20260112221428.6f1ce9fe.ddiss@suse.de> (raw)
In-Reply-To: <20260112114650-7d38ec05-adfd-4f65-8605-67b051fcdeaf@linutronix.de>

Hi Thomas,

On Mon, 12 Jan 2026 11:51:41 +0100, Thomas Weißschuh wrote:

> Hi David,
> 
> On Thu, Jan 08, 2026 at 07:39:42AM +1100, David Disseldorp wrote:
> > The sed script currently prints any CONFIG_ entries carried in installed
> > headers. A subsequent shell script parses this output to check whether
> > the found CONFIG_ values should be ignored or not.
> > Drop the unnecessary sed output post-processing and instead skip over
> > ignored CONFIG_ values as part of initial processing.  
> 
> The exlusion logic is going to go away completely soon:
> https://lore.kernel.org/lkml/20260112-headers_install-config-leak-v2-0-4d8084444603@linutronix.de/
> (My series is probably going through the asm-generic tree)
> 
> Our patches will conflict.

Looks good, I'm happy to drop this patch in favour of your removals.
Patch v2 2/2 should still be relevant and apply relatively cleanly.

Thanks, David

  reply	other threads:[~2026-01-12 11:14 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-07 20:39 [PATCH v2 0/2] scripts: headers_install: avoid some reprocessing David Disseldorp
2026-01-07 20:39 ` [PATCH v2 1/2] scripts: headers_install: filter ignored configs via sed David Disseldorp
2026-01-12 10:51   ` Thomas Weißschuh
2026-01-12 11:14     ` David Disseldorp [this message]
2026-01-07 20:39 ` [PATCH v2 2/2] scripts: headers_install: avoid extra sed call for license check David Disseldorp
2026-01-21 11:34   ` Nicolas Schier
2026-01-29 12:27     ` David Disseldorp
2026-01-08  8:38 ` [PATCH v2 0/2] scripts: headers_install: avoid some reprocessing David Disseldorp

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=20260112221428.6f1ce9fe.ddiss@suse.de \
    --to=ddiss@suse.de \
    --cc=linux-kbuild@vger.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