From: yankejian@huawei.com (Yankejian (Hackim Yim))
To: linux-arm-kernel@lists.infradead.org
Subject: arRe: [PATCH net-next 2/2] net: hns: enet specisies a reference to dsaf (config and documents)
Date: Wed, 9 Dec 2015 18:23:48 +0800 [thread overview]
Message-ID: <56680134.90504@huawei.com> (raw)
In-Reply-To: <4902591.DhWVhdI4KP@wuerfel>
On 2015/12/9 18:00, Arnd Bergmann wrote:
> On Wednesday 09 December 2015 17:25:13 Yankejian wrote:
>> thanks a lot for pointing it out.
>>
>> It is great regret that this change breaks compatibility with old dtbs.
>> this is a new driver which is run on developing boards, and all the
>> clients' boards are developing boards. So we provide them a method to
>> update the firmware on the board, once we update the dtsi and kernel,
>> we require our clients to update the existed firmware and kernel.
>> Therefore, these changes is actually under control. Shall we treat this
>> by this way?
> Ok, if you can show that the incompatible change is safe to do, that's
> fine. Just put the explanation above into the patch description to
> document that you have considered the effects of the change, and
> to ensure that it gets done atomically.
>
> Also, you have to merge the two patches into one to allow bisection,
> or do a series of three patches that need to be applied in order:
>
> 1. add ae-handle property
> 2. change driver to use that property
> 3. remove ae-name property
>
> Arnd
>
> .
>
Ok, thanks for your good advices.
i will change it in V2 PATCH.
Bset Regards
yankejian
WARNING: multiple messages have this Message-ID (diff)
From: "Yankejian (Hackim Yim)" <yankejian@huawei.com>
To: Arnd Bergmann <arnd@arndb.de>, linux-arm-kernel@lists.infradead.org
Cc: mark.rutland@arm.com, lisheng011@huawei.com,
salil.mehta@huawei.com, liguozhu@huawei.com,
haifeng.wei@huawei.com, pawel.moll@arm.com,
ijc+devicetree@hellion.org.uk, catalin.marinas@arm.com,
will.deacon@arm.com, linux-kernel@vger.kernel.org,
xuwei5@hisilicon.com, devicetree@vger.kernel.org,
robh+dt@kernel.org, huangdaode@hisilicon.com,
galak@codeaurora.org, netdev@vger.kernel.org,
fengguang.wu@intel.com, Yisen.Zhuang@huawei.com,
davem@davemloft.net
Subject: Re: arRe: [PATCH net-next 2/2] net: hns: enet specisies a reference to dsaf (config and documents)
Date: Wed, 9 Dec 2015 18:23:48 +0800 [thread overview]
Message-ID: <56680134.90504@huawei.com> (raw)
In-Reply-To: <4902591.DhWVhdI4KP@wuerfel>
On 2015/12/9 18:00, Arnd Bergmann wrote:
> On Wednesday 09 December 2015 17:25:13 Yankejian wrote:
>> thanks a lot for pointing it out.
>>
>> It is great regret that this change breaks compatibility with old dtbs.
>> this is a new driver which is run on developing boards, and all the
>> clients' boards are developing boards. So we provide them a method to
>> update the firmware on the board, once we update the dtsi and kernel,
>> we require our clients to update the existed firmware and kernel.
>> Therefore, these changes is actually under control. Shall we treat this
>> by this way?
> Ok, if you can show that the incompatible change is safe to do, that's
> fine. Just put the explanation above into the patch description to
> document that you have considered the effects of the change, and
> to ensure that it gets done atomically.
>
> Also, you have to merge the two patches into one to allow bisection,
> or do a series of three patches that need to be applied in order:
>
> 1. add ae-handle property
> 2. change driver to use that property
> 3. remove ae-name property
>
> Arnd
>
> .
>
Ok, thanks for your good advices.
i will change it in V2 PATCH.
Bset Regards
yankejian
WARNING: multiple messages have this Message-ID (diff)
From: "Yankejian (Hackim Yim)" <yankejian@huawei.com>
To: Arnd Bergmann <arnd@arndb.de>, <linux-arm-kernel@lists.infradead.org>
Cc: <mark.rutland@arm.com>, <lisheng011@huawei.com>,
<salil.mehta@huawei.com>, <liguozhu@huawei.com>,
<haifeng.wei@huawei.com>, <pawel.moll@arm.com>,
<ijc+devicetree@hellion.org.uk>, <catalin.marinas@arm.com>,
<will.deacon@arm.com>, <linux-kernel@vger.kernel.org>,
<xuwei5@hisilicon.com>, <devicetree@vger.kernel.org>,
<robh+dt@kernel.org>, <huangdaode@hisilicon.com>,
<galak@codeaurora.org>, <netdev@vger.kernel.org>,
<fengguang.wu@intel.com>, <Yisen.Zhuang@huawei.com>,
<davem@davemloft.net>
Subject: Re: arRe: [PATCH net-next 2/2] net: hns: enet specisies a reference to dsaf (config and documents)
Date: Wed, 9 Dec 2015 18:23:48 +0800 [thread overview]
Message-ID: <56680134.90504@huawei.com> (raw)
In-Reply-To: <4902591.DhWVhdI4KP@wuerfel>
On 2015/12/9 18:00, Arnd Bergmann wrote:
> On Wednesday 09 December 2015 17:25:13 Yankejian wrote:
>> thanks a lot for pointing it out.
>>
>> It is great regret that this change breaks compatibility with old dtbs.
>> this is a new driver which is run on developing boards, and all the
>> clients' boards are developing boards. So we provide them a method to
>> update the firmware on the board, once we update the dtsi and kernel,
>> we require our clients to update the existed firmware and kernel.
>> Therefore, these changes is actually under control. Shall we treat this
>> by this way?
> Ok, if you can show that the incompatible change is safe to do, that's
> fine. Just put the explanation above into the patch description to
> document that you have considered the effects of the change, and
> to ensure that it gets done atomically.
>
> Also, you have to merge the two patches into one to allow bisection,
> or do a series of three patches that need to be applied in order:
>
> 1. add ae-handle property
> 2. change driver to use that property
> 3. remove ae-name property
>
> Arnd
>
> .
>
Ok, thanks for your good advices.
i will change it in V2 PATCH.
Bset Regards
yankejian
next prev parent reply other threads:[~2015-12-09 10:23 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-05 6:10 [PATCH net-next 0/2] net: hns: enet specisies a reference to dsaf yankejian
2015-12-05 6:10 ` yankejian
2015-12-05 6:10 ` yankejian
2015-12-05 6:10 ` yankejian
2015-12-05 6:10 ` [PATCH net-next 1/2] " yankejian
2015-12-05 6:10 ` yankejian
2015-12-05 6:10 ` yankejian
2015-12-05 6:10 ` [PATCH net-next 2/2] net: hns: enet specisies a reference to dsaf (config and documents) yankejian
2015-12-05 6:10 ` yankejian
2015-12-05 6:10 ` yankejian
2015-12-05 22:19 ` Arnd Bergmann
2015-12-05 22:19 ` Arnd Bergmann
2015-12-07 7:14 ` Yankejian (Hackim Yim)
2015-12-07 7:14 ` Yankejian (Hackim Yim)
2015-12-07 7:14 ` Yankejian (Hackim Yim)
2015-12-07 7:14 ` Yankejian (Hackim Yim)
2015-12-07 9:40 ` arRe: " Arnd Bergmann
2015-12-07 9:40 ` Arnd Bergmann
2015-12-09 9:25 ` Yankejian (Hackim Yim)
2015-12-09 9:25 ` Yankejian (Hackim Yim)
2015-12-09 9:25 ` Yankejian (Hackim Yim)
2015-12-09 10:00 ` Arnd Bergmann
2015-12-09 10:00 ` Arnd Bergmann
2015-12-09 10:23 ` Yankejian (Hackim Yim) [this message]
2015-12-09 10:23 ` Yankejian (Hackim Yim)
2015-12-09 10:23 ` Yankejian (Hackim Yim)
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=56680134.90504@huawei.com \
--to=yankejian@huawei.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.