All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arnd Bergmann <arnd@arndb.de>
To: Tony Lindgren <tony@atomide.com>
Cc: linux-arm-kernel@lists.infradead.org, linux-omap@vger.kernel.org,
	Nicolas Pitre <nico@fluxnic.net>,
	Thomas Gleixner <tglx@linutronix.de>
Subject: Re: Remaining omap pull requests
Date: Tue, 12 Jul 2011 00:16:12 +0200	[thread overview]
Message-ID: <201107120016.12366.arnd@arndb.de> (raw)
In-Reply-To: <20110711114736.GX5783@atomide.com>

On Monday 11 July 2011, Tony Lindgren wrote:
> Hi Arnd,
> 
> Below is a summary of the pending omap pull requests as there are still
> few branches pending.
> 
> Can you please take a look and see what you can take of these for v3.1
> merge window?
> 
> There's still quite a bit more code shrinkage, and the new code for 4460
> and PRCM related changes are badly needed.

I've pulled everything now, please check if it looks ok to you.

I haven't really looked at the patches much, I hope that I have time
to at least do some test builds and take a very rough look at the
contents tomorrow.

Thanks for the detailed descriptions, and for splitting it
into good-sized series.

	Arnd

WARNING: multiple messages have this Message-ID (diff)
From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: Remaining omap pull requests
Date: Tue, 12 Jul 2011 00:16:12 +0200	[thread overview]
Message-ID: <201107120016.12366.arnd@arndb.de> (raw)
In-Reply-To: <20110711114736.GX5783@atomide.com>

On Monday 11 July 2011, Tony Lindgren wrote:
> Hi Arnd,
> 
> Below is a summary of the pending omap pull requests as there are still
> few branches pending.
> 
> Can you please take a look and see what you can take of these for v3.1
> merge window?
> 
> There's still quite a bit more code shrinkage, and the new code for 4460
> and PRCM related changes are badly needed.

I've pulled everything now, please check if it looks ok to you.

I haven't really looked at the patches much, I hope that I have time
to at least do some test builds and take a very rough look at the
contents tomorrow.

Thanks for the detailed descriptions, and for splitting it
into good-sized series.

	Arnd

  parent reply	other threads:[~2011-07-11 22:16 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-11 11:47 Remaining omap pull requests Tony Lindgren
2011-07-11 11:47 ` Tony Lindgren
2011-07-11 11:49 ` [GIT PULL] omap cleanup for v3.1 merge window, part 3 Tony Lindgren
2011-07-11 11:50 ` [GIT PULL] omap fixes for v3.1 merge window, part 2 Tony Lindgren
2011-07-11 11:53 ` [GIT PULL] omap related MFD and ASoC patches for v3.1 merge window Tony Lindgren
2011-07-11 11:53   ` Tony Lindgren
2011-07-11 22:16 ` Arnd Bergmann [this message]
2011-07-11 22:16   ` Remaining omap pull requests Arnd Bergmann
2011-07-13  6:16   ` Tony Lindgren
2011-07-13  6:16     ` Tony Lindgren
2011-08-02 23:14     ` Kevin Hilman
2011-08-02 23:14       ` Kevin Hilman
2011-08-03  0:06       ` Kevin Hilman
2011-08-03  0:06         ` Kevin Hilman
2011-08-10 12:21         ` Tony Lindgren
2011-08-10 12:21           ` Tony Lindgren
2011-08-16 14:07           ` Arnd Bergmann
2011-08-16 14:07             ` Arnd Bergmann
2011-07-12  8:41 ` Jan Weitzel
2011-07-12  8:41   ` Jan Weitzel
2011-07-13  6:25   ` Tony Lindgren
2011-07-13  6:25     ` Tony Lindgren

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=201107120016.12366.arnd@arndb.de \
    --to=arnd@arndb.de \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=nico@fluxnic.net \
    --cc=tglx@linutronix.de \
    --cc=tony@atomide.com \
    /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.