From: Mark Brown <broonie@kernel.org>
To: Konstantin Ryabitsev <mricon@kernel.org>
Cc: tools@kernel.org
Subject: Re: kgl track-subsystem crash
Date: Sun, 10 May 2026 22:20:25 +0900 [thread overview]
Message-ID: <agCGGdZ9laXFu73L@sirena.co.uk> (raw)
In-Reply-To: <20260128-successful-pegasus-of-innovation-4cd273@lemur>
[-- Attachment #1: Type: text/plain, Size: 1759 bytes --]
Hi Konstantin,
When I say
b4 review track 20260510053939.564314-3-enelsonmoore@gmail.com
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:
Retrieving series: 20260510053939.564314-3-enelsonmoore@gmail.com
Looking up 20260510053939.564314-3-enelsonmoore@gmail.com
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 <enelsonmoore@gmail.com>
Change-ID: 20260509-mfd-twl4030-power-update-checks-for-specific-boards-to-use-t-d88ef2ad7c39
Message-ID: 20260510053939.564314-2-enelsonmoore@gmail.com
Thanks,
Mark
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2026-05-10 13:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-28 20:54 kgl track-subsystem crash Mark Brown
2026-01-28 21:11 ` Konstantin Ryabitsev
2026-05-10 13:20 ` Mark Brown [this message]
2026-05-10 13:22 ` b4/lore patch ID deduplication confusion Mark Brown
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=agCGGdZ9laXFu73L@sirena.co.uk \
--to=broonie@kernel.org \
--cc=mricon@kernel.org \
--cc=tools@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