Hi Stephen,
Could you please add https://github.com/andestech/linux.git next
to linux-next
I will be sending pull requests to Linus for nds32 to be
included for 4.17 release.
https://lkml.org/lkml/2018/2/14/423
Thank you.
Greentime :)
Hi Greentime,
On Wed, 21 Feb 2018 16:14:39 +0800 Greentime Hu <[email protected]> wrote:
>
> Could you please add https://github.com/andestech/linux.git next
> to linux-next
>
> I will be sending pull requests to Linus for nds32 to be
> included for 4.17 release.
>
> https://lkml.org/lkml/2018/2/14/423
OK, I can't actually use your tree as it is at the moment. It contains
a set of patches that are copies of some commits in Linus' tree - it
looks like a rebase gone wrong. Please fix that up and try again.
--
Cheers,
Stephen Rothwell
2018-02-22 8:29 GMT+08:00 Stephen Rothwell <[email protected]>:
> Hi Greentime,
>
> On Wed, 21 Feb 2018 16:14:39 +0800 Greentime Hu <[email protected]> wrote:
>>
>> Could you please add https://github.com/andestech/linux.git next
>> to linux-next
>>
>> I will be sending pull requests to Linus for nds32 to be
>> included for 4.17 release.
>>
>> https://lkml.org/lkml/2018/2/14/423
>
> OK, I can't actually use your tree as it is at the moment. It contains
> a set of patches that are copies of some commits in Linus' tree - it
> looks like a rebase gone wrong. Please fix that up and try again.
Hi, Stephen:
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.
Hi Greentime,
On Thu, 22 Feb 2018 11:36:02 +0800 Greentime Hu <[email protected]> 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
[email protected]