From: haojian.zhuang@gmail.com (Haojian Zhuang)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL][for 3.14] pull request to enable Hisilicon SoC from pxa git tree
Date: Mon, 25 Nov 2013 13:18:59 +0800 [thread overview]
Message-ID: <5292DDC3.8060707@gmail.com> (raw)
In-Reply-To: <CAOesGMjomMk205LQojzO2-zyjvnxtUh_gkfd74WgB4TWbnxDYg@mail.gmail.com>
On 11/25/2013 12:05 PM, Olof Johansson wrote:
> Hi,
>
>
> On Sun, Nov 24, 2013 at 7:07 PM, Haojian Zhuang
> <haojian.zhuang@gmail.com> wrote:
>> Hi Olof & Kevin,
>>
>> Here's the pull request from pxa git tree to enable Hisilicon Hi3620 SoC.
>> Please help to merge.
>>
>> Best Regards
>> Haojian
>>
>> The following changes since commit 6ce4eac1f600b34f2f7f58f9cd8f0503d79e42ae:
>>
>> Linux 3.13-rc1 (2013-11-22 11:30:55 -0800)
>>
>> are available in the git repository at:
>>
>> http://git.kernel.org/pub/scm/linux/kernel/git/hzhuang1/linux.git
>> tags/hisilicon-init
>
> Hi,
>
> Overall this looks good, but I do have a few comments:
>
> First, I had a comment on one of the patches. It's your choice if you
> want to address it by respinning or by an incremental patch on top,
> but please address those.
Let me fix those. And send a second pull request.
>
> Second, it seems appropriate for you to start a second git tree for
> hisilicon, instead of reusing the pxa one -- at least if you expect
> more activity on that platform over time. You can create new trees on
> kernel.org as you see fit, so there's no reason not to.
>
Since hisilicon guys want to maintainer their SoC by themselves. This
patch set submitted by me is temporary in my git tree. They'll take over
my job in these weeks. So they'll submit pull request instead, and I'll
only submit patches.
And this git tree will be only used for pxa/mmp since github isn't
preferred. I'll update the MAINTAINER document instead.
> Thirdly, I noticed some patches have a Signed-off-by from your linaro
> address, and a committer ID of your gmail account. Please be
> consistent in which one you use since last S-o-b and committer should
> match -- you might want to reconfigure git to use the linaro one but
> either way is fine with me as long as it is consistent.
>
OK. Let me make them consistent.
> Finally, you've had a lot of review cycles, but surprisingly not many
> acked-by's on the final patches. See if you can get some out of the
> people whose feedback you have addressed.
>
Let me try.
Best Regards
Haojian
>
> Since you have to rebuild the branch to fix committer id, you might
> want to just fold in the changes from my review, but I'll leave that
> up to you.
>
> -Olof
>
prev parent reply other threads:[~2013-11-25 5:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-25 3:07 [GIT PULL][for 3.14] pull request to enable Hisilicon SoC from pxa git tree Haojian Zhuang
2013-11-25 4:05 ` Olof Johansson
2013-11-25 5:18 ` Haojian Zhuang [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=5292DDC3.8060707@gmail.com \
--to=haojian.zhuang@gmail.com \
--cc=linux-arm-kernel@lists.infradead.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).