From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org [172.17.192.35]) by mail.linuxfoundation.org (Postfix) with ESMTPS id 2A730D07 for ; Wed, 9 May 2018 21:51:54 +0000 (UTC) Received: from ozlabs.org (ozlabs.org [203.11.71.1]) by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 4B611681 for ; Wed, 9 May 2018 21:51:53 +0000 (UTC) Date: Thu, 10 May 2018 07:51:49 +1000 From: Stephen Rothwell To: Dan Williams Message-ID: <20180510075149.57c3034a@canb.auug.org.au> In-Reply-To: References: <20180502194632.GB18390@sasha-vm> <20180503020550.GP2714@sirena.org.uk> <20180503031000.GC29205@thunk.org> <0276fcda-0385-8f22-dbdb-e063f7ed8bbe@roeck-us.net> <20180503224217.GR2714@sirena.org.uk> <20180503230905.GA98604@atomide.com> <20180509084440.GW13402@sirena.org.uk> <20180509090346.GY13402@sirena.org.uk> <20180509204727.7ff38021@canb.auug.org.au> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; boundary="Sig_/KyNS2/d6MOKSvSK194yyHAA"; protocol="application/pgp-signature" Cc: "ksummit-discuss@lists.linuxfoundation.org" , linux-nvdimm , Greg KH , "linux-kernel@vger.kernel.org" , "w@1wt.eu" Subject: Re: [Ksummit-discuss] bug-introducing patches List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , --Sig_/KyNS2/d6MOKSvSK194yyHAA Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable Hi Dan, On Wed, 9 May 2018 09:04:31 -0700 Dan Williams w= rote: > > Please add: >=20 > git://git.kernel.org/pub/scm/linux/kernel/git/nvdimm/nvdimm.git > libnvdimm-fixes >=20 > We currently merge this into libnvdimm-for-next for -next coverage, > and resolve any conflicts vs new development. Do you want to see those > conflicts? Otherwise I would recommend only pulling libnvdimm-for-next > for -next and libnvdimm-fixes for this new -next-fixes effort. The conflicts are usually fine (but if you do the merges, I won't see them - which is even better :-)). I like to have the fixes branches in linux-next so that noone has to worry about probelsm in Linus' tree that have pending fixes already. 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.=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_/KyNS2/d6MOKSvSK194yyHAA Content-Type: application/pgp-signature Content-Description: OpenPGP digital signature -----BEGIN PGP SIGNATURE----- iQEzBAEBCAAdFiEENIC96giZ81tWdLgKAVBC80lX0GwFAlrzbXUACgkQAVBC80lX 0GwzAgf/TxQI4NrJdZFoI7Y//UmYxwfeeSgkLWVg4aKZOOJPzX93qoqf+uLItfGn RGKO51U4QQ+CFurwUXGuLOnjTKB2/ehyZYjDxj/UVsp709bDd+1A0vctYf8coYvn dmPL+CpX9cLwl8w+FpP1ehy9wxDHlZich7Jh8fspSC34NZ/CuVSFn4e2QpTaq9zb rJ2OaZ6Zy/t0+y/dFWtJD+o10Kp6aK4SXdF3o9sBEc9hp/nEBipVBK0BFnSYRbfo 4xfFh26jpvRLRV64JyK8kzsOJmn6mQRktV6xEEoeN9dDRH1XawwJVSAh7Rb4Xhri /9UyA5kh8GCOqE8mQOuie/iO3IGFow== =Sccc -----END PGP SIGNATURE----- --Sig_/KyNS2/d6MOKSvSK194yyHAA--