From: Santosh Shilimkar <santosh.shilimkar@ti.com>
To: Grygorii Strashko <grygorii.strashko@ti.com>
Cc: Linus Walleij <linus.walleij@linaro.org>,
<linux-gpio@vger.kernel.org>, <prabhakar.csengg@gmail.com>,
<nsekhar@ti.com>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 0/2] gpio: davinci: preparation fixes and updates to reuse it for Keystone
Date: Fri, 29 Nov 2013 10:41:30 -0500 [thread overview]
Message-ID: <5298B5AA.8030301@ti.com> (raw)
In-Reply-To: <1385048076-7875-1-git-send-email-grygorii.strashko@ti.com>
On Thursday 21 November 2013 10:34 AM, Grygorii Strashko wrote:
> This series is a preparation step for reusing Davinci GPIO driver
> for Keystone SoCs.
> And it's been created in order to break the strict dependency of
> Davinci GPIO driver from Davinci platform code.
>
> Based on patch:
> http://www.spinics.net/lists/kernel/msg1632405.html
>
> Grygorii Strashko (2):
> gpio: davinci: get rid of DAVINCI_N_GPIO
> gpio: introduce GPIO_DAVINCI kconfig option
>
> drivers/gpio/Kconfig | 7 +++++++
> drivers/gpio/Makefile | 2 +-
> drivers/gpio/gpio-davinci.c | 4 ++--
> 3 files changed, 10 insertions(+), 3 deletions(-)
>
Thanks Grygorii and clean-up is inline as discussed off-list.
FWIW,
Acked-by: Santosh Shilimkar <santosh.shilimkar@ti.com>
prev parent reply other threads:[~2013-11-29 15:41 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-21 15:34 [PATCH 0/2] gpio: davinci: preparation fixes and updates to reuse it for Keystone Grygorii Strashko
2013-11-21 15:34 ` [PATCH 1/2] gpio: davinci: get rid of DAVINCI_N_GPIO Grygorii Strashko
2013-11-26 10:27 ` Prabhakar Lad
2013-11-29 8:33 ` Linus Walleij
2013-12-15 11:57 ` Sekhar Nori
2013-11-21 15:34 ` [PATCH 2/2] gpio: introduce GPIO_DAVINCI kconfig option Grygorii Strashko
2013-11-26 10:29 ` Prabhakar Lad
2013-11-29 8:35 ` Linus Walleij
2013-12-15 12:04 ` Sekhar Nori
2013-11-29 15:41 ` Santosh Shilimkar [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=5298B5AA.8030301@ti.com \
--to=santosh.shilimkar@ti.com \
--cc=grygorii.strashko@ti.com \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nsekhar@ti.com \
--cc=prabhakar.csengg@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox