[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAJKOXPeREmAhrdxJAR4_Pn6ZzYEk8uR_dMCvxLXbBn+bfVQVPQ@mail.gmail.com>
Date: Wed, 22 Jul 2015 11:21:39 +0900
From: Krzysztof Kozlowski <k.kozlowski@...sung.com>
To: Uwe Kleine-König <uwe@...ine-koenig.org>
Cc: Linus Walleij <linus.walleij@...aro.org>,
Mark Brown <broonie@...nel.org>,
Liam Girdwood <lgirdwood@...il.com>,
Uwe Kleine-König
<u.kleine-koenig@...gutronix.de>, Chris Zhong <zyw@...k-chips.com>,
linux-next@...r.kernel.org, linux-kernel@...r.kernel.org,
kernel@...gutronix.de
Subject: Re: [PATCH v2 2/2] regulator: rk808: make better use of the gpiod API
2015-07-21 23:46 GMT+09:00 Uwe Kleine-König <uwe@...ine-koenig.org>:
> From: Uwe Kleine-König <u.kleine-koenig@...gutronix.de>
>
> The gpiod functions include variants for managed gpiod resources. Use it
> to simplify the remove function.
>
> As the driver handles a device node without a specification of dvs gpios
> just fine, additionally use the variant of gpiod_get exactly for this
> use case. This makes error checking more strict.
>
> As a third benefit this patch makes the driver use the flags parameter
> of gpiod_get* which will not be optional any more after 4.2 and so
> prevents a build failure when the respective gpiod commit is merged.
>
> Signed-off-by: Uwe Kleine-König <u.kleine-koenig@...gutronix.de>
> ---
> note the above mentioned gpiod change is already in next, so the driver
> fails to build there.
>
> Changes since (implicit) v1, sent with
> Message-Id: 1437461993-14860-1-git-send-email-u.kleine-koenig@...gutronix.de:
>
> - Assert that of_node_put is called in error path to not leak a reference
> and drop now empty remove callback.
> Thanks to Krzysztof Kozlowski for catching.
>
>
> Best regards
> Uwe
> drivers/regulator/rk808-regulator.c | 32 ++++++++++++--------------------
> 1 file changed, 12 insertions(+), 20 deletions(-)
Looks good now:
Reviewed-by: Krzysztof Kozlowski <k.kozlowski@...sung.com>
Best regards,
Krzysztof
--
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