linux-kernel - Re: SPI, GPIO, and DT maintainer ship (cry for help)

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 for Android: free password hash cracker in your pocket

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

Message-ID: <20120706180152.GA30152@sirena.org.uk>
Date:	Fri, 6 Jul 2012 19:01:52 +0100
From:	Mark Brown <broonie@...nsource.wolfsonmicro.com>
To:	Wolfram Sang <w.sang@...gutronix.de>
Cc:	Grant Likely <grant.likely@...retlab.ca>,
	Robert Herring <rob.herring@...xeda.com>,
	Linus Walleij <linus.walleij@...aro.org>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	spi-devel-general-request@...ts.sourceforge.net,
	devicetree-discuss <devicetree-discuss@...abs.org>
Subject: Re: SPI, GPIO, and DT maintainer ship (cry for help)

On Thu, Jul 05, 2012 at 10:09:17PM +0200, Wolfram Sang wrote:
> Hi Grant,

> > the next merge window, and quite possibly the next window.  Since you
> > three have agreed to co-maintain those subsystems with me, can you
> > please take a look at the patches that have been posted, pick up the
> > ones that look ready to go to you, and get them into linux-next?  I

> Though I'd like to help out, I need to pass on this time. My resources
> simply won't allow to do the job (with the quality I envision, that is).
> I hope somebody else can jump in? If not, I can collect urgent patches,
> at least.

I could probably help out with SPI if that's useful (GPIO seems already
covered by Linus W)?
--
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/