From: Wei Xu <xuwei5@hisilicon.com>
To: wenpan <wenpan@hisilicon.com>, Arnd Bergmann <arnd@arndb.de>,
Marty Plummer <netz.kernel@gmail.com>
Cc: mturquette@baylibre.com, sboyd@codeaurora.org,
robh+dt@kernel.org, mark.rutland@arm.com, linux@armlinux.org.uk,
linux-clk@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, howell.yang@hisilicon.com,
xuejiancheng@hisilicon.com, jalen.hsu@hisilicon.com,
lvkuanliang@hisilicon.com, suwenping@hisilicon.com,
raojun@hisilicon.com, kevin.lixu@hisilicon.com,
qinxiaojun@huawei.com
Subject: Re: [PATCH 1/3] arm: hisi: add ARCH_MULTI_V5 support
Date: Wed, 16 Nov 2016 09:31:49 +0000 [thread overview]
Message-ID: <582C2785.2010804@hisilicon.com> (raw)
In-Reply-To: <e78a288b-8bab-9441-2edb-6ec08e5103d7@hisilicon.com>
Hi Pan,
On 2016/11/16 8:56, wenpan wrote:
> Hi Marty，
> Does this confict with your patch？ If not，I hope this could be merged first. Besides could you tell me the link to your related patch?
This is the link: https://patchwork.kernel.org/patch/9334743/
BR,
Wei
>
> Thanks,
> Pan
>
> 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.
>>
>> Arnd
>>
>> .
>>
>
>
> .
>
next prev parent reply other threads:[~2016-11-16 9:31 UTC|newest]
Thread overview: 19+ 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
[not found] ` <20161017120705.3726-2-wenpan-C8/M+/jPZTeaMJb+Lgu22Q@public.gmane.org>
2016-10-17 13:48 ` Arnd Bergmann
2016-11-16 8:56 ` wenpan
2016-11-16 9:31 ` Wei Xu [this message]
[not found] ` <582C2785.2010804-C8/M+/jPZTeaMJb+Lgu22Q@public.gmane.org>
2016-11-17 3:03 ` Jiancheng Xue
2016-11-18 6:42 ` Jiancheng Xue
2017-10-11 5:35 ` Hao Zhang
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
[not found] ` <5dc55eef-808e-fa78-a5a0-4fccb31e5ceb-C8/M+/jPZTeaMJb+Lgu22Q@public.gmane.org>
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
[not found] ` <20161017120705.3726-4-wenpan-C8/M+/jPZTeaMJb+Lgu22Q@public.gmane.org>
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=582C2785.2010804@hisilicon.com \
--to=xuwei5@hisilicon.com \
--cc=arnd@arndb.de \
--cc=devicetree@vger.kernel.org \
--cc=howell.yang@hisilicon.com \
--cc=jalen.hsu@hisilicon.com \
--cc=kevin.lixu@hisilicon.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=lvkuanliang@hisilicon.com \
--cc=mark.rutland@arm.com \
--cc=mturquette@baylibre.com \
--cc=netz.kernel@gmail.com \
--cc=qinxiaojun@huawei.com \
--cc=raojun@hisilicon.com \
--cc=robh+dt@kernel.org \
--cc=sboyd@codeaurora.org \
--cc=suwenping@hisilicon.com \
--cc=wenpan@hisilicon.com \
--cc=xuejiancheng@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;
as well as URLs for NNTP newsgroup(s).