b4/lore patch ID deduplication confusion

Mark Brown <[email protected]>
Newsgroups org.kernel.linux.tools
Message-ID <[email protected]>
On Sun, May 10, 2026 at 10:20:25PM +0900, Mark Brown wrote:
> Hi Konstantin,
> 
> When I say
> 
>   b4 review track [email protected]
> 
> things get very confused and b4 tracks a different patch with no way to
> override what it's doing, I think some combination of b4 and lore's
> patch ID stuff is ignoring filenames and therefore faceplanting rather
> badly:

The same thing is happening with b4 am so I'm guessing this is on the
lore side (also fixed the subject line, sorry).

> 
> Retrieving series: [email protected]
> Looking up [email protected]
> WARNING: duplicate messages found at index 1
>    Subject 1: ARM: orion5x: update board check in mss2_pci_init() to use the DT
>    Subject 2: ASoC: ti: omap3pandora: update board check to use DT compatible
>   2 is not a reply... assume additional patch
> Assuming new revision: v2 ([PATCH v2] mfd: twl4030-power: update checks for specific boards to use the DT)
> Checking for newer revisions
> Grabbing search results from lore.kernel.org
> Checking for older revisions
> Grabbing search results from lore.kernel.org
> Server returned an error.
> WARNING: duplicate messages found at index 1
>    Subject 1: ARM: orion5x: update board check in mss2_pci_init() to use the DT
>    Subject 2: ASoC: ti: omap3pandora: update board check to use DT compatible
>   2 is not a reply... assume additional patch
> Assuming new revision: v2 ([PATCH v2] mfd: twl4030-power: update checks for specific boards to use the DT)
> No change-id found, generated: 20260509-mfd-twl4030-power-update-checks-for-specific-boards-to-use-t-d88ef2ad7c39
> Tracked series: mfd: twl4030-power: update checks for specific boards to use the DT v2 (1 patches)
>   From: Ethan Nelson-Moore <[email protected]>
>   Change-ID: 20260509-mfd-twl4030-power-update-checks-for-specific-boards-to-use-t-d88ef2ad7c39
>   Message-ID: [email protected]
> 
> Thanks,
> Mark
signature.asc (application/pgp-signature, 488 B)
-----BEGIN PGP SIGNATURE-----

iQEzBAABCgAdFiEEreZoqmdXGLWf4p/qJNaLcl1Uh9AFAmoAhqoACgkQJNaLcl1U
h9DBWQf+O7vuo7qAuGdRS8oXThwCSCN3MBCfQvQVuzAszVLRX5X/nlkYAvdUk1gj
mGDCZKOqQhI56HFdieB1Du/nD0Oefq37NRVswIXzy0Tnam/c3i2Ieogq2LNu8m3a
CrXeSJF0J1/r+hHfaP/7WgdKeQZpXARzRnj8JZuMjlhptIRkcKbq9Liobv5vIpbp
rBZsHaMvia4f+C9UdqVC9h0kbUO1devnTm+oXsGc5Y8Ej38oxkW57ClzxvSp+mlw
GY1TsQFniYNquYRLaLVVRKo2Diu8he2hKXhOFIXQKizLf9pUo6aWe9lqKwLlL+Hk
orXFiPe9b8uy3hWHXLFE4KzWYavPKg==
=mz3g
-----END PGP SIGNATURE-----
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.