All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kevin Hilman <khilman@ti.com>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: Tarun Kanti DebBarma <tarun.kanti@ti.com>,
	linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org, Rajendra Nayak <rnayak@ti.com>,
	Santosh Shilimkar <santosh.shilimkar@ti.com>, "Cousson\,
	Benoit" <b-cousson@ti.com>, Paul Walmsley <paul@pwsan.com>
Subject: Re: [PATCH 2/2] gpio/omap: add *remove* callback in platform_driver
Date: Mon, 16 Jul 2012 10:10:58 -0700	[thread overview]
Message-ID: <87ipdnein1.fsf@ti.com> (raw)
In-Reply-To: <CACRpkdZxUpQ=a-yQ8b4bnX3S9penPWkxJ+PG2Zi4i9YZibYRiw@mail.gmail.com> (Linus Walleij's message of "Sat, 14 Jul 2012 22:51:44 +0200")

Linus Walleij <linus.walleij@linaro.org> writes:

> On Thu, Jul 12, 2012 at 7:48 PM, Kevin Hilman <khilman@ti.com> wrote:
>
>> In the case of OMAP GPIO, unless it's an obvious fix, I would recommend
>> you wait at least until you see some acks/tested tags from any of
>>
>> - Santosh Shilimkar <santosh.shilimkar@ti.com>
>> - Rajendra Nayak <rnayak@ti.com>
>> - Benoit Cousson <b-cousson@ti.com>
>>
>> or Tony, Paul or myself.
>
> Instead of trying to store this information in my and Grants brains and
> us forgetting it, what about patching MAINTAINERS to reflect the fact
> instead? That's better I think, plus I use that file a lot.
>
>> For major series, I have been collecting/queueing them for Grant after
>> ensuring they have been well reviewed and well tested (although I am
>> eagerly hoping to hand off this role to someone else.)
>
> Listing it under your GIT tree in MAINTAINERS for this driver will make
> this work better I think.
>
> One path for OMAP GPIO patches, simple. It's obviously the
> ambiguity that cause the trouble. Then you can also decide
> on each cycle whether to send these to GPIO or ARM SoC
> etc.

Yeah, I understand the process, but I've been avoiding doing that
because, well, I don't want the job.  I have been trying to get someone
else at TI to maintain this driver, but have not been successful.

So, until that happens, feel free to queue up the patch below.

Santosh, note that I've put you as co-maintainer of this driver.

Kevin


>From c429e2e98ea7add98b85a47483ca7126284b22e6 Mon Sep 17 00:00:00 2001
From: Kevin Hilman <khilman@ti.com>
Date: Mon, 16 Jul 2012 10:05:07 -0700
Subject: [PATCH] MAINTAINERS: add entry OMAP GPIO driver

Since I've been maintaining this, making it official at the request of the
GPIO maintainers.

Cc: Grant Likely <grant.likely@secretlab.ca>
Cc: Linus Walleij <linus.walleij@linaro.org>
Cc: Santosh Shilimkar <santosh.shilimkar@ti.com>
Cc: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Kevin Hilman <khilman@ti.com>
---
 MAINTAINERS |    7 +++++++
 1 file changed, 7 insertions(+)

diff --git a/MAINTAINERS b/MAINTAINERS
index 03df1d1..61d117a 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -4943,6 +4943,13 @@ S:	Maintained
 F:	drivers/usb/*/*omap*
 F:	arch/arm/*omap*/usb*
 
+OMAP GPIO DRIVER
+M:	Santosh Shilimkar <santosh.shilimkar@ti.com>
+M:	Kevin Hilman <khilman@ti.com>
+L:	linux-omap@vger.kernel.org
+S:	Maintained
+F:	drivers/gpio/gpio.omap.c
+
 OMFS FILESYSTEM
 M:	Bob Copeland <me@bobcopeland.com>
 L:	linux-karma-devel@lists.sourceforge.net
-- 
1.7.9.2


WARNING: multiple messages have this Message-ID (diff)
From: Kevin Hilman <khilman@ti.com>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: Tarun Kanti DebBarma <tarun.kanti@ti.com>,
	linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org, Rajendra Nayak <rnayak@ti.com>,
	Santosh Shilimkar <santosh.shilimkar@ti.com>,
	"Cousson, Benoit" <b-cousson@ti.com>,
	Paul Walmsley <paul@pwsan.com>
Subject: Re: [PATCH 2/2] gpio/omap: add *remove* callback in platform_driver
Date: Mon, 16 Jul 2012 10:10:58 -0700	[thread overview]
Message-ID: <87ipdnein1.fsf@ti.com> (raw)
In-Reply-To: <CACRpkdZxUpQ=a-yQ8b4bnX3S9penPWkxJ+PG2Zi4i9YZibYRiw@mail.gmail.com> (Linus Walleij's message of "Sat, 14 Jul 2012 22:51:44 +0200")

Linus Walleij <linus.walleij@linaro.org> writes:

> On Thu, Jul 12, 2012 at 7:48 PM, Kevin Hilman <khilman@ti.com> wrote:
>
>> In the case of OMAP GPIO, unless it's an obvious fix, I would recommend
>> you wait at least until you see some acks/tested tags from any of
>>
>> - Santosh Shilimkar <santosh.shilimkar@ti.com>
>> - Rajendra Nayak <rnayak@ti.com>
>> - Benoit Cousson <b-cousson@ti.com>
>>
>> or Tony, Paul or myself.
>
> Instead of trying to store this information in my and Grants brains and
> us forgetting it, what about patching MAINTAINERS to reflect the fact
> instead? That's better I think, plus I use that file a lot.
>
>> For major series, I have been collecting/queueing them for Grant after
>> ensuring they have been well reviewed and well tested (although I am
>> eagerly hoping to hand off this role to someone else.)
>
> Listing it under your GIT tree in MAINTAINERS for this driver will make
> this work better I think.
>
> One path for OMAP GPIO patches, simple. It's obviously the
> ambiguity that cause the trouble. Then you can also decide
> on each cycle whether to send these to GPIO or ARM SoC
> etc.

Yeah, I understand the process, but I've been avoiding doing that
because, well, I don't want the job.  I have been trying to get someone
else at TI to maintain this driver, but have not been successful.

So, until that happens, feel free to queue up the patch below.

Santosh, note that I've put you as co-maintainer of this driver.

Kevin


>From c429e2e98ea7add98b85a47483ca7126284b22e6 Mon Sep 17 00:00:00 2001
From: Kevin Hilman <khilman@ti.com>
Date: Mon, 16 Jul 2012 10:05:07 -0700
Subject: [PATCH] MAINTAINERS: add entry OMAP GPIO driver

Since I've been maintaining this, making it official at the request of the
GPIO maintainers.

Cc: Grant Likely <grant.likely@secretlab.ca>
Cc: Linus Walleij <linus.walleij@linaro.org>
Cc: Santosh Shilimkar <santosh.shilimkar@ti.com>
Cc: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Kevin Hilman <khilman@ti.com>
---
 MAINTAINERS |    7 +++++++
 1 file changed, 7 insertions(+)

diff --git a/MAINTAINERS b/MAINTAINERS
index 03df1d1..61d117a 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -4943,6 +4943,13 @@ S:	Maintained
 F:	drivers/usb/*/*omap*
 F:	arch/arm/*omap*/usb*
 
+OMAP GPIO DRIVER
+M:	Santosh Shilimkar <santosh.shilimkar@ti.com>
+M:	Kevin Hilman <khilman@ti.com>
+L:	linux-omap@vger.kernel.org
+S:	Maintained
+F:	drivers/gpio/gpio.omap.c
+
 OMFS FILESYSTEM
 M:	Bob Copeland <me@bobcopeland.com>
 L:	linux-karma-devel@lists.sourceforge.net
-- 
1.7.9.2


WARNING: multiple messages have this Message-ID (diff)
From: khilman@ti.com (Kevin Hilman)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/2] gpio/omap: add *remove* callback in platform_driver
Date: Mon, 16 Jul 2012 10:10:58 -0700	[thread overview]
Message-ID: <87ipdnein1.fsf@ti.com> (raw)
In-Reply-To: <CACRpkdZxUpQ=a-yQ8b4bnX3S9penPWkxJ+PG2Zi4i9YZibYRiw@mail.gmail.com> (Linus Walleij's message of "Sat, 14 Jul 2012 22:51:44 +0200")

Linus Walleij <linus.walleij@linaro.org> writes:

> On Thu, Jul 12, 2012 at 7:48 PM, Kevin Hilman <khilman@ti.com> wrote:
>
>> In the case of OMAP GPIO, unless it's an obvious fix, I would recommend
>> you wait at least until you see some acks/tested tags from any of
>>
>> - Santosh Shilimkar <santosh.shilimkar@ti.com>
>> - Rajendra Nayak <rnayak@ti.com>
>> - Benoit Cousson <b-cousson@ti.com>
>>
>> or Tony, Paul or myself.
>
> Instead of trying to store this information in my and Grants brains and
> us forgetting it, what about patching MAINTAINERS to reflect the fact
> instead? That's better I think, plus I use that file a lot.
>
>> For major series, I have been collecting/queueing them for Grant after
>> ensuring they have been well reviewed and well tested (although I am
>> eagerly hoping to hand off this role to someone else.)
>
> Listing it under your GIT tree in MAINTAINERS for this driver will make
> this work better I think.
>
> One path for OMAP GPIO patches, simple. It's obviously the
> ambiguity that cause the trouble. Then you can also decide
> on each cycle whether to send these to GPIO or ARM SoC
> etc.

Yeah, I understand the process, but I've been avoiding doing that
because, well, I don't want the job.  I have been trying to get someone
else at TI to maintain this driver, but have not been successful.

So, until that happens, feel free to queue up the patch below.

Santosh, note that I've put you as co-maintainer of this driver.

Kevin


>From c429e2e98ea7add98b85a47483ca7126284b22e6 Mon Sep 17 00:00:00 2001
From: Kevin Hilman <khilman@ti.com>
Date: Mon, 16 Jul 2012 10:05:07 -0700
Subject: [PATCH] MAINTAINERS: add entry OMAP GPIO driver

Since I've been maintaining this, making it official at the request of the
GPIO maintainers.

Cc: Grant Likely <grant.likely@secretlab.ca>
Cc: Linus Walleij <linus.walleij@linaro.org>
Cc: Santosh Shilimkar <santosh.shilimkar@ti.com>
Cc: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Kevin Hilman <khilman@ti.com>
---
 MAINTAINERS |    7 +++++++
 1 file changed, 7 insertions(+)

diff --git a/MAINTAINERS b/MAINTAINERS
index 03df1d1..61d117a 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -4943,6 +4943,13 @@ S:	Maintained
 F:	drivers/usb/*/*omap*
 F:	arch/arm/*omap*/usb*
 
+OMAP GPIO DRIVER
+M:	Santosh Shilimkar <santosh.shilimkar@ti.com>
+M:	Kevin Hilman <khilman@ti.com>
+L:	linux-omap at vger.kernel.org
+S:	Maintained
+F:	drivers/gpio/gpio.omap.c
+
 OMFS FILESYSTEM
 M:	Bob Copeland <me@bobcopeland.com>
 L:	linux-karma-devel at lists.sourceforge.net
-- 
1.7.9.2

  reply	other threads:[~2012-07-16 17:10 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-11  9:13 [PATCH 0/2] gpio/omap: few code realignment and update of missing code Tarun Kanti DebBarma
2012-07-11  9:13 ` Tarun Kanti DebBarma
2012-07-11  9:13 ` Tarun Kanti DebBarma
2012-07-11  9:13 ` [PATCH 1/2] gpio/omap: move bank->dbck initialization to omap_gpio_mod_init() Tarun Kanti DebBarma
2012-07-11  9:13   ` Tarun Kanti DebBarma
2012-07-11  9:13   ` Tarun Kanti DebBarma
2012-07-11 17:51   ` Paul Walmsley
2012-07-11 17:51     ` Paul Walmsley
2012-07-11 17:56     ` DebBarma, Tarun Kanti
2012-07-11 17:56       ` DebBarma, Tarun Kanti
2012-07-11 21:51   ` Linus Walleij
2012-07-11 21:51     ` Linus Walleij
2012-07-11  9:13 ` [PATCH 2/2] gpio/omap: add *remove* callback in platform_driver Tarun Kanti DebBarma
2012-07-11  9:13   ` Tarun Kanti DebBarma
2012-07-11  9:13   ` Tarun Kanti DebBarma
2012-07-11 21:54   ` Linus Walleij
2012-07-11 21:54     ` Linus Walleij
2012-07-11 23:25   ` Kevin Hilman
2012-07-11 23:25     ` Kevin Hilman
2012-07-11 23:25     ` Kevin Hilman
2012-07-12 11:03     ` Linus Walleij
2012-07-12 11:03       ` Linus Walleij
2012-07-12 17:48       ` Kevin Hilman
2012-07-12 17:48         ` Kevin Hilman
2012-07-12 17:48         ` Kevin Hilman
2012-07-14 20:51         ` Linus Walleij
2012-07-14 20:51           ` Linus Walleij
2012-07-16 17:10           ` Kevin Hilman [this message]
2012-07-16 17:10             ` Kevin Hilman
2012-07-16 17:10             ` Kevin Hilman
2012-07-16 20:49             ` Linus Walleij
2012-07-16 20:49               ` Linus Walleij
2012-07-16 22:01               ` Kevin Hilman
2012-07-16 22:01                 ` Kevin Hilman
2012-07-16 22:01                 ` Kevin Hilman
2012-07-17  6:03             ` Shilimkar, Santosh
2012-07-17  6:03               ` Shilimkar, Santosh

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=87ipdnein1.fsf@ti.com \
    --to=khilman@ti.com \
    --cc=b-cousson@ti.com \
    --cc=linus.walleij@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=paul@pwsan.com \
    --cc=rnayak@ti.com \
    --cc=santosh.shilimkar@ti.com \
    --cc=tarun.kanti@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 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.