Re: Please add my h8300 tree to linux-next

From: Yoshinori Sato
Date: Tue May 12 2015 - 23:14:50 EST


At Wed, 13 May 2015 12:01:43 +1000,
Stephen Rothwell wrote:
>
> [1 <text/plain; US-ASCII (quoted-printable)>]
> Hi Yoshinori,
>
> On Wed, 13 May 2015 09:49:42 +0900 Yoshinori Sato <ysato@xxxxxxxxxxxxxxxxxxxx> wrote:
> >
> > At Wed, 13 May 2015 08:52:03 +1000, Stephen Rothwell wrote:
> > >
> > > On Wed, 13 May 2015 01:18:31 +0900 Yoshinori Sato <ysato@xxxxxxxxxxxxxxxxxxxx> wrote:
> > > >
> > > > Could you add this tree?
> > > > git://git.osdn.jp/gitroot/uclinux-h8/linux.git h8300-next
> > >
> > > I would be happy to, but:
> > >
> > > fatal: unable to connect to git.osdn.jp:
> > > git.osdn.jp[0: 202.221.179.28]: errno=Connection refused
> >
> > Sorry.
> > pleae try this server.
> > git://git.sourceforge.jp/gitroot/uclinux-h8/linux.git h8300-next
>
> 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.
>
> 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.

OK.
Thanks.

> --
> Cheers,
> Stephen Rothwell
> sfr@xxxxxxxxxxxxxxxx
> [2 OpenPGP digital signature <application/pgp-signature (7bit)>]
> No public key for C0D36BC22BED9C15 created at 2015-05-13T11:01:48+0900 using RSA

--
Yoshinori Sato
<ysato@xxxxxxxxxxxxxxxxxxxx>
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/