From mboxrd@z Thu Jan 1 00:00:00 1970 From: Stephen Rothwell Subject: Re: generic-iomap tree for linux-next Date: Fri, 8 Nov 2019 15:52:48 +1100 Message-ID: <20191108155248.0a32a03a@canb.auug.org.au> References: <20191029064834.23438-1-hch@lst.de> <20191107204743.GA22863@lst.de> <20191108132000.3e7bd5b8@canb.auug.org.au> Mime-Version: 1.0 Content-Type: multipart/signed; boundary="Sig_/tVtmaodFaJa/ooywirx=fo/"; protocol="application/pgp-signature"; micalg=pgp-sha256 Return-path: In-Reply-To: <20191108132000.3e7bd5b8@canb.auug.org.au> Sender: linux-kernel-owner@vger.kernel.org To: Christoph Hellwig Cc: Arnd Bergmann , Guo Ren , Michal Simek , Greentime Hu , Vincent Chen , Guan Xuetao , x86@kernel.org, linux-arch@vger.kernel.org, linux-s390@vger.kernel.org, linux-ia64@vger.kernel.org, linux-parisc@vger.kernel.org, linux-sh@vger.kernel.org, linux-hexagon@vger.kernel.org, linux-xtensa@linux-xtensa.org, linux-mips@vger.kernel.org, linux-kernel@vger.kernel.org, linux-m68k@lists.linux-m68k.org, openrisc@lists.librecores.org, linux-mtd@lists.infradead.org, linux-alpha@vger.kernel.org, sparclinux@vger.kernel.org, nios2-dev@lists.rocketboards.org, linux-riscv@lists.infradead.org, linux-snps-arc@lists.infradead.org, linux-arm-kernel@lists.infradead.org List-Id: linux-arch.vger.kernel.org --Sig_/tVtmaodFaJa/ooywirx=fo/ Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable Hi Christoph, On Fri, 8 Nov 2019 13:20:00 +1100 Stephen Rothwell w= rote: > > On Thu, 7 Nov 2019 21:47:43 +0100 Christoph Hellwig wrote: > > > > can you add the generic-ioremap tree: > >=20 > > git://git.infradead.org/users/hch/ioremap.git > >=20 > > to linux-next? =20 >=20 > I assume you mean the for-next branch? With that assumption, 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_/tVtmaodFaJa/ooywirx=fo/ Content-Type: application/pgp-signature Content-Description: OpenPGP digital signature -----BEGIN PGP SIGNATURE----- iQEzBAEBCAAdFiEENIC96giZ81tWdLgKAVBC80lX0GwFAl3E9KAACgkQAVBC80lX 0GzmWwf+Klgi0tTyTa+t0RWIsOgTgCRRshcd2R+zC2TAQiqpOvNWxiNkHSOO6rPt AIwk9/iB+0v8JHEaYe+JqqmAtlRJjfMKtLkGBCB8WLQ/Sw+V+BW+2kZfZbMDL47C Q2NA/MqqCVxs38kWlJA+gd3xF1FJLjYYuHlhaksjzlHUVGVcCxeXRrd521DYPcwm 9ZzSoL0488rxdiISFluZ44y3nKSgX3Ye5J4DnymJod7hsctYKZvWL+GxoizD+i6m HgzcYw5CxoMeQcS9WgBNCafeABW7i7w3jfCsmBjTNWCuUkE+Pruoct6C6G6Q5LqS jgJAqa5QBfJCS5OsMXSaf1cZapFTkQ== =R1aO -----END PGP SIGNATURE----- --Sig_/tVtmaodFaJa/ooywirx=fo/-- From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from ozlabs.org ([203.11.71.1]:45079 "EHLO ozlabs.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726281AbfKHExC (ORCPT ); Thu, 7 Nov 2019 23:53:02 -0500 Date: Fri, 8 Nov 2019 15:52:48 +1100 From: Stephen Rothwell Subject: Re: generic-iomap tree for linux-next Message-ID: <20191108155248.0a32a03a@canb.auug.org.au> In-Reply-To: <20191108132000.3e7bd5b8@canb.auug.org.au> References: <20191029064834.23438-1-hch@lst.de> <20191107204743.GA22863@lst.de> <20191108132000.3e7bd5b8@canb.auug.org.au> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="Sig_/tVtmaodFaJa/ooywirx=fo/"; protocol="application/pgp-signature"; micalg=pgp-sha256 Sender: linux-arch-owner@vger.kernel.org List-ID: To: Christoph Hellwig Cc: Arnd Bergmann , Guo Ren , Michal Simek , Greentime Hu , Vincent Chen , Guan Xuetao , x86@kernel.org, linux-arch@vger.kernel.org, linux-s390@vger.kernel.org, linux-ia64@vger.kernel.org, linux-parisc@vger.kernel.org, linux-sh@vger.kernel.org, linux-hexagon@vger.kernel.org, linux-xtensa@linux-xtensa.org, linux-mips@vger.kernel.org, linux-kernel@vger.kernel.org, linux-m68k@lists.linux-m68k.org, openrisc@lists.librecores.org, linux-mtd@lists.infradead.org, linux-alpha@vger.kernel.org, sparclinux@vger.kernel.org, nios2-dev@lists.rocketboards.org, linux-riscv@lists.infradead.org, linux-snps-arc@lists.infradead.org, linux-arm-kernel@lists.infradead.org Message-ID: <20191108045248.QntRdeiS4jDZEaj6XZuRL0-ERE5hxHP3o6W_KrwDTwA@z> --Sig_/tVtmaodFaJa/ooywirx=fo/ Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable Hi Christoph, On Fri, 8 Nov 2019 13:20:00 +1100 Stephen Rothwell w= rote: > > On Thu, 7 Nov 2019 21:47:43 +0100 Christoph Hellwig wrote: > > > > can you add the generic-ioremap tree: > >=20 > > git://git.infradead.org/users/hch/ioremap.git > >=20 > > to linux-next? =20 >=20 > I assume you mean the for-next branch? With that assumption, 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_/tVtmaodFaJa/ooywirx=fo/ Content-Type: application/pgp-signature Content-Description: OpenPGP digital signature -----BEGIN PGP SIGNATURE----- iQEzBAEBCAAdFiEENIC96giZ81tWdLgKAVBC80lX0GwFAl3E9KAACgkQAVBC80lX 0GzmWwf+Klgi0tTyTa+t0RWIsOgTgCRRshcd2R+zC2TAQiqpOvNWxiNkHSOO6rPt AIwk9/iB+0v8JHEaYe+JqqmAtlRJjfMKtLkGBCB8WLQ/Sw+V+BW+2kZfZbMDL47C Q2NA/MqqCVxs38kWlJA+gd3xF1FJLjYYuHlhaksjzlHUVGVcCxeXRrd521DYPcwm 9ZzSoL0488rxdiISFluZ44y3nKSgX3Ye5J4DnymJod7hsctYKZvWL+GxoizD+i6m HgzcYw5CxoMeQcS9WgBNCafeABW7i7w3jfCsmBjTNWCuUkE+Pruoct6C6G6Q5LqS jgJAqa5QBfJCS5OsMXSaf1cZapFTkQ== =R1aO -----END PGP SIGNATURE----- --Sig_/tVtmaodFaJa/ooywirx=fo/--