linux-kernel - Re: linux-next: branches to be 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] [thread-next>] [day] [month] [year] [list]

Date:   Wed, 12 Jul 2023 09:28:41 +0530
From:   Vignesh Raghavendra <vigneshr@...com>
To:     Stephen Rothwell <sfr@...b.auug.org.au>,
        Linux Next Mailing List <linux-next@...r.kernel.org>
CC:     Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        Miquel Raynal <miquel.raynal@...tlin.com>
Subject: Re: linux-next: branches to be removed

+ Miquel

On 10/07/23 12:56, Stephen Rothwell wrote:
> Hi all,
> 
> I will remove the following branches from linux-next tomorrow as they have
> not been updated in over a year.  If you want your branch retained or
> reinstated, please just send me an email letting me know.
> 

[...]

>   git://git.kernel.org/pub/scm/linux/kernel/git/mtd/linux.git     cfi/next

[...]

> These branches are all empty except the last which just contains a
> commit that is the same patch of a commit in Linus' tree.
> 

Development on CFI + Hyperbus has slowed down a bit, apart from odd
fixes every now and then which I have been asking Miquel to directly
apply to mtd/fixes. I do expect odd patches/improvements over next few
months, would it be possible to keep this tree included in linux-next if
its not too much of a burden?

-- 
Regards
Vignesh