Subject: Re: linux-next: duplicate patches in the tip tree

From: Peter Zijlstra <[email-masked]>
Date: Mon, 9 Dec 2024 12:08:42 +0100

On Mon, Dec 09, 2024 at 01:29:41PM +1100, Stephen Rothwell wrote:
> Hi all,
> 
> The following commits are also in the mm tree as different commits
> (but the same patches):
> 
>   96450ead1652 ("seqlock: add raw_seqcount_try_begin")
>   eb449bd96954 ("mm: convert mm_lock_seq to a proper seqcount")
> 
> These are commits
> 
>   46dbe8ab1205 ("seqlock: add raw_seqcount_try_begin")
>   5f0d64389e1f ("mm: convert mm_lock_seq to a proper seqcount")
> 
> from the mm-unstable branch of the mm tree.  The latter ones are already
> causing conflicts.

Why is this in -mm ? I agreed with Suren I'd take them through
tip/perf/core to go along with Andrii's uprobe patch that relies on
them.