[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <YiD86pay2ENCebkR@dev-arch.thelio-3990X>
Date: Thu, 3 Mar 2022 10:37:46 -0700
From: Nathan Chancellor <nathan@...nel.org>
To: Sedat Dilek <sedat.dilek@...il.com>
Cc: Nick Desaulniers <ndesaulniers@...gle.com>,
Arnd Bergmann <arnd@...nel.org>,
Masahiro Yamada <masahiroy@...nel.org>,
Arnd Bergmann <arnd@...db.de>,
Linus Torvalds <torvalds@...ux-foundation.org>,
Marco Elver <elver@...gle.com>,
Jani Nikula <jani.nikula@...el.com>,
David Sterba <dsterba@...e.com>, Alex Shi <alexs@...nel.org>,
Miguel Ojeda <ojeda@...nel.org>,
Mark Rutland <mark.rutland@....com>,
linux-kbuild@...r.kernel.org, llvm@...ts.linux.dev,
linux-doc@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 3/3] Kbuild: use -std=gnu11 for KBUILD_USERCFLAGS
Hi Sedat,
On Thu, Mar 03, 2022 at 07:26:05AM +0100, Sedat Dilek wrote:
> Hey Nick!
>
> This only applies 1/3.
>
> $ b4 --version
> 0.8.0
>
> $ b4 am https://lore.kernel.org/lkml/20220301145233.3689119-1-arnd@kernel.org/
> -o - | git am -3
> Analyzing 14 messages in the thread
> Will use the latest revision: v3
> You can pick other revisions using the -vN flag
> Checking attestation on all messages, may take a moment...
> ---
> ✓ [PATCH v3 1/3] Kbuild: move to -std=gnu11
> ✓ Signed: DKIM/kernel.org
> + Reviewed-by: Nathan Chancellor <nathan@...nel.org> (✓ DKIM/kernel.org)
> ERROR: missing [2/3]!
> ERROR: missing [3/3]!
> ---
> NOTE: install patatt for end-to-end signature verification
> ---
> Total patches: 1
> ---
> WARNING: Thread incomplete!
> Link: https://lore.kernel.org/r/20220301145233.3689119-1-arnd@kernel.org
> Base: not specified
> Wende an: Kbuild: move to -std=gnu11
It looks like the threading somehow got broken, likely due to the [v3]
on the first patch and not the second or third:
This worked for me on v5.17-rc6:
$ for i in $(seq 1 3); do b4 shazam -P _ 20220301145233.3689119-"$i"-arnd@...nel.org; done
"b4 shazam" is the equivalent of "b4 am -o - ... | git am" and the
"-P _" tells b4 to only fetch that exact message ID, not the whole
thread.
Cheers,
Nathan
Powered by blists - more mailing lists