From: Nicolas Schier <nsc@kernel.org>
To: Masahiro Yamada <masahiroy@kernel.org>
Cc: "Thomas Weißschuh" <thomas.weissschuh@linutronix.de>,
"Nathan Chancellor" <nathan@kernel.org>,
linux-kbuild@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/6] kbuild: uapi: only update hdrtest output on success
Date: Wed, 13 Aug 2025 07:46:29 +0200 [thread overview]
Message-ID: <aJwmtfA4U1jOXljP@levanger> (raw)
In-Reply-To: <CAK7LNARdhx+L6VeN2Q-gykcoWMY0MtoiNyhpY+Q9v_3tYA6o-w@mail.gmail.com>
On Wed, Aug 13, 2025 at 09:29:31AM +0900, Masahiro Yamada wrote:
> On Tue, Aug 12, 2025 at 2:33 PM Thomas Weißschuh
> <thomas.weissschuh@linutronix.de> wrote:
> >
> > If a header test fails, the output should not be updated.
> > Otherwise the next make invocation will not rerun the test.
> >
> > Also headers_check.pl should only run if the syntax check invocation
> > before succeeded.
> >
> > Add explicit sequencening.
>
> Did you test this?
>
> See scripts/Kbuild.include line 153
>
> The macro 'cmd' has "set -e".
>
> Any single error in a series of commands
> bails out.
Ah thanks! Yes, for me it works correct w/o the patch.
I was struggling with this: If I apply this patch, make no more forwards
the error code if headers_check.pl exits with error.
It's actually a bit funny:
W/o this patch, we have a command sequence like:
set -e; date ; false ; true; date
which bails out at false at stops processing subsequent commands.
Replacing the semicolons by '&&'
set -e; date && false && true; date
will prevent 'true' to be run, but the trailing 'date' will still be
executed.
Kind regards,
Nicolas
next prev parent reply other threads:[~2025-08-13 5:55 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-12 5:33 [PATCH 0/6] kbuild: uapi: various fixes Thomas Weißschuh
2025-08-12 5:33 ` [PATCH 1/6] kbuild: uapi: rerun header tests when headers_check.pl changes Thomas Weißschuh
2025-08-12 5:33 ` [PATCH 2/6] kbuild: uapi: only update hdrtest output on success Thomas Weißschuh
2025-08-13 0:29 ` Masahiro Yamada
2025-08-13 5:29 ` Thomas Weißschuh
2025-08-13 5:46 ` Nicolas Schier [this message]
2025-08-12 5:33 ` [PATCH 3/6] kbuild: uapi: fail header test on compiler warnings Thomas Weißschuh
2025-08-12 5:33 ` [PATCH 4/6] kbuild: uapi: upgrade warning on asm/types.h inclusion to error Thomas Weißschuh
2025-08-12 5:33 ` [PATCH 5/6] kbuild: uapi: upgrade check_sizetypes() warning " Thomas Weißschuh
2025-08-12 5:33 ` [PATCH 6/6] kbuild: uapi: upgrade check_declarations() " Thomas Weißschuh
2025-08-12 23:44 ` [PATCH 0/6] kbuild: uapi: various fixes Nathan Chancellor
2025-08-13 5:54 ` Nicolas Schier
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=aJwmtfA4U1jOXljP@levanger \
--to=nsc@kernel.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=masahiroy@kernel.org \
--cc=nathan@kernel.org \
--cc=thomas.weissschuh@linutronix.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