From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753067AbbCaWfn (ORCPT ); Tue, 31 Mar 2015 18:35:43 -0400 Received: from ozlabs.org ([103.22.144.67]:58737 "EHLO ozlabs.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752439AbbCaWfm (ORCPT ); Tue, 31 Mar 2015 18:35:42 -0400 Date: Wed, 1 Apr 2015 09:35:32 +1100 From: Stephen Rothwell To: Nicolas Ferre Cc: Olof Johansson , Arnd Bergmann , "Kevin Hilman" , Alexandre Belloni , Boris BREZILLON , Jean-Christophe PLAGNIOL-VILLARD , linux-arm-kernel , Linux Kernel list Subject: Re: at91 git tree in linux-next Message-ID: <20150401093532.173df258@canb.auug.org.au> In-Reply-To: <551A9FAC.2010203@atmel.com> References: <551A9FAC.2010203@atmel.com> 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_/LFwxxtDjcpMLwKGBs5gZHFP"; protocol="application/pgp-signature" Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org --Sig_/LFwxxtDjcpMLwKGBs5gZHFP Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable Hi Nicolas, On Tue, 31 Mar 2015 15:22:52 +0200 Nicolas Ferre = wrote: > > I am the maintainer for the Atmel ARM SoCs (aka at91) and I would like to > know if it's possible for you to include my git tree in linux-next. It is > usually pulled in by the ARM-soc guys (in copy). >=20 > Here it is, with the branch that you would pull: "at91-next". >=20 > git://git.kernel.org/pub/scm/linux/kernel/git/nferre/linux-at91.git at91= -next >=20 > I usually merge branches in this particular one when I send a pull-reques= t to > Arnd, Olof and Kevin so the material is usually pretty "stable". Added from today. 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_/LFwxxtDjcpMLwKGBs5gZHFP Content-Type: application/pgp-signature Content-Description: OpenPGP digital signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQIcBAEBCAAGBQJVGyE7AAoJEMDTa8Ir7ZwVPf0P+wcJwNm/bPgT7B0ufOOWY57i XHsR7WlYK3CCBO/su1Y+esB18FWtMOb0+o96xwQnmfEWCoi7T6iCD6MHcW92Ml1z fI+uOg2iXhTmN1BeQxSCxgA8e19jtL7ykTq2cAC1QRCx6kzq4AkS3pIvpyJgqerf AWF63m3WDkgmNPCO8qIpwS2vNGn3mXx1MEHJQD7eCo7qv0SOAw1FJIS348HBZ1Vl a/9BvoubwFFVwSG+lDCjTn13rKslM2mIKSJ9WlMTUlYb+22ClkPIt9uJhRVXkmaW lCf/6G82CQIBaPbJdF3i5BtrTOJCpEjOyHQIrSM6Anc9Caol0SyO3O6vHL/fVUWe 11MsSSuaLxOyoRYO4zzeMrZtTwsQ9nJV32hIqGNWmhZzLIYlsGSwVdgCIdgOpnuI 2xfQb8wIEm7ACeXPP7kGm8HwY6SX1Tr56+8rlI9wxW066w2MEA+CLLWlUCOKfa2Q s0SPWJtexOAHfjjOPt3DlGOfCMS4DNFzcBIqb4Lj0Vi07gxQpQYT83F1dzkRJ3Qu xpiyxFxUTA/t3+GnFKDqXVc57HzfwijS10ymr2DBuIjp98ZQPW8EMy25dee+2P8Y ZXQjsf7dikxGK9xkzzyUENgbFsGVKufe1g/gzJkZsZWQVCh9NLDgFF/R1IjC/ORq 1WPJakDjXKXwyykMIRet =iPAZ -----END PGP SIGNATURE----- --Sig_/LFwxxtDjcpMLwKGBs5gZHFP--