mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Grygorii Strashko <grygorii.strashko@ti.com>
To: Linus Walleij <linus.walleij@linaro.org>, <linux-gpio@vger.kernel.org>
Cc: <prabhakar.csengg@gmail.com>, <nsekhar@ti.com>,
	Santosh Shilimkar <santosh.shilimkar@ti.com>,
	<linux-kernel@vger.kernel.org>,
	Grygorii Strashko <grygorii.strashko@ti.com>
Subject: [PATCH 0/2] gpio: davinci: preparation fixes and updates to reuse it for Keystone
Date: Thu, 21 Nov 2013 17:34:34 +0200	[thread overview]
Message-ID: <1385048076-7875-1-git-send-email-grygorii.strashko@ti.com> (raw)

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(-)

-- 
1.7.9.5


             reply	other threads:[~2013-11-21 15:38 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-21 15:34 Grygorii Strashko [this message]
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 ` [PATCH 0/2] gpio: davinci: preparation fixes and updates to reuse it for Keystone Santosh Shilimkar

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=1385048076-7875-1-git-send-email-grygorii.strashko@ti.com \
    --to=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 \
    --cc=santosh.shilimkar@ti.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

all inboxes | Powered by JetHome®