linux-iio.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jonathan Cameron <jic23@kernel.org>
To: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>,
	"Daniel Baluta" <daniel.baluta@intel.com>
Cc: Mark Brown <broonie@linaro.org>,
	"linux-iio@vger.kernel.org" <linux-iio@vger.kernel.org>,
	Linus Walleij <linus.walleij@linaro.org>,
	Alexandre Courbot <acourbot@nvidia.com>,
	kernel@pengutronix.de
Subject: Re: [PATCH v3] iio: improve usage of gpiod API
Date: Sun, 22 Feb 2015 09:44:40 +0000	[thread overview]
Message-ID: <54E9A508.9070202@kernel.org> (raw)
In-Reply-To: <20150218160640.GK19388@pengutronix.de>

On 18/02/15 16:06, Uwe Kleine-König wrote:
> Hello Daniel,
> 
> On Wed, Feb 18, 2015 at 03:48:12PM +0200, Daniel Baluta wrote:
>> On Wed, Feb 18, 2015 at 2:47 PM, Uwe Kleine-König
>> <u.kleine-koenig@pengutronix.de> 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>
>>
>> Reviewed-by: Daniel Baluta <daniel.baluta@intel.com>
> Thanks.
Applied to the togreg branch of iio.git. Will initially be pushed out as
testing for the autobuilders to play.

Thanks,

Jonathan
> 
>> I can take care of gpiod_to_irq error code checking.
> Great.
> 
> Best regards
> Uwe
> 


      reply	other threads:[~2015-02-22  9:44 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-18 12:47 [PATCH v3] iio: improve usage of gpiod API Uwe Kleine-König
2015-02-18 13:48 ` Daniel Baluta
2015-02-18 16:06   ` Uwe Kleine-König
2015-02-22  9:44     ` Jonathan Cameron [this message]

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=54E9A508.9070202@kernel.org \
    --to=jic23@kernel.org \
    --cc=acourbot@nvidia.com \
    --cc=broonie@linaro.org \
    --cc=daniel.baluta@intel.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).