Multiple independent patches sent in one series

Multiple independent patches sent in one series

[Geert Uytterhoeven]

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