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: omap code merged to mainline, fixes only for -rc, no more -omap releases
Date: Tue, 2 Mar 2010 12:27:47 -0800	[thread overview]
Message-ID: <20100302202747.GJ7393@atomide.com> (raw)

Hi all,

Linus just pulled our code for 2.6.34, so let's now concentrate
on the fixes for for 2.6.34 -rc cycle.

So no more new code please except for the 2.6.35 merge window.

It seems like we can send about 1/3 of all the patches during
the -rc cycle as fixes, so please tweak the patches accordingly
if you want them in during the -rc cycle. For the fixes, please
specify what it fixes in the patch description. And please have
the magic word "fix" somewhere in the patch subject too.

For the patches going into 2.6.35 merge window, we need to have
those tested and integrated in linux-omap master branch by
2.6.34-rc6 or so.

I'll be rebuilding linux-omap master branch again today on top
of the current code from Linus. I will not tag 2.6.33-omap1 or
anything like that as 2.6.33 _mainline_ tree is our stable tree.

So please base any products and distros on the _mainline_ recent
stable version, currently 2.6.33, and apply the patches you need
on top of it. I guess that's mostly Kevin's PM branch and Tomi's
DSS2 branch that you might want to apply.

This way we are following the standard Linux development cycle.

Also, I'll be taking few days off starting Wednesday :)

Regards,

Tony

                 reply	other threads:[~2010-03-02 20:26 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20100302202747.GJ7393@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