public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Yoshinori Sato <ysato@users.sourceforge.jp>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Please add my h8300 tree to linux-next
Date: Wed, 13 May 2015 12:14:41 +0900	[thread overview]
Message-ID: <873831rwwu.wl-ysato@users.sourceforge.jp> (raw)
In-Reply-To: <20150513120143.1d3e3615@canb.auug.org.au>

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@users.sourceforge.jp> 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@users.sourceforge.jp> 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@canb.auug.org.au
> [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@users.sourceforge.jp>

      reply	other threads:[~2015-05-13  3:14 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-12 16:18 Please add my h8300 tree to linux-next Yoshinori Sato
2015-05-12 22:52 ` Stephen Rothwell
2015-05-13  0:49   ` Yoshinori Sato
2015-05-13  2:01     ` Stephen Rothwell
2015-05-13  3:14       ` Yoshinori Sato [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=873831rwwu.wl-ysato@users.sourceforge.jp \
    --to=ysato@users.sourceforge.jp \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox