All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nicolas Schier <n.schier@avm.de>
To: Arnd Bergmann <arnd@kernel.org>
Cc: linux-kbuild@vger.kernel.org, Arnd Bergmann <arnd@arndb.de>,
	Masahiro Yamada <masahiroy@kernel.org>,
	Nathan Chancellor <nathan@kernel.org>,
	Nicolas Schier <nicolas@fjasle.eu>, Tony Finch <dot@dotat.at>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] [v2] scripts/unifdef: avoid constexpr keyword
Date: Wed, 10 Apr 2024 09:52:48 +0200	[thread overview]
Message-ID: <ZhZFUEFJQ-THmulp@buildd.core.avm.de> (raw)
In-Reply-To: <20240408071758.2526806-1-arnd@kernel.org>

On Mon, Apr 08, 2024 at 09:17:52AM +0200, Arnd Bergmann wrote:
> From: Arnd Bergmann <arnd@arndb.de>
> 
> Starting with c23, 'constexpr' is a keyword in C like in C++ and cannot
> be used as an identifier:
> 
> scripts/unifdef.c:206:25: error: 'constexpr' can only be used in variable declarations
>   206 | static bool             constexpr;              /* constant #if expression */
>       |                         ^
> scripts/unifdef.c:880:13: error: expected identifier or '('
>   880 |                 constexpr = false;
>       |                           ^
> 
> Rename this instance to allow changing to C23 at some point in the future.
> 
> Cc: Masahiro Yamada <masahiroy@kernel.org>
> Cc: Nathan Chancellor <nathan@kernel.org>
> Cc: Nicolas Schier <nicolas@fjasle.eu>
> Cc: linux-kbuild@vger.kernel.org
> Reviewed-By: Tony Finch <dot@dotat.at>
> Signed-off-by: Arnd Bergmann <arnd@arndb.de>
> ---
>  v2: include fixup from Tony

thanks, LGTM.

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

  reply	other threads:[~2024-04-10  7:58 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-08  7:17 [PATCH] [v2] scripts/unifdef: avoid constexpr keyword Arnd Bergmann
2024-04-10  7:52 ` Nicolas Schier [this message]
2024-04-16 12:08 ` 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=ZhZFUEFJQ-THmulp@buildd.core.avm.de \
    --to=n.schier@avm.de \
    --cc=arnd@arndb.de \
    --cc=arnd@kernel.org \
    --cc=dot@dotat.at \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=masahiroy@kernel.org \
    --cc=nathan@kernel.org \
    --cc=nicolas@fjasle.eu \
    /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.