[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <a3917cf4-6090-2c47-f8f6-c25db52662e0@gmail.com>
Date: Tue, 18 Jun 2019 19:27:09 +0300
From: Dmitry Osipenko <digetx@...il.com>
To: Mark Brown <broonie@...nel.org>
Cc: Thierry Reding <thierry.reding@...il.com>,
Jonathan Hunter <jonathanh@...dia.com>,
Peter De Schrijver <pdeschrijver@...dia.com>,
Rob Herring <robh+dt@...nel.org>, devicetree@...r.kernel.org,
linux-tegra@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v2 2/8] regulator: core: Parse max-spread value per
regulator couple
17.06.2019 18:25, Mark Brown пишет:
> On Tue, Jun 04, 2019 at 02:58:58AM +0300, Dmitry Osipenko wrote:
>
>> +#include <linux/regulator/driver.h>
>> #include <linux/regulator/consumer.h>
>> #include <linux/suspend.h>
>>
>> @@ -156,7 +157,7 @@ struct regulation_constraints {
>> int system_load;
>>
>> /* used for coupled regulators */
>> - int max_spread;
>> + int max_spread[MAX_COUPLED];
>
> I'd rather move MAX_COUPLED into a separate header than include driver.h
> so we've got a bit more compile time sepration.
>
I'll address this in the next revision.
Powered by blists - more mailing lists