public inbox for linux-kbuild@vger.kernel.org
 help / color / mirror / Atom feed
From: David Disseldorp <ddiss@suse.de>
To: linux-kbuild@vger.kernel.org
Subject: [PATCH v2 0/2] scripts: headers_install: avoid some reprocessing
Date: Thu,  8 Jan 2026 07:39:41 +1100	[thread overview]
Message-ID: <20260107205239.6390-1-ddiss@suse.de> (raw)

scripts/headers_install.sh is relatively inefficient: it parses/modifies
headers via unifdef and three sed invocations, with sed output
post-processed via grep in one case (user-space CONFIG_ leaks).

These patches attempt to improve simplicity and efficiency by merging
two sed calls and processing user-space CONFIG_ leak filters inline.

Output is unaffected, aside from one minor error string change:
 error: $INFILE: leak CONFIG_X to user-space
becomes...
 error: $INFILE:CONFIG_X leak to user-space

License and CONFIG leak checks have been manually tested via error
injection.

Changes since v1 RFC:
- accept $INFILE prefixes from e.g. make headers_install O=build_dir
  as reported by Oliver Sang / kernel test robot
- drop extra config filter variable and do it all inline in sed

David Disseldorp (2):
      scripts: headers_install: filter ignored configs via sed
      scripts: headers_install: avoid extra sed call for license check

 scripts/headers_install.sh | 74 ++++++++++++++++----------------------
 1 file changed, 31 insertions(+), 43 deletions(-)

             reply	other threads:[~2026-01-07 20:52 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-07 20:39 David Disseldorp [this message]
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
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=20260107205239.6390-1-ddiss@suse.de \
    --to=ddiss@suse.de \
    --cc=linux-kbuild@vger.kernel.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