On Sun, 02 Jun 2019 16:43:14 +0900, Stephen Rothwell wrote: > > [1 <text/plain; US-ASCII (quoted-printable)>] > Hi Yoshinori, > > On Sun, 02 Jun 2019 16:13:04 +0900 Yoshinori Sato <ysato@xxxxxxxxxxxxxxxxxxxx> wrote: > > > > Since I created a temporary sh-next, please get it here. > > git://git.sourceforge.jp/gitroot/uclinux-h8/linux.git tags/sh-next > > I have added that tree to linux-next from tomorrow. However, thet is > no sh-next tag in that tree, so I used the sh-next branch. I don't > think you need the back merge of Linus' tree. Oh sorry. I created sh-next branch in this git repository. > 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. > > 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@xxxxxxxxxxxxxxxx > [2 OpenPGP digital signature <application/pgp-signature (7bit)>] > No public key for 015042F34957D06C created at 2019-06-02T16:43:14+0900 using RSA -- Yosinori Sato
