Dup commits in NFC trees [Was: Time to call it quits for the maintainer summit?]

Hi Mark,

Moving the discussion to the NFC ML.

On 11/08/2026 00:47, Mark Brown wrote:
> On Mon, Aug 10, 2026 at 04:23:41PM +0100, Mark Brown wrote:
> 
>> I don't think any of that stuff is really what's causing issues with DRM
>> externally - for -next the issues I see are the constant cherry picking
>> (which I gather is also an issue for stable), and outside of that the
> 
> For some numbers on the cherry picking: I'm currently seeing 111 dups in
> drm (we also have 6 more in subtrees), out of 1739 total non-merge
> commits.  That's about 6% which seems like a lot, and they generate
> almost all of the frequent conflicts that DRM generates.  Next on the
> list is nfc with 17/35 which is a much larger percentage, and all of the
> 8 commits in the hyperv-fixes tree are duplicates.
I'm not sure whether you have been aware of this, but NFC has a new
maintainer: David [1]. I see that the new tree is listed in linux-next.

Maybe David doesn't know he is not supposed to cherry-pick commits
between his "for-linus" and "for-next" branches, but he should merge
"for-linux" into "for-next" instead.

[1]
https://lore.kernel.org/[email protected]

Cheers,
Matt
-- 
Sponsored by the NGI0 Core fund.