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

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-ID: <20241209132941.58021bb7@canb.auug.org.au>
Date: Mon, 9 Dec 2024 13:29:41 +1100
From: Stephen Rothwell <sfr@...b.auug.org.au>
To: Thomas Gleixner <tglx@...utronix.de>, Ingo Molnar <mingo@...hat.com>,
 "H. Peter Anvin" <hpa@...or.com>, Peter Zijlstra <peterz@...radead.org>,
 Andrew Morton <akpm@...ux-foundation.org>
Cc: Linux Kernel Mailing List <linux-kernel@...r.kernel.org>, Linux Next
 Mailing List <linux-next@...r.kernel.org>
Subject: linux-next: duplicate patches in the tip tree

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.

-- 
Cheers,
Stephen Rothwell

Content of type "application/pgp-signature" skipped