linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg Ungerer <gerg@snapgear.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	linux-kernel@vger.kernel.org, linux-next@vger.kernel.org
Subject: Re: [PATCH] m68knommu: ColdFire add support for kernel preemption
Date: Mon, 23 Jun 2008 23:23:08 +1000	[thread overview]
Message-ID: <485FA3BC.5080807@snapgear.com> (raw)
In-Reply-To: <20080623175326.ddf5d2d4.sfr@canb.auug.org.au>

Hi Stephen,

Stephen Rothwell wrote:
> Hi Greg,
> 
> On Sun, 22 Jun 2008 22:51:02 -0700 Andrew Morton <akpm@linux-foundation.org> wrote:
>> On Mon, 23 Jun 2008 15:32:53 +1000 Greg Ungerer <gerg@snapgear.com> wrote:
>>
>>> 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
> 
> Added today (slipped it in at the end).

Great, thanks.


>>> 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
> 
> This tree currently has no for-linus branch.  You should create one (even
> if it just a subset of Linus' tree).  I've added it using its master
> branch for now, please let me know when it is fixed.

Ok, fixed now. There is an empty for-linus branch there.


> Also, these branches would normally be called for-next.  Most people keep
> for-linus for bug fixes for the current release.  If you decide to change
> the branch name, just let me know.

Ok, done too. Branches named for-next exist in both. The patches
on the for-linus branch in the m68knommu.git are now on the
for-next branch.

Do I need to send a request to Linus to pull this into his
tree during the next merge window?  Or will it migrate up
from linux-next?


> Repeat of the rules for linux-next: anything included must have been
> posted somewhere appropriate, reviewed and unit tested (i.e. your tree
> should build for you).
> 
>> Great, thanks.  But can we get them into linux-next please?  I'll pick
>> them up via that route.
> 
> Done.

Thanks
Greg


------------------------------------------------------------------------
Greg Ungerer  --  Chief Software Dude       EMAIL:     gerg@snapgear.com
SnapGear -- a Secure Computing Company      PHONE:       +61 7 3435 2888
825 Stanley St,                             FAX:         +61 7 3891 3630
Woolloongabba, QLD, 4102, Australia         WEB: http://www.SnapGear.com

  reply	other threads:[~2008-06-23 13:23 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200805010216.m412GT6t004096@goober>
     [not found] ` <20080501143336.552e39e1.akpm@linux-foundation.org>
     [not found]   ` <481AC07A.6080707@snapgear.com>
     [not found]     ` <20080502083755.GA13973@Chamillionaire.breakpoint.cc>
     [not found]       ` <20080502052235.eb9c336a.akpm@linux-foundation.org>
     [not found]         ` <485F3585.2080606@snapgear.com>
2008-06-23  5:51           ` [PATCH] m68knommu: ColdFire add support for kernel preemption Andrew Morton
2008-06-23  7:53             ` Stephen Rothwell
2008-06-23 13:23               ` Greg Ungerer [this message]
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=485FA3BC.5080807@snapgear.com \
    --to=gerg@snapgear.com \
    --cc=akpm@linux-foundation.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).