Hi Andrew,
Andrew Morton wrote:
> On Fri, 2 May 2008 10:37:55 +0200 Sebastian Siewior <[email protected]> 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.
Regards
Greg
------------------------------------------------------------------------
Greg Ungerer -- Chief Software Dude EMAIL: [email protected]
Secure Computing Corporation PHONE: +61 7 3435 2888
825 Stanley St, FAX: +61 7 3891 3630
Woolloongabba, QLD, 4102, Australia WEB: http://www.SnapGear.com
On Mon, 23 Jun 2008 15:32:53 +1000 Greg Ungerer <[email protected]> wrote:
> Hi Andrew,
>
> Andrew Morton wrote:
> > On Fri, 2 May 2008 10:37:55 +0200 Sebastian Siewior <[email protected]> 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.
Hi Greg,
On Sun, 22 Jun 2008 22:51:02 -0700 Andrew Morton <[email protected]> wrote:
>
> On Mon, 23 Jun 2008 15:32:53 +1000 Greg Ungerer <[email protected]> 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).
> > 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.
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.
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.
--
Cheers,
Stephen Rothwell [email protected]
http://www.canb.auug.org.au/~sfr/
Hi Stephen,
Stephen Rothwell wrote:
> Hi Greg,
>
> On Sun, 22 Jun 2008 22:51:02 -0700 Andrew Morton <[email protected]> wrote:
>> On Mon, 23 Jun 2008 15:32:53 +1000 Greg Ungerer <[email protected]> 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: [email protected]
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
On Mon, 23 Jun 2008 23:23:08 +1000 Greg Ungerer <[email protected]> wrote:
> Do I need to send a request to Linus to pull this into his
> tree during the next merge window?
Yes, you do - nothing has changed in that regard.
> Or will it migrate up
> from linux-next?
Nope, linux-next is a testing tree only.
Hi Greg,
On Mon, 23 Jun 2008 23:23:08 +1000 Greg Ungerer <[email protected]> wrote:
>
> 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.
I have updated my info, thanks.
> 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?
Andrew has answered these.
--
Cheers,
Stephen Rothwell [email protected]
http://www.canb.auug.org.au/~sfr/