[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4902591.DhWVhdI4KP@wuerfel>
Date: Wed, 09 Dec 2015 11:00:21 +0100
From: Arnd Bergmann <arnd@...db.de>
To: linux-arm-kernel@...ts.infradead.org
Cc: "Yankejian (Hackim Yim)" <yankejian@...wei.com>,
mark.rutland@....com, lisheng011@...wei.com,
salil.mehta@...wei.com, liguozhu@...wei.com,
haifeng.wei@...wei.com, pawel.moll@....com,
ijc+devicetree@...lion.org.uk, catalin.marinas@....com,
will.deacon@....com, linux-kernel@...r.kernel.org,
xuwei5@...ilicon.com, devicetree@...r.kernel.org,
robh+dt@...nel.org, huangdaode@...ilicon.com, galak@...eaurora.org,
netdev@...r.kernel.org, fengguang.wu@...el.com,
Yisen.Zhuang@...wei.com, davem@...emloft.net
Subject: Re: arRe: [PATCH net-next 2/2] net: hns: enet specisies a reference to dsaf (config and documents)
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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists