linux-kernel - Re: [PATCH] GPIOLIB: Allow GPIOs to be named

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]

Date:	Fri, 13 Mar 2009 09:43:49 +0000
From:	Daniel Silverstone <dsilvers@...tec.co.uk>
To:	Andrew Morton <akpm@...ux-foundation.org>
Cc:	linux-kernel@...r.kernel.org, David Brownell <david-b@...bell.net>
Subject: Re: [PATCH] GPIOLIB: Allow GPIOs to be named

On Thu, 2009-03-05 at 12:27 +0000, Daniel Silverstone wrote:
> > > I was unable to find anything in MAINTAINERS or at the top of gpiolib.c
> > > to indicate who to CC, hence sending this only to the list. Below is a
> > > patch against 2150edc6c5cf00f7adb54538b9ea2a3e9cedca3f.
> > gpio core is developed/maintained by David Brownell.  Who owes us a
> > MAINTAINERS update ;)
> David, have you had a chance to review this patch? It was also
> added-to-mm on the 13th Jan as gpiolib-allow-gpios-to-be-named.patch --
> I believe you were CCed on this add.
> With -rc8 looming, I am anxious to know if this is acceptable for going
> into the .30 merge window.

Andrew,

with -rc8 out, and David apparently MIA on this topic, is now an
appropriate time for me to ask that you queue this up for the .30 merge
window, or is that something you can't really do?

Regards,

Daniel.

-- 
Daniel Silverstone                              http://www.simtec.co.uk/
PGP mail accepted and encouraged.            Key Id: 2BC8 4016 2068 7895


--
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/