mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Nathan Chancellor <nathan@kernel.org>
To: Vincent Mailhol <mailhol.vincent@wanadoo.fr>
Cc: Nick Desaulniers <ndesaulniers@google.com>,
	Tom Rix <trix@redhat.com>,
	linux-kernel@vger.kernel.org, llvm@lists.linux.dev,
	Palmer Dabbelt <palmerdabbelt@google.com>,
	Arnd Bergmann <arnd@arndb.de>
Subject: Re: [PATCH] checksyscalls: ignore -Wunused-macros
Date: Sun, 24 Apr 2022 15:17:45 -0700	[thread overview]
Message-ID: <YmXMiTXEvFXZ/swU@dev-arch.thelio-3990X> (raw)
In-Reply-To: <20220422151725.1336997-1-mailhol.vincent@wanadoo.fr>

Hi Vincent,

On Sat, Apr 23, 2022 at 12:17:25AM +0900, Vincent Mailhol wrote:
> The macros defined in this file are for testing only and are purposely
> not used. When compiled with W=2, both gcc and clang yield some
> -Wunused-macros warnings. Ignore them.
> 
> Signed-off-by: Vincent Mailhol <mailhol.vincent@wanadoo.fr>

The change itself looks fine but a couple of comments:

1. Nick and I do not pick up patches, we rely on others to do so.
   Additionally, this is not really something within our domain, despite
   what get_maintainer.pl might say. This change should be sent to
   either

   Masahiro Yamada <masahiroy@kernel.org>
   linux-kbuild@vger.kernel.org

   or

   Andrew Morton <akpm@linux-foundation.org>

   so that it can be applied by one of them.

2. I am not sure that silencing warnings from W=2 is that useful, as
   they are unlikely to be real issues. Not to discourage you by any
   means but it might be more useful to focus on cleaning up warnings
   from W=1 and getting those promoted to regular build warnings.

Cheers,
Nathan

> ---
>  scripts/checksyscalls.sh | 3 ++-
>  1 file changed, 2 insertions(+), 1 deletion(-)
> 
> diff --git a/scripts/checksyscalls.sh b/scripts/checksyscalls.sh
> index 9dbab13329fa..cde15f22ec98 100755
> --- a/scripts/checksyscalls.sh
> +++ b/scripts/checksyscalls.sh
> @@ -255,6 +255,7 @@ cat << EOF
>  /* 64-bit ports never needed these, and new 32-bit ports can use statx */
>  #define __IGNORE_fstat64
>  #define __IGNORE_fstatat64
> +
>  EOF
>  }
>  
> @@ -268,4 +269,4 @@ syscall_list() {
>  }
>  
>  (ignore_list && syscall_list $(dirname $0)/../arch/x86/entry/syscalls/syscall_32.tbl) | \
> -$* -Wno-error -E -x c - > /dev/null
> +$* -Wno-error -Wno-unused-macros -E -x c - > /dev/null
> -- 
> 2.35.1
> 

  reply	other threads:[~2022-04-24 22:17 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-22 15:17 Vincent Mailhol
2022-04-24 22:17 ` Nathan Chancellor [this message]
2022-04-25  6:17   ` Vincent MAILHOL
2022-04-25  6:50     ` Arnd Bergmann
2022-04-25  7:42       ` Vincent MAILHOL
2022-04-25  8:49         ` Arnd Bergmann
2022-04-26 15:57           ` Vincent MAILHOL
2022-04-29 17:02 ` 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=YmXMiTXEvFXZ/swU@dev-arch.thelio-3990X \
    --to=nathan@kernel.org \
    --cc=arnd@arndb.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=llvm@lists.linux.dev \
    --cc=mailhol.vincent@wanadoo.fr \
    --cc=ndesaulniers@google.com \
    --cc=palmerdabbelt@google.com \
    --cc=trix@redhat.com \
    /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®