All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nicolas Schier <n.schier@avm.de>
To: Masahiro Yamada <masahiroy@kernel.org>
Cc: linux-kbuild@vger.kernel.org,
	Nathan Chancellor <nathan@kernel.org>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] kbuild: fix W= flags in the help message
Date: Mon, 22 Jan 2024 16:20:56 +0100	[thread overview]
Message-ID: <Za6H2NfODGU419hX@buildd.core.avm.de> (raw)
In-Reply-To: <20240120083255.2757978-1-masahiroy@kernel.org>

On Sat, Jan 20, 2024 at 05:32:55PM +0900, Masahiro Yamada wrote:
> W=c and W=e are supported.
> 
> Signed-off-by: Masahiro Yamada <masahiroy@kernel.org>
> ---
> 
>  Makefile | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/Makefile b/Makefile
> index f288eb2dc8fd..8c6a935c62e6 100644
> --- a/Makefile
> +++ b/Makefile
> @@ -1653,7 +1653,7 @@ help:
>  	@echo  '                       (sparse by default)'
>  	@echo  '  make C=2   [targets] Force check of all c source with $$CHECK'
>  	@echo  '  make RECORDMCOUNT_WARN=1 [targets] Warn about ignored mcount sections'
> -	@echo  '  make W=n   [targets] Enable extra build checks, n=1,2,3 where'
> +	@echo  '  make W=n   [targets] Enable extra build checks, n=1,2,3,c,e where'

In the top of scripts/Makefile.extrawarn we have kind of a duplication
of this description.  Might you want to update that too?

Reviewed-by: Nicolas Schier <nicolas@fjasle.eu>

  reply	other threads:[~2024-01-22 15:27 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-20  8:32 [PATCH] kbuild: fix W= flags in the help message Masahiro Yamada
2024-01-22 15:20 ` Nicolas Schier [this message]
2024-01-24 11:59   ` Masahiro Yamada

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=Za6H2NfODGU419hX@buildd.core.avm.de \
    --to=n.schier@avm.de \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=masahiroy@kernel.org \
    --cc=nathan@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.