linux-kernel - Re: linux-next: New tree for generic PM domain providers

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: <20230727105539.55227684@canb.auug.org.au>
Date:   Thu, 27 Jul 2023 10:55:39 +1000
From:   Stephen Rothwell <sfr@...b.auug.org.au>
To:     Ulf Hansson <ulf.hansson@...aro.org>
Cc:     Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        Linux PM <linux-pm@...r.kernel.org>,
        Linux ARM <linux-arm-kernel@...ts.infradead.org>,
        Arnd Bergmann <arnd@...nel.org>,
        Olof Johansson <olof@...om.net>, Nishanth Menon <nm@...com>
Subject: Re: linux-next: New tree for generic PM domain providers

Hi Ulf,

On Wed, 26 Jul 2023 13:37:34 +0200 Ulf Hansson <ulf.hansson@...aro.org> wrote:
>
> I would like to add a new tree to the linux-next integration tree. The
> new tree is intended to host drivers for the so-called generic PM
> domains providers (aka genpd providers). Most of the changes that I
> intend to collect will thus be within drivers/genpd/*, which is a new
> subsystem especially targeted for this.
> 
> These are the branches:
> git://git.kernel.org/pub/scm/linux/kernel/git/ulfh/linux-pm.git next
> git://git.kernel.org/pub/scm/linux/kernel/git/ulfh/linux-pm.git fixes
> 
> The plan is to start collecting patches beyond v6.6-rc1, but that
> isn't really clear yet.

Added 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