linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Greentime Hu <green.hu@gmail.com>
Cc: Arnd Bergmann <arnd@arndb.de>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Pull Request for linux-next
Date: Thu, 22 Feb 2018 15:28:57 +1100	[thread overview]
Message-ID: <20180222152857.60a47735@canb.auug.org.au> (raw)
In-Reply-To: <CAEbi=3ef0YhsWj9Sh6FZPWoaYJEZgtXq6_3u4CnXuqjCCLNOww@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1295 bytes --]

Hi Greentime,

On Thu, 22 Feb 2018 11:36:02 +0800 Greentime Hu <green.hu@gmail.com> wrote:
>
> Sorry about that.
> I did the following steps this time and please pull again.
> 
> git remote add mainline https://github.com/torvalds/linux
> git fetch --all
> git checkout -b next v4.16-rc1
> git am ./tmp/*.patch
> 
> Please let me know if I did something wrong.

Looks good.

I have added your tree from tomorrow.

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@canb.auug.org.au

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

  reply	other threads:[~2018-02-22  4:29 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-21  8:14 Pull Request for linux-next Greentime Hu
2018-02-22  0:29 ` Stephen Rothwell
2018-02-22  3:36   ` Greentime Hu
2018-02-22  4:28     ` Stephen Rothwell [this message]
  -- strict thread matches above, loose matches on Subject: below --
2018-02-25  7:59 Tobin C. Harding
2018-02-25 20:54 ` Stephen Rothwell
2018-02-25 22:13   ` Tobin C. Harding
2017-10-31 20:43 Palmer Dabbelt
2017-10-31 21:21 ` Stephen Rothwell
2009-11-15 16:35 PULL request " Tejun Heo
2009-11-15 22:52 ` Stephen Rothwell

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=20180222152857.60a47735@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=arnd@arndb.de \
    --cc=green.hu@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    /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;
as well as URLs for NNTP newsgroup(s).