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

Peter Zijlstra
2024-12-09T11:08:46Z

[-- Attachment #1: Type: text/plain, Size: 706 bytes --]

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.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]