linux-kernel - Re: linux-next: duplicate patch in the nolibc 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: <ZOSE1GoBrrqvBc0i@1wt.eu>
Date:   Tue, 22 Aug 2023 11:50:12 +0200
From:   Willy Tarreau <w@....eu>
To:     Christian Brauner <brauner@...nel.org>
Cc:     Shuah Khan <skhan@...uxfoundation.org>,
        "Paul E. McKenney" <paulmck@...nel.org>,
        Thomas Weißschuh <thomas@...ch.de>,
        Stephen Rothwell <sfr@...b.auug.org.au>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        Linux Next Mailing List <linux-next@...r.kernel.org>
Subject: Re: linux-next: duplicate patch in the nolibc tree

Hi,

On Mon, Aug 21, 2023 at 06:07:45PM +0200, Christian Brauner wrote:
> > We will go to our plan b of having Willy drop the patch, resend the
> > pull request to me ....
> 
> No, I didn't drop it so I appreciate it if you went with your plan.
> If I drop it now I'd be causing churn after having this sit in -next for
> over 5 weeks and I'll send a pr in the middle of this week.

I personally don't care about dropping it, but the whole process is
unclear to me and I'm unsure about what I can/have to do if at all
to help here.

Thanks,
Willy