linux-kernel - Re: [PATCH 2/2] gpio/omap: add *remove* callback in platform

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <87ipdnein1.fsf@ti.com>
Date:	Mon, 16 Jul 2012 10:10:58 -0700
From:	Kevin Hilman <khilman@...com>
To:	Linus Walleij <linus.walleij@...aro.org>
Cc:	Tarun Kanti DebBarma <tarun.kanti@...com>,
	linux-omap@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
	linux-kernel@...r.kernel.org, Rajendra Nayak <rnayak@...com>,
	Santosh Shilimkar <santosh.shilimkar@...com>,
	"Cousson\, Benoit" <b-cousson@...com>,
	Paul Walmsley <paul@...an.com>
Subject: Re: [PATCH 2/2] gpio/omap: add *remove* callback in platform_driver

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

> On Thu, Jul 12, 2012 at 7:48 PM, Kevin Hilman <khilman@...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@...com>
>> - Rajendra Nayak <rnayak@...com>
>> - Benoit Cousson <b-cousson@...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@...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@...retlab.ca>
Cc: Linus Walleij <linus.walleij@...aro.org>
Cc: Santosh Shilimkar <santosh.shilimkar@...com>
Cc: Andrew Morton <akpm@...ux-foundation.org>
Signed-off-by: Kevin Hilman <khilman@...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@...com>
+M:	Kevin Hilman <khilman@...com>
+L:	linux-omap@...r.kernel.org
+S:	Maintained
+F:	drivers/gpio/gpio.omap.c
+
 OMFS FILESYSTEM
 M:	Bob Copeland <me@...copeland.com>
 L:	linux-karma-devel@...ts.sourceforge.net
-- 
1.7.9.2

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/