[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <DB5PR0401MB22130B915A5690E9BC56CCE5F3F70@DB5PR0401MB2213.eurprd04.prod.outlook.com>
Date: Thu, 25 Oct 2018 02:40:03 +0000
From: Andy Tang <andy.tang@....com>
To: Scott Wood <oss@...error.net>,
"sboyd@...nel.org" <sboyd@...nel.org>,
"mturquette@...libre.com" <mturquette@...libre.com>
CC: "robh+dt@...nel.org" <robh+dt@...nel.org>,
"mark.rutland@....com" <mark.rutland@....com>,
"benh@...nel.crashing.org" <benh@...nel.crashing.org>,
"paulus@...ba.org" <paulus@...ba.org>,
"mpe@...erman.id.au" <mpe@...erman.id.au>,
"linux-clk@...r.kernel.org" <linux-clk@...r.kernel.org>,
"devicetree@...r.kernel.org" <devicetree@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"linuxppc-dev@...ts.ozlabs.org" <linuxppc-dev@...ts.ozlabs.org>
Subject: RE: [PATCH 3/3 v2] clk: qoriq: update clock driver
> -----Original Message-----
> From: Scott Wood <oss@...error.net>
> Sent: 2018年10月25日 2:37
> To: Andy Tang <andy.tang@....com>; sboyd@...nel.org;
> mturquette@...libre.com
> Cc: robh+dt@...nel.org; mark.rutland@....com;
> benh@...nel.crashing.org; paulus@...ba.org; mpe@...erman.id.au;
> linux-clk@...r.kernel.org; devicetree@...r.kernel.org;
> linux-kernel@...r.kernel.org; linuxppc-dev@...ts.ozlabs.org
> Subject: Re: [PATCH 3/3 v2] clk: qoriq: update clock driver
>
> On Wed, 2018-10-24 at 10:11 +0800, andy.tang@....com wrote:
> > From: Yuantian Tang <andy.tang@....com>
> >
> > Legacy bindings are deleted. So the legacy support in driver can be
> > deleted safely.
>
> NACK (both this and 2/3). The legacy support is intended to preserve
> compatibility, regardless of what the dts files in the current kernel tree do.
> If years later we find it's been broken for a while and nobody complained,
> then maybe it'll be time to remove it, but why deliberately throw away
> compatibility the instant the users have been removed from reference
> DTs that might be copied by board vendors, etc?
>
> Note that even if we didn't care about long-term compatibility at all,
> removing the support in the same patchset as the change to the dts files
> means that the patches can't go in via separate trees (though if that's still
> the intent, you should make it clear who you're asking to take what by
> putting them in separate patchsets).
Points are taken. Will update this patch set. Thanks a lot.
BR,
Andy
>
> -Scott
Powered by blists - more mailing lists