linux-kernel - Re: Upcoming nolibc pull request for the next merge window

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <20230722130120.6e4c0eab@canb.auug.org.au>
Date:   Sat, 22 Jul 2023 13:01:20 +1000
From:   Stephen Rothwell <sfr@...b.auug.org.au>
To:     "Paul E. McKenney" <paulmck@...nel.org>
Cc:     Linus Torvalds <torvalds@...ux-foundation.org>,
        Willy Tarreau <w@....eu>,
        Shuah Khan <skhan@...uxfoundation.org>,
        Thomas Weißschuh 
        <thomas@...ch.de>, linux-kernel@...r.kernel.org
Subject: Re: Upcoming nolibc pull request for the next merge window

Hi Paul,

On Fri, 21 Jul 2023 10:39:48 -0700 "Paul E. McKenney" <paulmck@...nel.org> wrote:
>
> This is just to let you know that Willy and I are adding co-maintainers
> for nolibc.  Shuah Khan will join me as administrative maintainer,
> and will be sending the pull request to you for the next merge window.
> 
> Similarly, Thomas Weißschuh will be joining Willy as technical maintainer
> for nolibc.  With luck, this won't affect you, but in case you come across
> a nolibc issue, please reach out to Thomas as well as Willy, Shuah,
> and myself.  There will of course be an update to the MAINTAINERS file
> in the near future, but just to let you know in the meantime.

Would it make sense to add a separate nolibc branch to linux-next (and
no longer merge it into the rcu branch?  Or are there dependencies
between the two?

-- 
Cheers,
Stephen Rothwell

Content of type "application/pgp-signature" skipped