[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20180222152857.60a47735@canb.auug.org.au>
Date: Thu, 22 Feb 2018 15:28:57 +1100
From: Stephen Rothwell <sfr@...b.auug.org.au>
To: Greentime Hu <green.hu@...il.com>
Cc: Arnd Bergmann <arnd@...db.de>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: Pull Request for linux-next
Hi Greentime,
On Thu, 22 Feb 2018 11:36:02 +0800 Greentime Hu <green.hu@...il.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@...b.auug.org.au
Content of type "application/pgp-signature" skipped
Powered by blists - more mailing lists