linux-kernel - Re: linux-next: duplicate patch in the risc-v 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: Windows password security audit tool. GUI, reports in PDF.

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

Message-ID: <mhng-24fa846c-974e-452c-a593-2206e8970851@palmer-ri-x1c9>
Date: Sun, 28 Apr 2024 14:55:36 -0700 (PDT)
From: Palmer Dabbelt <palmer@...belt.com>
To: Stephen Rothwell <sfr@...b.auug.org.au>
CC: Paul Walmsley <paul@...an.com>, linux-kernel@...r.kernel.org,
  linux-next@...r.kernel.org
Subject:     Re: linux-next: duplicate patch in the risc-v tree

On Sun, 28 Apr 2024 14:35:53 PDT (-0700), Stephen Rothwell wrote:
> Hi all,
>
> The following commits are also in Linus Torvalds' tree as different
> commits (but the same patch):
>
>   bac292e849d7 ("selftests: sud_test: return correct emulated syscall value on RISC-V")
>
> This is commit
>
>   17c67ed752d6 ("selftests: sud_test: return correct emulated syscall value on RISC-V")
>
> in Linus' tree.

Sorry about that, looks like I accidentally merge this into both 
for-next and fixes.  It's a fix, though not strictly a regression (the 
selftest never worked), so maybe I just was being too careful the first 
time.

I dropped it from for-next.

>
> -- 
> Cheers,
> Stephen Rothwell