linux-kernel - Re: Update the clk tree for linux-next

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:	Fri, 13 Mar 2015 10:07:24 +1100
From:	Stephen Rothwell <sfr@...b.auug.org.au>
To:	Mike Turquette <mturquette@...aro.org>
Cc:	Stephen Boyd <sboyd@...eaurora.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	"linux-arm-kernel@...ts.infradead.org" 
	<linux-arm-kernel@...ts.infradead.org>
Subject: Re: Update the clk tree for linux-next

Hi Mike,

On Thu, 12 Mar 2015 12:08:47 -0700 Mike Turquette <mturquette@...aro.org> wrote:
>
> Stephen Boyd has kindly agreed to co-maintain the clk framework with
> me and we have shared commit access to a new git tree at kernel.org:
> 
> https://git.kernel.org/cgit/linux/kernel/git/clk/linux.git/
> 
> Can you update linux-next to pull from this tree instead of the
> git.linaro.org address? They are currently mirrors but the
> git.kernel.org tree is the canonical tree from this day forth. The
> full path to pull from is:
> 
> git://git.kernel.org/pub/scm/linux/kernel/git/clk/linux.git clk-next

OK, I have updated to use this and added Stephen as a contact for the
tree.  It is not quite in sync with the old tree at the moment.

For Stephen's benefit:

Thanks for adding your subsystem tree as a participant of linux-next.  As
you may know, this is not a judgment 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