mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jiancheng Xue <xuejiancheng@hisilicon.com>
To: Arnd Bergmann <arnd@arndb.de>, Pan Wen <wenpan@hisilicon.com>
Cc: <robh+dt@kernel.org>, <mark.rutland@arm.com>,
	<linux@armlinux.org.uk>, <xuwei5@hisilicon.com>,
	<linux-kernel@vger.kernel.org>,
	<linux-arm-kernel@lists.infradead.org>,
	<howell.yang@hisilicon.com>, <jalen.hsu@hisilicon.com>,
	<lvkuanliang@hisilicon.com>, <suwenping@hisilicon.com>,
	<raojun@hisilicon.com>, <kevin.lixu@hisilicon.com>,
	Marty Plummer <netz.kernel@gmail.com>
Subject: Re: [PATCH 1/3] arm: hisi: add ARCH_MULTI_V5 support
Date: Mon, 5 Dec 2016 10:03:16 +0800	[thread overview]
Message-ID: <2fcf5a5f-8935-c4f0-a034-c8a72dc2be0f@hisilicon.com> (raw)
In-Reply-To: <5893354.6MrIxqzRoI@wuerfel>

Hi Arnd,

On 2016/10/17 21:48, Arnd Bergmann wrote:
> On Monday, October 17, 2016 8:07:03 PM CEST Pan Wen wrote:
>> Add support for some HiSilicon SoCs which depend on ARCH_MULTI_V5.
>>
>> Signed-off-by: Pan Wen <wenpan@hisilicon.com>
>>
> 
> Looks ok. I've added Marty Plummer to Cc, he was recently proposing
> patches for Hi3520, which I think is closely related to this one.
> Please try to work together so the patches don't conflict. It should
> be fairly straightforward since you are basically doing the same
> change here.
> 
Marty hasn't give any replies about this thread until now. I reviewed
the patch for Hi3520. And I think this patch won't conflict with Hi3520.
Could you help us to ack this patch?

Thanks,
Jiancheng

  parent reply	other threads:[~2016-12-05  2:04 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-17 12:07 [PATCH 0/3] add basic SoC support for HiSilicon Hi3516CV300 Pan Wen
2016-10-17 12:07 ` [PATCH 1/3] arm: hisi: add ARCH_MULTI_V5 support Pan Wen
2016-10-17 13:48   ` Arnd Bergmann
2016-11-16  8:56     ` wenpan
2016-11-16  9:31       ` Wei Xu
2016-11-17  3:03         ` Jiancheng Xue
2016-11-18  6:42           ` Jiancheng Xue
2016-12-05  2:03     ` Jiancheng Xue [this message]
2016-12-09 15:07       ` Marty Plummer
2016-12-12  7:11         ` Jiancheng Xue
     [not found]           ` <59a9b91c-d7be-cf3a-d461-252cb493d61c@gmail.com>
2017-01-20  1:47             ` Jiancheng Xue
2017-01-27 16:44               ` Arnd Bergmann
2016-10-17 12:07 ` [PATCH 2/3] clk: hisilicon: add CRG driver for Hi3516CV300 SoC Pan Wen
2016-10-18 15:58   ` Rob Herring
2016-10-19  2:38     ` Jiancheng Xue
2016-10-19  2:45       ` Rob Herring
2016-10-19  3:54         ` Jiancheng Xue
2016-10-20 17:48           ` Stephen Boyd
2016-10-21  1:46             ` Jiancheng Xue
2016-10-17 12:07 ` [PATCH 3/3] dts: hisi: add dts files for Hi3516CV300 demo board Pan Wen
2016-12-12 11:34   ` Jiancheng Xue
2017-01-20 16:40   ` Wei Xu
2017-01-22  9:33   ` Kefeng Wang

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=2fcf5a5f-8935-c4f0-a034-c8a72dc2be0f@hisilicon.com \
    --to=xuejiancheng@hisilicon.com \
    --cc=arnd@arndb.de \
    --cc=howell.yang@hisilicon.com \
    --cc=jalen.hsu@hisilicon.com \
    --cc=kevin.lixu@hisilicon.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@armlinux.org.uk \
    --cc=lvkuanliang@hisilicon.com \
    --cc=mark.rutland@arm.com \
    --cc=netz.kernel@gmail.com \
    --cc=raojun@hisilicon.com \
    --cc=robh+dt@kernel.org \
    --cc=suwenping@hisilicon.com \
    --cc=wenpan@hisilicon.com \
    --cc=xuwei5@hisilicon.com \
    /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

all inboxes | Powered by JetHome®