mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Bryan Wu <bryan.wu@analog.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Bryan Wu <bryan.wu@analog.com>,
	LKML <linux-kernel@vger.kernel.org>,
	Jeff Garzik <jeff@garzik.org>,
	David Brownell <dbrownell@users.sourceforge.net>,
	Greg Kroah-Hartman <greg@kroah.com>,
	Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [GIT PULL try#2] Blackfin update
Date: Thu, 26 Jul 2007 08:41:38 +0800	[thread overview]
Message-ID: <1185410498.13974.7.camel@roc-laptop> (raw)
In-Reply-To: <alpine.LFD.0.999.0707251125140.3607@woody.linux-foundation.org>

On Wed, 2007-07-25 at 11:26 -0700, Linus Torvalds wrote:
> 
> On Wed, 25 Jul 2007, Bryan Wu wrote:
> > 
> > Please pull from 'for-linus' branch of
> 
> This really is too big for post-rc1.
> 
> I realize that this is all blackfin-only, and that it doesn't matter from 
> a practical standpoint, but I want you guys to learn to follow the merge 
> window, and the only way I can do that is by enforcing it.
> 
> 			Linus

Exactly. In the 2.6.23-rc1 merge window, I am trying to submit blackfin
driver patches and other new stuffs. So put those bug fixing and some
small updates in this series.

I will review the series again, submit critical bug fixing in rc2 and
maybe split rest of them into following -rc.

Thanks Jeff, after using you script, I generate this big email. It's
beautiful but I missed merge window.

Thanks a lot
Best Regards,
- Bryan Wu

  reply	other threads:[~2007-07-26  0:41 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-25 15:26 Bryan Wu
2007-07-25 18:26 ` Linus Torvalds
2007-07-26  0:41   ` Bryan Wu [this message]
     [not found] ` <1185382018.1050.152.camel@localhost>
2007-07-26  6:10   ` Bryan Wu
2007-07-26  8:21 Hennerich, Michael

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=1185410498.13974.7.camel@roc-laptop \
    --to=bryan.wu@analog.com \
    --cc=akpm@linux-foundation.org \
    --cc=dbrownell@users.sourceforge.net \
    --cc=greg@kroah.com \
    --cc=jeff@garzik.org \
    --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
all inboxes | Powered by JetHome®