linux-kernel - Re: linux-next: a new pending-fixes branch

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:   Sat, 12 May 2018 10:14:19 +0300
From:   Kalle Valo <kvalo@...eaurora.org>
To:     Stephen Rothwell <sfr@...b.auug.org.au>
Cc:     Linux-kernel Mailing List <linux-kernel@...r.kernel.org>,
        Linux-Next Mailing List <linux-next@...r.kernel.org>,
        0-Day Mailing List <lkp@...ts.01.org>,
        Sasha Levin <Alexander.Levin@...rosoft.com>,
        Linus <torvalds@...ux-foundation.org>,
        Andrew Morton <akpm@...ux-foundation.org>
Subject: Re: linux-next: a new pending-fixes branch

Stephen Rothwell <sfr@...b.auug.org.au> writes:

> As an outcome of some discussion, I have added a pending-fixes branch
> to linux-next.  This branch contains Linus' tree merged with branches
> containing only fixes pending for the current release.  The branch is a
> strict subset of linux-next each day (as so rebases like linux-next
> does).
>
> It would be good if this branch could be tested by the 0-Day service
> and any other testing that people do - in the hope of sending fewer
> "fixes causing bugs" patches to Linus.
>
> There is not intention that bug fixes for Linus' tree should
> necessarily be tested in linux-next before being forwarded, but
> (especially for slightly less urgent bugs, at least) it seems like a
> good idea.
>
> I currently have 55 branches of bug fixes included.

Is there a list of branches you use available somewhere? I would like to
check that wireless-drivers is included.

-- 
Kalle Valo