From: Ashok Raj <ashok.raj@intel.com>
To: <tools@linux.kernel.org>
Cc: <konstantin@linuxfoundation.org>, Ashok Raj <ashok.raj@intel.com>,
"Dave Jiang" <dave.jiang@intel.com>
Subject: b4 pulling from lore has issues when new rev has some new patches
Date: Wed, 14 Jun 2023 10:44:13 -0700 [thread overview]
Message-ID: <ZIn8bVstydHNZZ9J@a4bf019067fa.jf.intel.com> (raw)
Hi Konstatin
Dave suggested to send it your way.
I'm trying to use b4 (for the first time :-)).
I tried to pull from lore.
V1: https://lore.kernel.org/r/20230603193439.502645149@linutronix.de
V2: https://lore.kernel.org/lkml/20230613115353.599087484@linutronix.de/
When i try
#b4 shazam <v2 msg id>
it reports that it imported 8 patches as expected.
I was told I could pass v1 and it would now there is a V2 and pull the
latest.
But the same with v1 msg-id, it pulls only 6 patches as opposed to 8.
It does tell there are 8, patches but only pulls 6. Maybe because there are
2 new patches in the front?
V1 only has 6, and v2 had 8 patches. GIving the v1 id only pulled 6 patches.
araj@araj-ucode:~/work/linux.git.trees$ b4 shazam -H 20230603193439.502645149@linutronix.de
Grabbing thread from lore.kernel.org/all/20230603193439.502645149@linutronix.de/t.mbox.gz
Checking for newer revisions
Grabbing search results from lore.kernel.org
Analyzing 25 messages in the thread
Partial reroll detected, reconstituting from v1
Will use the latest revision: v2
You can pick other revisions using the -vN flag
Checking attestation on all messages, may take a moment...
---
[PATCH v1->v2 1/6] x86/smp: Remove pointless wmb() from native_stop_other_cpus()
[PATCH v1->v2 2/6] x86/smp: Acquire stopping_cpu unconditionally
[PATCH v1->v2 3/6] x86/smp: Use dedicated cache-line for mwait_play_dead()
[PATCH v1->v2 4/6] x86/smp: Cure kexec() vs. mwait_play_dead() breakage
+ Reviewed-by: Ashok Raj <ashok.raj@intel.com>
+ Tested-by: Ashok Raj <ashok.raj@intel.com>
[PATCH v2 5/6] x86/smp: Split sending INIT IPI out into a helper function
[PATCH v1->v2 6/6] x86/smp: Put CPUs into INIT on shutdown if possible
+ Reviewed-by: Ashok Raj <ashok.raj@intel.com>
---
NOTE: install dkimpy for DKIM signature verification
---
Total patches: 6
---
WARNING: v2 is a partial reroll from previous revisions
Please carefully review the resulting series to ensure correctness
Pass --no-partial-reroll to disable
---
Base: attempting to guess base-commit...
Base: failed to guess base
Magic: Preparing a sparse worktree
---
Applying: x86/smp: Remove pointless wmb() from native_stop_other_cpus()
Applying: x86/smp: Acquire stopping_cpu unconditionally
Applying: x86/smp: Use dedicated cache-line for mwait_play_dead()
Applying: x86/smp: Cure kexec() vs. mwait_play_dead() breakage
Applying: x86/smp: Split sending INIT IPI out into a helper function
Applying: x86/smp: Put CPUs into INIT on shutdown if possible
---
Fetching into FETCH_HEAD
You can now merge or checkout FETCH_HEAD
e.g.: git merge --no-ff -F /home/araj/work/linux.git.trees/.git/b4-cover --edit FETCH_HEAD --signoff
--
Cheers,
Ashok
Bike Shedding: (a.k.a Parkinson's Law of Triviality)
- When the discussion on a topic is inversely proportionate to the gravity of
the topic.
next reply other threads:[~2023-06-14 17:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-14 17:44 Ashok Raj [this message]
2023-06-14 18:19 ` b4 pulling from lore has issues when new rev has some new patches Konstantin Ryabitsev
2023-06-14 18:53 ` Ashok Raj
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=ZIn8bVstydHNZZ9J@a4bf019067fa.jf.intel.com \
--to=ashok.raj@intel.com \
--cc=dave.jiang@intel.com \
--cc=konstantin@linuxfoundation.org \
--cc=tools@linux.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).