All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: Greg Ungerer <gerg@snapgear.com>
Cc: torvalds@linux-foundation.org, gerg@uclinux.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] m68knommu: ColdFire add support for kernel preemption
Date: Thu, 1 May 2008 14:33:36 -0700	[thread overview]
Message-ID: <20080501143336.552e39e1.akpm@linux-foundation.org> (raw)
In-Reply-To: <200805010216.m412GT6t004096@goober>

On Thu, 1 May 2008 12:16:29 +1000
Greg Ungerer <gerg@snapgear.com> wrote:

> Subject: [PATCH] m68knommu: ColdFire add support for kernel preemption

Please find a way to get your patch queue into linux-next so that others
get some visibility into what you're brewing earlier than
last-day-of-the-merge-window?

Also, when emailing patches like this I do think that it's best that they
be sequence-numbered, even if they are all non-overlapping and unrelated. 
Because it allows the recipient to check that none got lost.

Thanks.

  reply	other threads:[~2008-05-01 21:34 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-01  2:16 [PATCH] m68knommu: ColdFire add support for kernel preemption Greg Ungerer
2008-05-01 21:33 ` Andrew Morton [this message]
2008-05-02  7:19   ` Greg Ungerer
2008-05-02  8:37     ` Sebastian Siewior
2008-05-02 12:22       ` Andrew Morton
2008-06-23  5:32         ` Greg Ungerer
2008-06-23  5:51           ` Andrew Morton
2008-06-23  7:53             ` Stephen Rothwell
2008-06-23 13:23               ` Greg Ungerer
2008-06-23 17:42                 ` Andrew Morton
2008-06-23 23:47                 ` Stephen Rothwell

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=20080501143336.552e39e1.akpm@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=gerg@snapgear.com \
    --cc=gerg@uclinux.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.