All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Wolfram Sang <w.sang@pengutronix.de>
Cc: Grant Likely <grant.likely@secretlab.ca>,
	Robert Herring <rob.herring@calxeda.com>,
	Linus Walleij <linus.walleij@linaro.org>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	spi-devel-general-request@lists.sourceforge.net,
	devicetree-discuss <devicetree-discuss@ozlabs.org>
Subject: Re: SPI, GPIO, and DT maintainer ship (cry for help)
Date: Fri, 6 Jul 2012 19:01:52 +0100	[thread overview]
Message-ID: <20120706180152.GA30152@sirena.org.uk> (raw)
In-Reply-To: <20120705200917.GA15639@pengutronix.de>

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

      reply	other threads:[~2012-07-06 18:02 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-02  0:49 SPI, GPIO, and DT maintainer ship (cry for help) Grant Likely
2012-07-02  0:49 ` Grant Likely
2012-07-02  4:04 ` Rob Herring
2012-07-04 23:30 ` Linus Walleij
2012-07-04 23:30   ` Linus Walleij
2012-07-05 20:09 ` Wolfram Sang
2012-07-06 18:01   ` Mark Brown [this message]

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=20120706180152.GA30152@sirena.org.uk \
    --to=broonie@opensource.wolfsonmicro.com \
    --cc=devicetree-discuss@ozlabs.org \
    --cc=grant.likely@secretlab.ca \
    --cc=linus.walleij@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rob.herring@calxeda.com \
    --cc=spi-devel-general-request@lists.sourceforge.net \
    --cc=torvalds@linux-foundation.org \
    --cc=w.sang@pengutronix.de \
    /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.