Hi all,
I have created today's linux-next tree at
git://git.kernel.org/pub/scm/linux/kernel/git/sfr/linux-next.git.
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
allmodconfig for both powerpc and x86_64.
There was only one minor merge problem and one build problem.
We are up to 35 trees, more are welcome (even if they are currently
empty).
Status of my local build tests is at
http://kisskb.ellerman.id.au/kisskb/branch/9/.
Also, the linux-next tree is being build/boot tested by the guys at
test.kernel.org. Thanks to them.
This release has one already known build problem: CONFIG_NFS_FS && !
CONFIG_NFS_V4 will fail to build.
--
Cheers,
Stephen Rothwell [email protected]
On Wed, 27 Feb 2008 17:03:00 +1100 Stephen Rothwell <[email protected]> wrote:
>
> You can see which trees have been included by looking in the Next/Trees
> file in the source.
The astute will notice that the pata tree has been renamed to ide as this
better reflects reality (according to Andrew).
--
Cheers,
Stephen Rothwell [email protected]
http://www.canb.auug.org.au/~sfr/
On Wed, 27 Feb 2008 17:03:00 +1100 Stephen Rothwell <[email protected]> wrote:
> We are up to 35 trees, more are welcome (even if they are currently
> empty).
So who's missing now?
I have:
git-acpi
git-agpgart
git-alsa
git-arm
git-arm-master
git-audit-master
git-avr32
git-backlight
git-battery
git-block
git-bluetooth
git-cifs
git-cpufreq
git-cryptodev
git-drm
git-dvb
git-gfs2-nmw
git-hid
git-hrt
git-hwmon
git-ia64
git-ieee1394
git-infiniband
git-input
git-intelfb
git-jfs
git-jg-misc
git-kbuild
git-kvm
git-lblnet
git-leds
git-libata-all
git-m32r
git-md-accel
git-mips
git-mmc
git-mtd
git-net
git-nfs
git-nfsd
git-ntfs
git-ocfs2
git-parisc
git-pcmcia (dead)
git-perfmon (i don't actually include this)
git-powerpc
git-s390
git-sas (might be dead)
git-sched
git-scsi-misc
git-scsi-rc-fixes
git-scsi-target
git-selinux
git-sh
git-slub
git-sparc64
git-ubi
git-unionfs
git-v9fs
git-watchdog
git-x86
git-xfs
git-xtensa
Plus quilt trees:
http://www.kernel.org/pub/linux/kernel/people/kristen/pci-hotplug (seems to be dead)
ftp://ftp.kernel.org/pub/linux/kernel/people/tytso/ext4-patches/LATEST/broken-out/
http://www.kernel.org/pub/linux/kernel/people/gregkh/gregkh-2.6/gregkh-01-driver-core
http://www.kernel.org/pub/linux/kernel/people/gregkh/gregkh-2.6/gregkh-03-usb
http://www.kernel.org/pub/linux/kernel/people/gregkh/gregkh-2.6/gregkh-02-pci
http://khali.linux-fr.org/devel/linux-2.6/jdelvare-i2c/
http://kernel.org/pub/linux/kernel/people/bart/pata-2.6/patches/
ftp://ftp.kernel.org/pub/linux/kernel/people/agk/patches/2.6/editing/
On Tue, 26 Feb 2008 23:00:59 -0800 Andrew Morton <[email protected]> wrote:
>
> So who's missing now?
>
> I have:
Of this list, I *don't* have:
> git-agpgart
> git-alsa
> git-arm
> git-arm-master
> git-audit-master
> git-backlight
> git-battery
> git-block
> git-bluetooth
> git-cifs
> git-cpufreq
> git-cryptodev
> git-drm
> git-gfs2-nmw
> git-input
> git-intelfb
> git-jg-misc
> git-lblnet
> git-leds
> git-libata-all
> git-m32r
> git-md-accel
> git-mips
> git-mmc
> git-mtd
> git-net
> git-ntfs
> git-parisc
> git-pcmcia (dead)
> git-perfmon (i don't actually include this)
> git-sas (might be dead)
> git-sched
> git-scsi-target
> git-slub
> git-sparc64
> git-unionfs
> git-v9fs
> git-watchdog
> git-x86
> git-xtensa
>
>
> Plus quilt trees:
>
> http://www.kernel.org/pub/linux/kernel/people/kristen/pci-hotplug (seems to be dead)
> ftp://ftp.kernel.org/pub/linux/kernel/people/tytso/ext4-patches/LATEST/broken-out/
But on the plus side I also have:
blackfin
dlm
libata-dev (same as git-libata-all?)
m68k
tests
--
Cheers,
Stephen Rothwell [email protected]
On Wednesday 27 February 2008 9:06:26 am Stephen Rothwell wrote:
> On Tue, 26 Feb 2008 23:00:59 -0800 Andrew Morton
<[email protected]> wrote:
> > So who's missing now?
> >
> > I have:
>
> Of this list, I *don't* have:
...
> > git-lblnet
I keep the labeled networking patches for the upcoming (in this case
2.6.26) kernel here:
* git://git.infradead.org/users/pcmoore/lblnet-2.6_testing
Patches for the current kernel (in this case 2.6.25) live here:
* git://git.infradead.org/users/pcmoore/lblnet-2.6
Both are currently empty.
--
paul moore
linux security @ hp
Hi Paul,
On Wed, 27 Feb 2008 09:43:52 -0500 Paul Moore <[email protected]> wrote:
>
> I keep the labeled networking patches for the upcoming (in this case
> 2.6.26) kernel here:
>
> * git://git.infradead.org/users/pcmoore/lblnet-2.6_testing
Added in anticipation, thanks.
--
Cheers,
Stephen Rothwell [email protected]
On Wednesday 27 February 2008 10:31:53 am Stephen Rothwell wrote:
> Hi Paul,
>
> On Wed, 27 Feb 2008 09:43:52 -0500 Paul Moore <[email protected]>
wrote:
> > I keep the labeled networking patches for the upcoming (in this
> > case 2.6.26) kernel here:
> >
> > * git://git.infradead.org/users/pcmoore/lblnet-2.6_testing
>
> Added in anticipation, thanks.
Thanks, sorry for not sending mail sooner.
--
paul moore
linux security @ hp
Stephen Rothwell wrote:
> But on the plus side I also have:
>
> libata-dev (same as git-libata-all?)
Intentionally different. libata-dev.git#NEXT is for linux-next, and
libata-dev.git#ALL is for -mm.
Jeff
On Thu, Feb 28, 2008 at 01:06:26AM +1100, Stephen Rothwell wrote:
> On Tue, 26 Feb 2008 23:00:59 -0800 Andrew Morton <[email protected]> wrote:
> >
> > So who's missing now?
> > ftp://ftp.kernel.org/pub/linux/kernel/people/tytso/ext4-patches/LATEST/broken-out/
Hi Stephen,
please add:
git://git.kernel.org/pub/scm/linux/kernel/git/tytso/ext4.git next
This contains a subset of the patches in the ext4 patch set which we
are explicitly planning on pushing to Linus at the next merge window.
It actually probably wouldn't hurt to pull the entire quilt series
into linux-next, since we don't export any interfaces that are used by
other linux trees, and that would give us better heads up for
conflicts in patches still in development conflicting with upcoming
core changes. But it conflicts with the initial premise of
linux-next, so that's why I set up the next branch of the above git
tree.
Regards,
- Ted
Hi Jeff,
On Wed, 27 Feb 2008 12:30:59 -0500 Jeff Garzik <[email protected]> wrote:
>
> Intentionally different. libata-dev.git#NEXT is for linux-next, and
> libata-dev.git#ALL is for -mm.
Excellent. Thanks for that.
--
Cheers,
Stephen Rothwell [email protected]
http://www.canb.auug.org.au/~sfr/
Hi Ted,
On Wed, 27 Feb 2008 14:55:25 -0500 Theodore Tso <[email protected]> wrote:
>
> please add:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/tytso/ext4.git next
Added, thanks.
> This contains a subset of the patches in the ext4 patch set which we
> are explicitly planning on pushing to Linus at the next merge window.
That's what we want.
> It actually probably wouldn't hurt to pull the entire quilt series
> into linux-next, since we don't export any interfaces that are used by
> other linux trees, and that would give us better heads up for
> conflicts in patches still in development conflicting with upcoming
> core changes. But it conflicts with the initial premise of
> linux-next, so that's why I set up the next branch of the above git
> tree.
Thanks, the less conflicts I have to fix the better. :-) I guess over
time patches will migrate into your next branch or they will appear there
after the next Linus release.
--
Cheers,
Stephen Rothwell [email protected]