From: Alexandre Courbot <acourbot@nvidia.com>
To: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
Cc: Jonathan Cameron <jic23@kernel.org>, <linux-iio@vger.kernel.org>,
"Linus Walleij" <linus.walleij@linaro.org>,
<kernel@pengutronix.de>, Mark Brown <broonie@linaro.org>
Subject: Re: [PATCH] iio: improve usage of gpiod API
Date: Wed, 18 Feb 2015 16:22:06 +0900 [thread overview]
Message-ID: <54E43D9E.9040008@nvidia.com> (raw)
In-Reply-To: <20150218071523.GH19388@pengutronix.de>
On 02/18/2015 04:15 PM, Uwe Kleine-König wrote:
> On Wed, Feb 18, 2015 at 10:08:42AM +0900, Alexandre Courbot wrote:
>> On 02/17/2015 06:21 PM, Uwe Kleine-König wrote:
>>> Since 39b2bbe3d715 (gpio: add flags argument to gpiod_get*() functions)
>>> which appeared in v3.17-rc1, the gpiod_get* functions take an additional
>>> parameter that allows to specify direction and initial value for
>>> outputs.
>>>
>>> Signed-off-by: Uwe Kleine-König <u.kleine-koenig@pengutronix.de>
>>
>> Nice, thanks for taking the time to do this!
> I have some more, just didn't come around to wrap in commits and send
> out:
>
> http://git.pengutronix.de/?p=ukl/linux.git;a=commitdiff;h=1783b17ba922f92d043bad650c0209de1c201080;hp=e36f014edff70fc02b3d3d79cead1d58f289332e
>
> I will do one patch a day ...
That's great - do these cover all the uses of gpiod_get* that need to be
updated? If so, you could close this series with a final patch that
removes the macro definitions allowing variable arguments.
next prev parent reply other threads:[~2015-02-18 7:22 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-17 9:21 [PATCH] iio: improve usage of gpiod API Uwe Kleine-König
2015-02-17 10:05 ` Linus Walleij
2015-02-18 1:08 ` Alexandre Courbot
2015-02-18 7:15 ` Uwe Kleine-König
2015-02-18 7:22 ` Alexandre Courbot [this message]
2015-02-18 7:25 ` Uwe Kleine-König
2015-02-18 7:28 ` Alexandre Courbot
2015-02-18 9:55 ` Daniel Baluta
2015-02-18 9:39 ` Linus Walleij
2015-02-22 9:51 ` Jonathan Cameron
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=54E43D9E.9040008@nvidia.com \
--to=acourbot@nvidia.com \
--cc=broonie@linaro.org \
--cc=jic23@kernel.org \
--cc=kernel@pengutronix.de \
--cc=linus.walleij@linaro.org \
--cc=linux-iio@vger.kernel.org \
--cc=u.kleine-koenig@pengutronix.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.