All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: Greg Ungerer <gerg@snapgear.com>
Cc: linux-kernel@vger.kernel.org, linux-next@vger.kernel.org,
	Stephen Rothwell <sfr@canb.auug.org.au>
Subject: Re: [PATCH] m68knommu: ColdFire add support for kernel preemption
Date: Sun, 22 Jun 2008 22:51:02 -0700	[thread overview]
Message-ID: <20080622225102.5117f22b.akpm@linux-foundation.org> (raw)
In-Reply-To: <485F3585.2080606@snapgear.com>

On Mon, 23 Jun 2008 15:32:53 +1000 Greg Ungerer <gerg@snapgear.com> wrote:

> Hi Andrew,
> 
> Andrew Morton wrote:
> > On Fri, 2 May 2008 10:37:55 +0200 Sebastian Siewior <lkml@ml.breakpoint.cc> 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?
> >>> Is a git tree the only way?
> >> Others (Greg KH for instance, i2c) have quilt queues.
> > 
> > Yup.  Examples:
> > 
> > ftp://ftp.kernel.org/pub/linux/kernel/people/agk/patches/2.6/editing/
> > http://ozlabs.org/~rusty/kernel/rr-latest
> > http://www.kernel.org/pub/linux/kernel/people/gregkh/gregkh-2.6/gregkh-02-usb
> > 
> > Note how you can publish subsets of your patchset by bracketing them with
> > "# MM_PATCHES_START" and "# MM_PATCHES_END" for -mm, and "#
> > NEXT_PATCHES_START" and "# NEXT_PATCHES_END" for linux-next.
> 
> I decided to go the git route.
> 
> Here is a git tree for the collection of patches for the m68knommu
> architecture that I intend for the 2.6.27 merge window.
> 
> git://git.kernel.org/pub/scm/linux/kernel/git/gerg/m68knommu.git for-linus
> 
> I have created a general uclinux changes git tree as well,
> 
> git://git.kernel.org/pub/scm/linux/kernel/git/gerg/uclinux.git for-linus
> 
> though currently I have nothing queued for that.
> 

Great, thanks.  But can we get them into linux-next please?  I'll pick
them up via that route.

  reply	other threads:[~2008-06-23  5:51 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
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 [this message]
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=20080622225102.5117f22b.akpm@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=gerg@snapgear.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    /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.