From: Wei Xu <xuwei5@hisilicon.com>
To: Arnd Bergmann <arnd@arndb.de>, <linux-arm-kernel@lists.infradead.org>
Cc: Wang Long <long.wanglong@huawei.com>, <yanhaifeng@gmail.com>,
<zhangfei.gao@linaro.org>, <haojian.zhuang@linaro.org>,
<galak@codeaurora.org>, <ijc+devicetree@hellion.org.uk>,
<jason@lakedaemon.net>, <jh80.chung@samsung.com>,
<khilman@linaro.org>, <lee.jones@linaro.org>,
<linux@arm.linux.org.uk>, <mark.rutland@arm.com>,
<maxime.ripard@free-electrons.com>, <obh+dt@kernel.org>,
<olof@lixom.net>, <pawel.moll@arm.com>, <swarren@nvidia.com>,
<thomas.petazzoni@free-electrons.com>, <huxinwei@huawei.com>,
<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<peifeiyue@huawei.com>
Subject: Re: [PATCH 0/7] ARM: hisi: enable HiP01 SoC
Date: Fri, 5 Dec 2014 08:34:02 +0800 [thread overview]
Message-ID: <5480FD7A.6030802@hisilicon.com> (raw)
In-Reply-To: <3601066.g7Jvjk5UFL@wuerfel>
On 2014/12/4 20:58, Arnd Bergmann wrote:
> On Friday 28 November 2014 02:15:43 Wang Long wrote:
>> This series patch enable Hisilicon HiP01 SoC. The HiP01 SoC series
>> chip is designed for networking product, it integrates a rich peripheral
>> interfaces to support network applications and supports both one
>> core or dual cores and quad cores. The core is Cortex A9.
>
> Sorry for the delay in my reply. The patches look good to me, but I'm
> not sure what you expect to happen to them. You have a number of
> people listed as recipients, but it's not clear if you expect any of
> us to apply them into a git tree.
Hi Arnd,
> Is Xu Wei going to pick these up in a git tree and send a pull request
> to arm@kernel.org?
I will send a pull request about it.
Thanks!
Best Regards,
Wei
> Arnd
>
> .
>
next prev parent reply other threads:[~2014-12-05 0:36 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-28 2:15 [PATCH 0/7] ARM: hisi: enable HiP01 SoC Wang Long
2014-11-28 2:15 ` [PATCH 1/7] ARM: debug: add HiP01 debug uart Wang Long
2014-11-28 2:15 ` [PATCH 2/7] ARM: hisi: enable HiP01 SoC Wang Long
2014-11-28 2:15 ` [PATCH 3/7] ARM: dts: Add hip01-ca9x2 dts file Wang Long
2014-11-28 2:15 ` [PATCH 4/7] ARM: config: enable ARCH_HIP01 Wang Long
2014-11-28 2:15 ` [PATCH 5/7] ARM: hisi: add a common smp_prepares_cpus function Wang Long
2014-11-28 2:15 ` [PATCH 6/7] ARM: hisi: rename secondary_startup function Wang Long
2014-11-28 2:15 ` [PATCH 7/7] ARM: hisi: enable smp for HiP01 Wang Long
2014-12-04 12:58 ` [PATCH 0/7] ARM: hisi: enable HiP01 SoC Arnd Bergmann
2014-12-05 0:34 ` Wei Xu [this message]
-- strict thread matches above, loose matches on Subject: below --
2014-12-24 3:09 Wang Long
2014-12-24 3:19 ` Wei Xu
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=5480FD7A.6030802@hisilicon.com \
--to=xuwei5@hisilicon.com \
--cc=arnd@arndb.de \
--cc=devicetree@vger.kernel.org \
--cc=galak@codeaurora.org \
--cc=haojian.zhuang@linaro.org \
--cc=huxinwei@huawei.com \
--cc=ijc+devicetree@hellion.org.uk \
--cc=jason@lakedaemon.net \
--cc=jh80.chung@samsung.com \
--cc=khilman@linaro.org \
--cc=lee.jones@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=long.wanglong@huawei.com \
--cc=mark.rutland@arm.com \
--cc=maxime.ripard@free-electrons.com \
--cc=obh+dt@kernel.org \
--cc=olof@lixom.net \
--cc=pawel.moll@arm.com \
--cc=peifeiyue@huawei.com \
--cc=swarren@nvidia.com \
--cc=thomas.petazzoni@free-electrons.com \
--cc=yanhaifeng@gmail.com \
--cc=zhangfei.gao@linaro.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