From: Nathan Chancellor <nathan@kernel.org>
To: kees@kernel.org, Jaihind Yadav <jaihindy@qti.qualcomm.com>
Cc: nsc@kernel.org, linux-hardening@vger.kernel.org,
linux-kbuild@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-modules@vger.kernel.org
Subject: Re: [PATCH v3] scripts/gcc-plugins: suppress recorded GCC switches for extmod builds
Date: Tue, 01 Sep 2026 16:13:12 -0700 [thread overview]
Message-ID: <178830439251.3086667.14013595113820949472.b4-ty@b4> (raw)
In-Reply-To: <20260820060116.786173-1-jaihindy@qti.qualcomm.com>
On Thu, 20 Aug 2026 11:31:16 +0530, Jaihind Yadav wrote:
> scripts/gcc-plugins: suppress recorded GCC switches for extmod builds
Applied to
https://git.kernel.org/pub/scm/linux/kernel/git/kbuild/linux.git kbuild-next-unstable
Thanks!
[1/1] scripts/gcc-plugins: suppress recorded GCC switches for extmod builds
https://git.kernel.org/kbuild/c/51794b107d54b
Please look out for regression or issue reports or other follow up
comments, as they may result in the patch/series getting dropped or
reverted. Patches applied to an "unstable" branch are accepted pending
wider testing in -next and any post-commit review; they will generally
be moved to the main branch in a week if no issues are found.
Best regards,
--
Cheers,
Nathan
next prev parent reply other threads:[~2026-09-01 23:13 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20260803181217.GB1067866@ax162>
[not found] ` <20260813082949.1622045-1-jaihindy@qti.qualcomm.com>
[not found] ` <202608130942.4FFA5AAB9D@keescook>
[not found] ` <CY5PR02MB8991D4B48F9391D1849B2CFCE2DA2@CY5PR02MB8991.namprd02.prod.outlook.com>
2026-08-14 18:23 ` [PATCH v2] kstack_erase: suppress -grecord-gcc-switches for external module builds Nicolas Schier
2026-08-14 22:45 ` Nathan Chancellor
2026-08-16 8:11 ` Jaihind Yadav
2026-08-17 18:51 ` Nathan Chancellor
2026-08-19 5:03 ` Jaihind Yadav
2026-08-20 6:01 ` [PATCH v3] scripts/gcc-plugins: suppress recorded GCC switches for extmod builds Jaihind Yadav
2026-08-28 15:13 ` Nicolas Schier
2026-09-01 21:11 ` Kees Cook
2026-09-01 23:13 ` Nathan Chancellor [this message]
2026-09-02 5:21 ` Jaihind Yadav
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=178830439251.3086667.14013595113820949472.b4-ty@b4 \
--to=nathan@kernel.org \
--cc=jaihindy@qti.qualcomm.com \
--cc=kees@kernel.org \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-modules@vger.kernel.org \
--cc=nsc@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