[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <d5e63ea6935991d855e2ae12915b3b4614e8f3aa.camel@fi.rohmeurope.com>
Date: Tue, 25 Feb 2020 06:23:31 +0000
From: "Vaittinen, Matti" <Matti.Vaittinen@...rohmeurope.com>
To: "broonie@...nel.org" <broonie@...nel.org>
CC: "rafael@...nel.org" <rafael@...nel.org>,
"mazziesaccount@...il.com" <mazziesaccount@...il.com>,
"mark.rutland@....com" <mark.rutland@....com>,
"gregkh@...uxfoundation.org" <gregkh@...uxfoundation.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"devicetree@...r.kernel.org" <devicetree@...r.kernel.org>,
"sre@...nel.org" <sre@...nel.org>,
"Laine, Markus" <Markus.Laine@...rohmeurope.com>,
"linux-pm@...r.kernel.org" <linux-pm@...r.kernel.org>,
"robh+dt@...nel.org" <robh+dt@...nel.org>,
"lgirdwood@...il.com" <lgirdwood@...il.com>,
"Mutanen, Mikko" <Mikko.Mutanen@...rohmeurope.com>
Subject: Re: [RFC PATCH v3 5/8] regulator: use linear_ranges helper
Hello Mark,
On Mon, 2020-02-24 at 11:57 +0000, Mark Brown wrote:
> On Thu, Feb 20, 2020 at 09:36:38AM +0200, Matti Vaittinen wrote:
> > Change the regulator helpers to use common linear_ranges code.
>
> This needs to be squashed in with the previous commit to avoid build
> breaks.
I don't think so.
Only change required on individual regulator drivers should be renaming
the struct regulator_linear_range to linear_range. Rest of the changes
should be internal to regulator framework, right?
Even the naming change of the linear_range struct members should not be
visible to these drivers as they use the initializer macro for setting
the values. I must admit I didn't compile _all_ the regulator drivers
when I tested this though. I will try compiling at least most of the
regulator drivers for next version though. And I think the feedback for
this series has been mostly positive so I'll also drop the RFC for it.
Best Regards
Matti Vaittinen
Powered by blists - more mailing lists