From: Santosh Shilimkar <santosh.shilimkar@ti.com>
To: Linus Walleij <linus.walleij@linaro.org>,
yegorslists@googlemail.com, Kevin Hilman <khilman@linaro.org>
Cc: "linux-gpio@vger.kernel.org" <linux-gpio@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
Linux-OMAP <linux-omap@vger.kernel.org>,
ext Tony Lindgren <tony@atomide.com>
Subject: Re: [PATCH v3] gpio: omap: implement get_direction
Date: Thu, 24 Apr 2014 09:29:52 -0400 [thread overview]
Message-ID: <535911D0.3020907@ti.com> (raw)
In-Reply-To: <CACRpkdZPNGHNQhqovDoaKTXZT3mJfN4pjKSBxW7m6wT5u-XEYQ@mail.gmail.com>
On Thursday 24 April 2014 09:13 AM, Linus Walleij wrote:
> On Thu, Apr 24, 2014 at 8:57 AM, <yegorslists@googlemail.com> wrote:
>
>> From: Yegor Yefremov <yegorslists@googlemail.com>
>>
>> This patch implements gpio_chip's get_direction() routine, that
>> lets other drivers get particular GPIOs direction using
>> struct gpio_desc.
>>
>> Signed-off-by: Yegor Yefremov <yegorslists@googlemail.com>
>> Acked-by: Javier Martinez Canillas <javier@dowhile0.org>
>> ---
>> Changes:
>> v3: get rid of _get_gpio_direction() (Linus Walleij)
>> v2: rework return value calculation
>
> Looks good to me, Kevin, Santosh?
>
Looks fine to me as well.
Acked-by: Santosh Shilimkar <santosh.shilimkar@ti.com>
> Part of me wants to list Javier as maintainer for this driver.
>
Am ok with it as well.
WARNING: multiple messages have this Message-ID (diff)
From: santosh.shilimkar@ti.com (Santosh Shilimkar)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3] gpio: omap: implement get_direction
Date: Thu, 24 Apr 2014 09:29:52 -0400 [thread overview]
Message-ID: <535911D0.3020907@ti.com> (raw)
In-Reply-To: <CACRpkdZPNGHNQhqovDoaKTXZT3mJfN4pjKSBxW7m6wT5u-XEYQ@mail.gmail.com>
On Thursday 24 April 2014 09:13 AM, Linus Walleij wrote:
> On Thu, Apr 24, 2014 at 8:57 AM, <yegorslists@googlemail.com> wrote:
>
>> From: Yegor Yefremov <yegorslists@googlemail.com>
>>
>> This patch implements gpio_chip's get_direction() routine, that
>> lets other drivers get particular GPIOs direction using
>> struct gpio_desc.
>>
>> Signed-off-by: Yegor Yefremov <yegorslists@googlemail.com>
>> Acked-by: Javier Martinez Canillas <javier@dowhile0.org>
>> ---
>> Changes:
>> v3: get rid of _get_gpio_direction() (Linus Walleij)
>> v2: rework return value calculation
>
> Looks good to me, Kevin, Santosh?
>
Looks fine to me as well.
Acked-by: Santosh Shilimkar <santosh.shilimkar@ti.com>
> Part of me wants to list Javier as maintainer for this driver.
>
Am ok with it as well.
next prev parent reply other threads:[~2014-04-24 13:30 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-24 6:57 [PATCH v3] gpio: omap: implement get_direction yegorslists
2014-04-24 6:57 ` yegorslists at googlemail.com
2014-04-24 13:13 ` Linus Walleij
2014-04-24 13:13 ` Linus Walleij
2014-04-24 13:29 ` Santosh Shilimkar [this message]
2014-04-24 13:29 ` Santosh Shilimkar
2014-04-24 16:42 ` Tony Lindgren
2014-04-24 16:42 ` Tony Lindgren
2014-04-24 22:25 ` Kevin Hilman
2014-04-24 22:25 ` Kevin Hilman
2014-04-24 13:35 ` Linus Walleij
2014-04-24 13:35 ` Linus Walleij
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=535911D0.3020907@ti.com \
--to=santosh.shilimkar@ti.com \
--cc=khilman@linaro.org \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=tony@atomide.com \
--cc=yegorslists@googlemail.com \
/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.