devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Rob Herring <rob.herring@calxeda.com>
To: Grant Likely <grant.likely@secretlab.ca>
Cc: Linus Walleij <linus.walleij@linaro.org>,
	Wolfram Sang <w.sang@pengutronix.de>,
	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: Sun, 01 Jul 2012 23:04:24 -0500	[thread overview]
Message-ID: <4FF11DC8.7080908@calxeda.com> (raw)
In-Reply-To: <CACxGe6tyO5u7eiq1OiPX-u439YAcQDFz3eOOGZ4bNPtwmYwNkg@mail.gmail.com>

Grant,

On 07/01/2012 07:49 PM, Grant Likely wrote:
> Hi Wolfram, Rob & Linus W.
> 
> I believe all three of you know that I'm in the process of moving to
> Scotland. The house is on the market and we have flights booked for
> the end of July.

Cool!

> The problem is that the move is becoming so much work that I barely
> have time to sit down with the computer, let alone handle patches. It
> probably isn't going to get any better either until the kids are
> settled in their new school (mid August).  I need help to prepare for
> 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
> may even need you to send pull requests to Linus when the window opens
> if I'm still under water.

No problem. I am going on vacation the last part of July, but should be
online off and on. There hasn't been too much that needs to be merged
thru DT tree. I have been queuing up a few things, but hadn't yet
replied on them as my last pull request hadn't been pulled.

> Also, if you have any bug fixes that need to go into v3.5, go ahead
> and send them on to Linus directly (Rob, I think I saw a pull request
> from you).

Yes, will do.

> Things will definitely be better after the move is finished and
> ksummit/plumbers is over.  Until then, thanks in advance for anything
> you can do to help with the load.

See you in San Diego and good luck with the move.

Rob

  reply	other threads:[~2012-07-02  4:04 UTC|newest]

Thread overview: 5+ 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  4:04 ` Rob Herring [this message]
     [not found] ` <CACxGe6tyO5u7eiq1OiPX-u439YAcQDFz3eOOGZ4bNPtwmYwNkg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2012-07-04 23:30   ` Linus Walleij
2012-07-05 20:09 ` Wolfram Sang
2012-07-06 18:01   ` Mark Brown

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=4FF11DC8.7080908@calxeda.com \
    --to=rob.herring@calxeda.com \
    --cc=devicetree-discuss@ozlabs.org \
    --cc=grant.likely@secretlab.ca \
    --cc=linus.walleij@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).