mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Bryan Wu" <cooloney.lkml@gmail.com>
To: "Pekka Enberg" <penberg@cs.helsinki.fi>
Cc: "Michal Simek" <simekm2@fel.cvut.cz>,
	linux-kernel@vger.kernel.org, monstr@monstr.eu
Subject: Re: New linux arch
Date: Tue, 8 Jan 2008 17:00:37 +0800	[thread overview]
Message-ID: <386072610801080100w30b7c6dar773e47de1472a030@mail.gmail.com> (raw)
In-Reply-To: <84144f020801080049r487690ffv9f49c68160b205d2@mail.gmail.com>

On Jan 8, 2008 4:49 PM, Pekka Enberg <penberg@cs.helsinki.fi> wrote:
> Hi Bryan,
>
> On Jan 8, 2008 10:28 AM, Bryan Wu <cooloney.lkml@gmail.com> wrote:
> > 1. Push patches to LKML when merge window open (2 weeks after a stable
> > kernel version release, for example 2 weeks after 2.6.24 released)
>
> You shouldn't wait for the merge window to open to send patches for
> review for the first time; otherwise you'll just miss the opportunity
> to merge ;-).
>

Really? I was told before to send out big patch to LKML for the merge window.
If not, it's good news for Michal and MicroBlaze guys.

Thanks
-Bryan Wu

  reply	other threads:[~2008-01-08  9:00 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-07 11:29 Michal Simek
2008-01-07 12:34 ` Sam Ravnborg
2008-01-07 12:51   ` Michal Simek
2008-01-07 19:16     ` Sam Ravnborg
2008-01-07 12:47 ` Pekka Enberg
2008-01-07 13:00   ` Michal Simek
2008-01-07 13:12     ` Pekka Enberg
2008-01-07 13:34   ` Jan Engelhardt
2008-01-07 17:26     ` Stefan Richter
2008-01-07 17:39       ` Jan Engelhardt
2008-01-07 17:54         ` H. Peter Anvin
2008-01-07 18:20   ` Stefan Richter
2008-01-07 22:00 ` Benjamin Herrenschmidt
2008-01-07 22:39   ` Michal Simek
2008-01-08  8:28 ` Bryan Wu
2008-01-08  8:49   ` Pekka Enberg
2008-01-08  9:00     ` Bryan Wu [this message]
2008-01-08 17:05       ` Stefan Richter
2008-01-08 17:12   ` Stefan Richter
2008-01-09  1:16 ` Arnd Bergmann

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=386072610801080100w30b7c6dar773e47de1472a030@mail.gmail.com \
    --to=cooloney.lkml@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=monstr@monstr.eu \
    --cc=penberg@cs.helsinki.fi \
    --cc=simekm2@fel.cvut.cz \
    /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®