public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: Tony Lindgren <tony@atomide.com>
To: linux-omap@vger.kernel.org
Subject: Merge plans for 2.6.33 merge window
Date: Thu, 3 Dec 2009 09:36:00 -0800	[thread overview]
Message-ID: <20091203173559.GR4348@atomide.com> (raw)

Hi all,

As 2.6.32 is out, I'm planning to send Linus a pull request
for the code we have currently in for-next. That's already
a huge pile of code with the 7xx merge, header move, and
ioremap changes, pm etc:

Then I'll pile up another set of changes for next week
for a second round.

We should try to get in the clock framework changes,
especially clock framework for omap4. And the new mux
framework. Then there are some new board files, like
touchbook and various fixes.

Just FYI in case you're wondering why I'm not merging
recently posted code right now.

Regards,

Tony

             reply	other threads:[~2009-12-03 17:35 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-03 17:36 Tony Lindgren [this message]
2009-12-03 18:28 ` Merge plans for 2.6.33 merge window Pandita, Vikram
2009-12-03 18:44   ` Tony Lindgren
2009-12-03 19:58     ` Pandita, Vikram
2009-12-03 22:09 ` Cory Maccarrone
2009-12-03 22:13   ` 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=20091203173559.GR4348@atomide.com \
    --to=tony@atomide.com \
    --cc=linux-omap@vger.kernel.org \
    /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