From: Stephen Rothwell <sfr@...>
Subject: What do you want from linux-next?
 [2]Date: Mar 24, 11:11 pm 2008

Hi Linus, Andrew,

Now that we are (presumably) approaching the next merge window, can I ask
what use (if any) will you be making of the linux-next tree?
Alternatively, is there any information you want from it?

--=20
Cheers,
Stephen Rothwell                    sfr@canb.auug.org.au [3]
http://www.canb.auug.org.au/~sfr/ [4]


From: Randy.Dunlap <rdunlap@...>
Subject: Re: What do you want from linux-next?
 [4]Date: Mar 24, 11:59 pm 2008

On Tue, 25 Mar 2008, Stephen Rothwell wrote:

> Hi Linus, Andrew,
> 
> Now that we are (presumably) approaching the next merge window, can I ask
> what use (if any) will you be making of the linux-next tree?
> Alternatively, is there any information you want from it?

Hi,

I'd like some clarification about the future (use) of linux-next
and Andrew's -mm patch series.  They duplicate a lot of the major
git tree or quilt patch series.  Can we expect both of them to
continue as is or will -mm be a patch series on top of linux-next
or what?

-- 
~Randy
--


From: Andrew Morton <akpm@...>
Subject: Re: What do you want from linux-next?
 [4]Date: Mar 25, 12:32 am 2008

On Mon, 24 Mar 2008 20:59:42 -0700 (PDT) "Randy.Dunlap" <rdunlap@xenotime.net> wrote:

> On Tue, 25 Mar 2008, Stephen Rothwell wrote:
> 
> > Hi Linus, Andrew,
> > 
> > Now that we are (presumably) approaching the next merge window, can I ask
> > what use (if any) will you be making of the linux-next tree?
> > Alternatively, is there any information you want from it?
> 

afacit it's already working.  The level of merge and build errors in the
subsystem trees this time around is a tiny fraction of what it was at the
same stage in 2.6.24-rcX.  otoh perhaps this is because Ingo got tired of
all the complaining and took most of his tree away from me, dunno ;)

> 
> I'd like some clarification about the future (use) of linux-next
> and Andrew's -mm patch series.  They duplicate a lot of the major
> git tree or quilt patch series.  Can we expect both of them to
> continue as is or will -mm be a patch series on top of linux-next
> or what?

There are 60 or 80 "susbsytem" trees hosted in -mm at present:

...
# spi
# mfd
# vt
# kprobes
# quota
# i4l
# i2o
# ecryptfs
# autofs
# rtc
# gpio
# fbdev
# md
# pnp
# ext2
# ext3
# ufs
# udf
# reiserfs
# fat
# documentation
# cgroups
# memcgroup
# cpusets
# signals
# pgrp
# ptrace
# workqueues
# cpu hotplug
# kdump
# dma
# ipc
# ipmi
# tty
# elf
# char
# keys
<etc>

I need to find a way to a) get matureish parts of those trees into
linux-next and to b) base the rest of -mm off linux-next.  I haven't
started thinking about that yet.

There seem to be some trees which aren't yet in linux-next, some of them
significant.  The present list I'm pulling from is

git-acpi
git-agpgart
git-alsa-tiwai
git-arm
git-arm-master
git-avr32
git-audit-master
git-backlight
git-battery
git-block
git-cifs
git-cpufreq
git-drm
git-dvb
git-gfs2-nmw
git-dlm
git-hrt
git-kvm
git-net
git-bluetooth
git-cryptodev
git-ia64
git-ieee1394
git-scsi-misc
git-hid
git-hwmon
git-infiniband
git-input
git-intelfb
git-jfs
git-kbuild
git-lblnet
git-leds
git-libata-all
git-m32r
git-mips
git-async-tx
git-mmc
git-mtd
git-nfs
git-nfsd
git-ocfs2
git-parisc
git-perfmon
git-pcmcia
git-powerpc-merge
git-powerpc
git-s390
git-sched
git-scsi-rc-fixes
git-scsi-target
git-sas
git-selinux
git-security-testing
git-semaphore
git-sh
git-slub
git-sparc64
git-ubi
git-udf
git-jg-misc
git-unionfs
git-ntfs
git-v9fs
git-watchdog
git-x86
git-kgdb-light
git-xfs
git-xtensa
http://ozlabs.org/~rusty/kernel/rr-latest [5]
http://www.kernel.org/pub/linux/kernel/people/kristen/pci-hotplug [6]
ftp://ftp.kernel.org/pub/linux/kernel/people/tytso/ext4-patches/LATEST/broken-out/ [7]
http://www.kernel.org/pub/linux/kernel/people/gregkh/gregkh-2.6/gregkh-01-driver-core [8]
http://www.kernel.org/pub/linux/kernel/people/gregkh/gregkh-2.6/gregkh-03-usb [9]
http://www.kernel.org/pub/linux/kernel/people/gregkh/gregkh-2.6/gregkh-02-pci [10]
http://khali.linux-fr.org/devel/linux-2.6/jdelvare-i2c/ [11]
http://kernel.org/pub/linux/kernel/people/bart/pata-2.6/patches/ [12]
ftp://ftp.kernel.org/pub/linux/kernel/people/agk/patches/2.6/editing/ [13]

which ones are missing?



Do we know if many people are testing linux-next yet?

I had planned on asking patch contributors to base their work on linux-next
when the 2.6.23- and 2.6.24-style calamities reoccurred.  But it just
hasn't happened.

--

From: Stephen Rothwell <sfr@...>
Subject: linux-next: Tree for March 27
 [13]Date: Mar 27, 3:33 am 2008

Hi all,

I have created today's linux-next tree at
git://git.kernel.org/pub/scm/linux/kernel/git/sfr/linux-next.git
(tar balls at
http://www.kernel.org/pub/linux/kernel/people/sfr/linux-next/ [14]).

You can see which trees have been included by looking in the Next/Trees
file in the source.  There are also quilt-import.log and merge.log files
in the Next directory.  Between each merge, the tree was built with
a ppc64_defconfig for powerpc and an allmodconfig for x86_64.

There were a few merge conflicts (fairly trivial) and several build
failures that have been notified.

We are up to 49 trees, more are welcome (even if they are currently
empty).  Thanks to those who have contributed, and to those who haven't,
please do.

In particular, I have very few of the architecture trees ....

Status of my local build tests is at
http://kisskb.ellerman.id.au/linux-next [15].  If maintainers want to give
advice about cross compilers/configs that work, we are always open to add
more builds.

Thanks to Jan Dittmer for adding the linux-next tree to his build tests
at http://l4x.org/k/ [16] and the guys at http://test.kernel.org/ [17].

--=20
Cheers,
Stephen Rothwell                    sfr@canb.auug.org.au [18]