[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20171105131022.401a880a@canb.auug.org.au>
Date: Sun, 5 Nov 2017 13:10:22 +1100
From: Stephen Rothwell <sfr@...b.auug.org.au>
To: Shuah Khan <shuahkh@....samsung.com>
Cc: "Rafael J. Wysocki" <rafael@...nel.org>,
linux-kernel@...r.kernel.org, linux-pm@...r.kernel.org
Subject: Re: Request to add cpupower git to linux-next
Hi Shuah,
On Fri, 3 Nov 2017 10:26:58 -0600 Shuah Khan <shuahkh@....samsung.com> wrote:
>
> Could you please add
>
> git://git.kernel.org/pub/scm/linux/kernel/git/shuah/linux.git cpupower
> to linux-next
>
> I will be sending pull requests to Rafael Wysocki for cpupower to be
> included in linux-pm starting soon for 4.15 release.
Added from tomorrow.
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
Powered by blists - more mailing lists