linux-kernel - Re: [PATCH] m68knommu: ColdFire add support for kernel preemption

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <485FA3BC.5080807@snapgear.com>
Date:	Mon, 23 Jun 2008 23:23:08 +1000
From:	Greg Ungerer <gerg@...pgear.com>
To:	Stephen Rothwell <sfr@...b.auug.org.au>
CC:	Andrew Morton <akpm@...ux-foundation.org>,
	linux-kernel@...r.kernel.org, linux-next@...r.kernel.org
Subject: Re: [PATCH] m68knommu: ColdFire add support for kernel preemption

Hi Stephen,

Stephen Rothwell wrote:
> Hi Greg,
> 
> On Sun, 22 Jun 2008 22:51:02 -0700 Andrew Morton <akpm@...ux-foundation.org> wrote:
>> On Mon, 23 Jun 2008 15:32:53 +1000 Greg Ungerer <gerg@...pgear.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@...pgear.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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/