[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <VI1PR10MB235240E26EFE426F0B6D6EA0FE720@VI1PR10MB2352.EURPRD10.PROD.OUTLOOK.COM>
Date: Tue, 5 Mar 2019 10:03:08 +0000
From: Steve Twiss <stwiss.opensource@...semi.com>
To: Axel Lin <axel.lin@...ics.com>, Mark Brown <broonie@...nel.org>
CC: Support Opensource <Support.Opensource@...semi.com>,
Liam Girdwood <lgirdwood@...il.com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: RE: [PATCH 2/2] regulator: da9063: Convert to use
regulator_set/get_current_limit_regmap
On 04 March 2019 13:16, Axel Lin wrote:
Hi Axel,
> To: Mark Brown <broonie@...nel.org>
> Subject: [PATCH 2/2] regulator: da9063: Convert to use
> regulator_set/get_current_limit_regmap
>
> Use regulator_set/get_current_limit_regmap helpers to save some code.
>
> Signed-off-by: Axel Lin <axel.lin@...ics.com>
> ---
> drivers/regulator/da9063-regulator.c | 107 +++++++--------------------
> 1 file changed, 28 insertions(+), 79 deletions(-)
Thanks again,
Acked-by: Steve Twiss <stwiss@...nsource.diasemi.com>
Regards,
Steve
ps.
This patch applies to next-20190305.
But doesn't cleanly apply cleanly to v5.0, I guess because there are several patches
queued up in linux-next, in the same way as the da9062 patch has minor issues for v5.0.
Hunk #4 FAILED at 131.
Hunk #7 FAILED at 850
2 out of 7 hunks FAILED -- saving rejects to file drivers/regulator/da9063-regulator.c.rej
Powered by blists - more mailing lists