From: Nicolas Schier <nsc@kernel.org>
To: Nathan Chancellor <nathan@kernel.org>
Cc: Nicolas Schier <nsc@kernel.org>,
Rasmus Villemoes <linux@rasmusvillemoes.dk>,
Arnd Bergmann <arnd@arndb.de>,
Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
Maxime Ripard <mripard@kernel.org>,
Thomas Zimmermann <tzimmermann@suse.de>,
David Airlie <airlied@gmail.com>, Simona Vetter <simona@ffwll.ch>,
linux-kbuild@vger.kernel.org, linux-kernel@vger.kernel.org,
dri-devel@lists.freedesktop.org
Subject: Re: [PATCH] kbuild: Rename Makefile.extrawarn to Makefile.warn
Date: Mon, 27 Oct 2025 22:59:28 +0100 [thread overview]
Message-ID: <176160225481.2834943.9284627955715309233.b4-ty@kernel.org> (raw)
In-Reply-To: <20251023-rename-scripts-makefile-extrawarn-v1-1-8f7531542169@kernel.org>
On Thu, 23 Oct 2025 22:01:36 +0200, Nathan Chancellor wrote:
> Since commit e88ca24319e4 ("kbuild: consolidate warning flags in
> scripts/Makefile.extrawarn"), scripts/Makefile.extrawarn contains all
> warnings for the main kernel build, not just warnings enabled by the
> values for W=. Rename it to scripts/Makefile.warn to make it clearer
> that this Makefile is where all Kbuild warning handling should exist.
>
>
> [...]
Applied to kbuild-next, thanks!
[1/1] kbuild: Rename Makefile.extrawarn to Makefile.warn
https://git.kernel.org/kbuild/c/24722b62
Please note that commit hashes might change in case of issues with
kbuild-next.
Best regards,
--
Nicolas
prev parent reply other threads:[~2025-10-27 22:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-23 20:01 Nathan Chancellor
2025-10-23 20:03 ` Arnd Bergmann
2025-10-27 21:59 ` Nicolas Schier [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=176160225481.2834943.9284627955715309233.b4-ty@kernel.org \
--to=nsc@kernel.org \
--cc=airlied@gmail.com \
--cc=arnd@arndb.de \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@rasmusvillemoes.dk \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mripard@kernel.org \
--cc=nathan@kernel.org \
--cc=simona@ffwll.ch \
--cc=tzimmermann@suse.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
all inboxes | Powered by JetHome®