From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
Cc: Prabhakar <prabhakar.csengg@gmail.com>,
users@linux.kernel.org, tools@linux.kernel.org
Subject: Multiple independent patches sent in one series
Date: Tue, 8 Nov 2022 12:08:59 +0100 [thread overview]
Message-ID: <CAMuHMdUNMCEFgPXva3zL9GW7JO=J-kTHxR8mBafnjLavyDD5Dw@mail.gmail.com> (raw)
Hi Konstantin,
I've ryn into a new oddity:
$ b4 am 20221107172953.63218-1-prabhakar.mahadev-lad.rj@bp.renesas.com
Grabbing thread from
lore.kernel.org/all/20221107172953.63218-1-prabhakar.mahadev-lad.rj%40bp.renesas.com/t.mbox.gz
Analyzing 2 messages in the thread
Assuming new revision: v2 ([PATCH] arm64: dts: renesas: r9a07g054:
Drop #address-cells from pinctrl node)
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] arm64: dts: renesas: r9a07g054: Drop #address-cells
from pinctrl node
---
✓ Signed: DKIM/gmail.com
---
Total patches: 1
---
Link: https://lore.kernel.org/r/20221107172953.63218-2-prabhakar.mahadev-lad.rj@bp.renesas.com
Base: not specified
git am
./v2_20221107_prabhakar_csengg_arm64_dts_renesas_r9a07g054_drop_address_cells_from_pinctrl_node.mbx
$ b4 am 20221107172953.63218-2-prabhakar.mahadev-lad.rj@bp.renesas.com
Grabbing thread from
lore.kernel.org/all/20221107172953.63218-2-prabhakar.mahadev-lad.rj%40bp.renesas.com/t.mbox.gz
Analyzing 2 messages in the thread
Checking attestation on all messages, may take a moment...
---
✓ [PATCH] arm64: dts: renesas: r9a07g054: Drop #address-cells
from pinctrl node
---
✓ Signed: DKIM/gmail.com
---
Total patches: 1
---
Link: https://lore.kernel.org/r/20221107172953.63218-2-prabhakar.mahadev-lad.rj@bp.renesas.com
Base: not specified
git am
./20221107_prabhakar_csengg_arm64_dts_renesas_r9a07g054_drop_address_cells_from_pinctrl_node.mbx
Running "git am -s *mbx" fails with a conflict, as the bogus v2 mbox
contains the same patch (the second).
As I first thought I did something wrong, I removed both mbox files,
and retried:
$ b4 am 20221107172953.63218-1-prabhakar.mahadev-lad.rj@bp.renesas.com
Analyzing 2 messages in the thread
Checking attestation on all messages, may take a moment...
---
✓ [PATCH] arm64: dts: renesas: r9a07g054: Drop #address-cells
from pinctrl node
---
✓ Signed: DKIM/gmail.com
---
Total patches: 1
---
Link: https://lore.kernel.org/r/20221107172953.63218-2-prabhakar.mahadev-lad.rj@bp.renesas.com
Base: not specified
git am
./20221107_prabhakar_csengg_arm64_dts_renesas_r9a07g054_drop_address_cells_from_pinctrl_node.mbx
$ b4 am 20221107172953.63218-2-prabhakar.mahadev-lad.rj@bp.renesas.com
Analyzing 2 messages in the thread
Checking attestation on all messages, may take a moment...
---
✓ [PATCH] arm64: dts: renesas: r9a07g054: Drop #address-cells
from pinctrl node
---
✓ Signed: DKIM/gmail.com
---
Total patches: 1
---
Link: https://lore.kernel.org/r/20221107172953.63218-2-prabhakar.mahadev-lad.rj@bp.renesas.com
Base: not specified
git am
./20221107_prabhakar_csengg_arm64_dts_renesas_r9a07g054_drop_address_cells_from_pinctrl_node.mbx
Now I end up with a single mbox, containing only the second patch?
Explicitly requesting the first one fails:
$ b4 am 20221107172953.63218-1-prabhakar.mahadev-lad.rj@bp.renesas.com -P_
Analyzing 2 messages in the thread
Specified msgid is not present in the series, cannot cherrypick
The issue seems to be that both patches were intended to be independent,
but were sent as a single series, or created in a single "git
format-patch" run (cfr. In-Reply-To in the second email), without "[PATCH
n/m]" sequence numbers. Which does not sound that unusual to me...
Using "b4 mbox" does give me an mbox with both patches, so I'm happy ;-)
Thanks!
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
reply other threads:[~2022-11-08 11:09 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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='CAMuHMdUNMCEFgPXva3zL9GW7JO=J-kTHxR8mBafnjLavyDD5Dw@mail.gmail.com' \
--to=geert@linux-m68k.org \
--cc=konstantin@linuxfoundation.org \
--cc=prabhakar.csengg@gmail.com \
--cc=tools@linux.kernel.org \
--cc=users@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).