On Fri, Mar 4, 2022 at 8:18 AM Sedat Dilek <sedat.dilek@xxxxxxxxx> wrote: > > On Fri, Mar 4, 2022 at 7:47 AM Sedat Dilek <sedat.dilek@xxxxxxxxx> wrote: > > > > On Thu, Mar 3, 2022 at 6:37 PM Nathan Chancellor <nathan@xxxxxxxxxx> wrote: > > > > > > 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@xxxxxxxxxx/ > > > > -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@xxxxxxxxxx> (✓ 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@xxxxxxxxxx > > > > 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@xxxxxxxxxx; 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. > > > > > > > Hmm, the universe is not good to me... > > > > $ for i in $(seq 1 3); do b4 shazam -P _ > > 20220301145233.3689119-"$i"-arnd@xxxxxxxxxx; done > > usage: b4 [-h] [--version] [-d] [-q] {mbox,am,attest,pr,ty,diff,kr} ... > > b4: error: argument subcmd: invalid choice: 'shazam' (choose from > > 'mbox', 'am', 'attest', 'pr', 'ty', 'diff', 'kr') > > usage: b4 [-h] [--version] [-d] [-q] {mbox,am,attest,pr,ty,diff,kr} ... > > b4: error: argument subcmd: invalid choice: 'shazam' (choose from > > 'mbox', 'am', 'attest', 'pr', 'ty', 'diff', 'kr') > > usage: b4 [-h] [--version] [-d] [-q] {mbox,am,attest,pr,ty,diff,kr} ... > > b4: error: argument subcmd: invalid choice: 'shazam' (choose from > > 'mbox', 'am', 'attest', 'pr', 'ty', 'diff', 'kr') > > > > Do I need a higher version of b4 (here: v0.8.0)? > > > > Check myself... b4.git: > > > > commit 7c1d044ff1d5235e598d4c777c4abfe60e0a09a8 > > ("shazam: change default behaviour to be "apply-here"") > > > > ...is post-v0.8.0. > > > > I brutally applied the post-v0.8.0 patches stolen from b4.git over my > local distro b4 files. > > And was able to apply the triple: > > $ git log --oneline --no-merges > 5.17.0-rc6-1-amd64-clang13-lto..5.17.0-rc6-2-amd64-clang13-lto > 96a4222bdd4c (for-5.17/kbuild-std_gnu11-arndb-20220301) Kbuild: use > -std=gnu11 for KBUILD_USERCFLAGS > c4e8cef401a8 treewide: use -Wdeclaration-after-statement > 6a7cc105b238 Kbuild: move to -std=gnu11 > I was able to build and boot on bare metal. No new warnings in my build-log here after switching to -std=gnu11. Tested-by: Sedat Dilek <sedat.dilek@xxxxxxxxx> # LLVM/Clang v13.0.0 x86-64 - sed@ -
