From: Greentime Hu <green.hu@gmail.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
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 11:36:02 +0800 [thread overview]
Message-ID: <CAEbi=3ef0YhsWj9Sh6FZPWoaYJEZgtXq6_3u4CnXuqjCCLNOww@mail.gmail.com> (raw)
In-Reply-To: <20180222112931.7001de9e@canb.auug.org.au>
2018-02-22 8:29 GMT+08:00 Stephen Rothwell <sfr@canb.auug.org.au>:
> Hi Greentime,
>
> On Wed, 21 Feb 2018 16:14:39 +0800 Greentime Hu <green.hu@gmail.com> 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.
next prev parent reply other threads:[~2018-02-22 3:36 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 [this message]
2018-02-22 4:28 ` Stephen Rothwell
-- 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='CAEbi=3ef0YhsWj9Sh6FZPWoaYJEZgtXq6_3u4CnXuqjCCLNOww@mail.gmail.com' \
--to=green.hu@gmail.com \
--cc=arnd@arndb.de \
--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;
as well as URLs for NNTP newsgroup(s).