From: Nathan Chancellor <nathan@kernel.org>
To: Sedat Dilek <sedat.dilek@gmail.com>
Cc: Nick Desaulniers <ndesaulniers@google.com>,
Arnd Bergmann <arnd@kernel.org>,
Masahiro Yamada <masahiroy@kernel.org>,
Arnd Bergmann <arnd@arndb.de>,
Linus Torvalds <torvalds@linux-foundation.org>,
Marco Elver <elver@google.com>,
Jani Nikula <jani.nikula@intel.com>,
David Sterba <dsterba@suse.com>, Alex Shi <alexs@kernel.org>,
Miguel Ojeda <ojeda@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
linux-kbuild@vger.kernel.org, llvm@lists.linux.dev,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 3/3] Kbuild: use -std=gnu11 for KBUILD_USERCFLAGS
Date: Thu, 3 Mar 2022 10:37:46 -0700 [thread overview]
Message-ID: <YiD86pay2ENCebkR@dev-arch.thelio-3990X> (raw)
In-Reply-To: <CA+icZUWD_O1WTKNDTj7f+EUxx5Pf=zC53mfOBNgtj1JQwjZVAQ@mail.gmail.com>
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@kernel.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@kernel.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
next prev parent reply other threads:[~2022-03-03 17:37 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-01 14:52 [PATCH 1/3] [v3] Kbuild: move to -std=gnu11 Arnd Bergmann
2022-03-01 14:52 ` [PATCH 2/3] treewide: use -Wdeclaration-after-statement Arnd Bergmann
2022-03-01 16:54 ` Nathan Chancellor
2022-03-01 19:57 ` Nick Desaulniers
2022-03-01 20:06 ` Nick Desaulniers
2022-03-01 20:20 ` Linus Torvalds
2022-03-01 20:28 ` Nick Desaulniers
2022-03-03 0:44 ` Masahiro Yamada
2022-03-04 11:29 ` Sedat Dilek
2022-03-06 10:03 ` Sedat Dilek
2022-03-01 14:52 ` [PATCH 3/3] Kbuild: use -std=gnu11 for KBUILD_USERCFLAGS Arnd Bergmann
2022-03-01 17:00 ` Nathan Chancellor
2022-03-01 19:56 ` Nick Desaulniers
2022-03-02 22:14 ` Sedat Dilek
2022-03-02 22:54 ` Nick Desaulniers
2022-03-03 6:26 ` Sedat Dilek
2022-03-03 17:37 ` Nathan Chancellor [this message]
2022-03-04 6:47 ` Sedat Dilek
2022-03-04 7:18 ` Sedat Dilek
2022-03-04 11:12 ` Sedat Dilek
2022-03-06 10:04 ` Sedat Dilek
2022-03-01 16:53 ` [PATCH 1/3] [v3] Kbuild: move to -std=gnu11 Nathan Chancellor
2022-03-04 5:03 ` Masahiro Yamada
2022-03-04 11:24 ` Sedat Dilek
2022-03-06 10:01 ` Sedat Dilek
2022-03-04 11:37 ` Sedat Dilek
2022-03-04 16:25 ` Sedat Dilek
2022-03-06 15:31 ` Sedat Dilek
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=YiD86pay2ENCebkR@dev-arch.thelio-3990X \
--to=nathan@kernel.org \
--cc=alexs@kernel.org \
--cc=arnd@arndb.de \
--cc=arnd@kernel.org \
--cc=dsterba@suse.com \
--cc=elver@google.com \
--cc=jani.nikula@intel.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=mark.rutland@arm.com \
--cc=masahiroy@kernel.org \
--cc=ndesaulniers@google.com \
--cc=ojeda@kernel.org \
--cc=sedat.dilek@gmail.com \
--cc=torvalds@linux-foundation.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.