From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/7] ARM: hisi: enable HiP01 SoC
Date: Thu, 04 Dec 2014 13:58:52 +0100 [thread overview]
Message-ID: <3601066.g7Jvjk5UFL@wuerfel> (raw)
In-Reply-To: <1417140950-67103-1-git-send-email-long.wanglong@huawei.com>
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.
Is Xu Wei going to pick these up in a git tree and send a pull request
to arm at kernel.org?
Arnd
next prev parent reply other threads:[~2014-12-04 12:58 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 ` Arnd Bergmann [this message]
2014-12-05 0:34 ` [PATCH 0/7] ARM: hisi: enable HiP01 SoC Wei Xu
-- 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=3601066.g7Jvjk5UFL@wuerfel \
--to=arnd@arndb.de \
--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