From: Paul Mundt <lethal@linux-sh.org>
To: Bryan Wu <bryan.wu@analog.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [GIT PULL] Blackfin updates for 2.6.22-rc4
Date: Thu, 14 Jun 2007 11:36:49 +0900 [thread overview]
Message-ID: <20070614023649.GA21576@linux-sh.org> (raw)
In-Reply-To: <1181786785.21995.5.camel@roc-desktop>
On Thu, Jun 14, 2007 at 10:06:25AM +0800, Bryan Wu wrote:
> 107 files changed, 7034 insertions(+), 3557 deletions(-)
This has new platform support, new drivers, and so on. None of which is
suitable outside of -rc1-2. You are aware of this thing called the merge
window?
Try splitting out the critical bugfixes in to a different tree and have
that pulled for the next -rc, if you expect to get any of the fixes
merged for 2.6.22.
next prev parent reply other threads:[~2007-06-14 2:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-14 2:06 [GIT PULL] Blackfin updates for 2.6.22-rc4 Bryan Wu
2007-06-14 2:36 ` Paul Mundt [this message]
2007-06-14 2:57 ` Jeff Garzik
-- strict thread matches above, loose matches on Subject: below --
2007-06-14 7:09 Bryan Wu
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=20070614023649.GA21576@linux-sh.org \
--to=lethal@linux-sh.org \
--cc=bryan.wu@analog.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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