linux-kernel - Re: linux-next: trees being removed

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: <20250306084758.12c73d0c@canb.auug.org.au>
Date: Thu, 6 Mar 2025 08:47:58 +1100
From: Stephen Rothwell <sfr@...b.auug.org.au>
To: Nick Terrell <terrelln@...a.com>
Cc: Linux Next Mailing List <linux-next@...r.kernel.org>, Linux Kernel
 Mailing List <linux-kernel@...r.kernel.org>, Dan Williams
 <dan.j.williams@...el.com>, "Gustavo A. R. Silva" <gustavo@...eddedor.com>,
 Jeff Layton <jlayton@...nel.org>, Jeremy Kerr <jk@...abs.org>, Joel Stanley
 <joel@....id.au>, Kent Overstreet <kent.overstreet@...ux.dev>, Linus
 Walleij <linus.walleij@...aro.org>, Vineet Gupta <vgupta@...nel.org>, David
 Sterba <dsterba@...e.com>
Subject: Re: linux-next: trees being removed

Hi Nick,

On Wed, 5 Mar 2025 21:34:18 +0000 Nick Terrell <terrelln@...a.com> wrote:
>
> > On Wed, 12 Feb 2025 09:56:32 +1100 Stephen Rothwell <sfr@...b.auug.org.au> wrote:  
> >> 
> >> Tree Last commit date
> >>  URL
> >>  comits (if any)
> >> ---- ----------------
> >> zstd 2023-11-20 14:49:34 -0800
> >>  https://github.com/terrelln/linux.git#zstd-next  
> 
> Could I get the (`zstd`, `https://github.com/terrelln/linux.git#zstd-next`) tree back please?
> 
> We just released zstd-1.5.7 upstream, and I'm working on updating the kernel to this
> version. David Sterba alerted me to this [1].
> 
> Thanks & sorry for the churn,

No worries, it is back from today.

Thanks for adding your subsystem tree as a participant of linux-next.  As
you may know, this is not a judgement of your code.  The purpose of
linux-next is for integration testing and to lower the impact of
conflicts between subsystems in the next merge window. 

You will need to ensure that the patches/commits in your tree/series have
been:
     * submitted under GPL v2 (or later) and include the Contributor's
        Signed-off-by,
     * posted to the relevant mailing list,
     * reviewed by you (or another maintainer of your subsystem tree),
     * successfully unit tested, and 
     * destined for the current or next Linux merge window.

Basically, this should be just what you would send to Linus (or ask him
to fetch).  It is allowed to be rebased if you deem it necessary.

-- 
Cheers,
Stephen Rothwell 
sfr@...b.auug.org.au

Content of type "application/pgp-signature" skipped