From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756082AbbCLXHf (ORCPT ); Thu, 12 Mar 2015 19:07:35 -0400 Received: from ozlabs.org ([103.22.144.67]:51159 "EHLO ozlabs.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755356AbbCLXHb (ORCPT ); Thu, 12 Mar 2015 19:07:31 -0400 Date: Fri, 13 Mar 2015 10:07:24 +1100 From: Stephen Rothwell To: Mike Turquette Cc: Stephen Boyd , "linux-kernel@vger.kernel.org" , "linux-arm-kernel@lists.infradead.org" Subject: Re: Update the clk tree for linux-next Message-ID: <20150313100724.645fdd1a@canb.auug.org.au> In-Reply-To: References: X-Mailer: Claws Mail 3.11.1 (GTK+ 2.24.25; i586-pc-linux-gnu) MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; boundary="Sig_/e/ptFIdeZTpT7lEDuGbZ.B+"; protocol="application/pgp-signature" Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org --Sig_/e/ptFIdeZTpT7lEDuGbZ.B+ Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable Hi Mike, On Thu, 12 Mar 2015 12:08:47 -0700 Mike Turquette w= rote: > > 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: >=20 > https://git.kernel.org/cgit/linux/kernel/git/clk/linux.git/ >=20 > 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: >=20 > 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.=20 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=20 * 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. --=20 Cheers, Stephen Rothwell=20 sfr@canb.auug.org.au --Sig_/e/ptFIdeZTpT7lEDuGbZ.B+ Content-Type: application/pgp-signature Content-Description: OpenPGP digital signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQIcBAEBCAAGBQJVAhwxAAoJEMDTa8Ir7ZwVtRMP/jekQJwqHp6cr3QUCbDm1E// BC7G+KIktBZK3whGWNyre5Nigg2agMPZOy9uEdSTwEc5AVMgX7LRDAtusfb+DBcp 5EoVkfWVp+W6V600+wvhxG1a95okagiI4osUBQJrgpoUQJ1MugYPBo0pc7Nc9VO1 57Nxke+B0MAmi479SPiC/iC4Z5+WZbDw3fa1FaQgPuU2p2CzAE2+QTup/miDgFXB NzKDqtRF6uFwawYA9STVvhj9dcqiod7BnzmOvw6wuMuqIH2nvr4kv7vBjORZdPzs JyexiWBaHazlqPxyEgK7VEMkHTrQbOybJ9NJc0UndxG6GUqi6s+vV5D969D5DKVt ZzrnWjaJ7FznWWBrsXypAStwbVUsPBJFCYrBLFoeYh4SQrz8HZER2NqDunVBj5hZ 1EVMyR1OqfdZ1fvKJlMojLphSX4S8Sj4UKBcp0VZJfzlTg3kaKz0rJ88uPEL2ydp K09oRxGAQBMDkmNaasAKPcqW8br35roC0U1gTnhiGdjQIF6at2gAOHN7BHPKZK1l uDZ2Jh1sI6lxID0eG8znKeuapwWX6P/o/CPZh1vBKGHZPG5ANclHIXU+10U+xpLW S+87eWhZ9FLzv3kjrqn0vv0+zV9KNLL/AmrmAwi0x+Hyd+XXBUfmSbkdq9CON5xn BCW1LT6Yr9v53yWEOTw+ =7PRK -----END PGP SIGNATURE----- --Sig_/e/ptFIdeZTpT7lEDuGbZ.B+--