linux-kernel - Re: [PATCH v3 0/8] sched: Move a series of sysctls starting with sys/kernel/sched

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]

Date:   Sun, 20 Feb 2022 11:05:19 +1100
From:   Stephen Rothwell <sfr@...hwell.id.au>
To:     Luis Chamberlain <mcgrof@...nel.org>
Cc:     Andrew Morton <akpm@...ux-foundation.org>, peterz@...radead.org,
        Zhen Ni <nizhen@...ontech.com>,
        Stephen Rothwell <sfr@...b.auug.org.au>, mingo@...hat.com,
        juri.lelli@...hat.com, vincent.guittot@...aro.org,
        keescook@...omium.org, linux-kernel@...r.kernel.org,
        linux-fsdevel@...r.kernel.org, tangmeng <tangmeng@...ontech.com>,
        Mark Brown <broonie@...nel.org>
Subject: Re: [PATCH v3 0/8] sched: Move a series of sysctls starting with
 sys/kernel/sched_*

Hi Luis,

On Fri, 18 Feb 2022 10:21:56 -0800 Luis Chamberlain <mcgrof@...nel.org> wrote:
>
> On Thu, Feb 17, 2022 at 06:52:38PM -0800, Andrew Morton wrote:
> > On Wed, 16 Feb 2022 23:51:08 -0800 Luis Chamberlain <mcgrof@...nel.org> wrote:
> >   
> > > Are you folks OK if say Stephen adds a sysctl-next for linux-next so
> > > we can beat on these there too?  
> > 
> > Sure.  I just sent you a couple which I've collected.  
> 
> OK thanks! I've merged those into sysctl-next [0]
> 
> Stephen,
> 
> Can you add it to the set of trees you pull? I'll send a patch to add
> this to MAINTAINERS too then.
> 
> [0] git://git.kernel.org/pub/scm/linux/kernel/git/mcgrof/linux.git sysctl-next

Added from whenever the next linux-next tree gets done.

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