linux-next: Tree for Feb 22

2021-02-22 Thread Stephen Rothwell
Hi all, Please do not add any changes destined for v5.13 to your linux-next included branches until after v5.12-rc1 has been released. Changes since 20210219: The sparc tree gained a conflict against Linus' tree. The kbuild tree gained a build failure so I used the version from next-20210219.

linux-next: Tree for Feb 22

2019-02-21 Thread Stephen Rothwell
Hi all, Changes since 20190221: New tree: devfreq The powerpc tree gained conflicts against the dma-mapping tree and a build failure for which I reverted a commit. The nfs-anna tree gained a conflict against the nfs tree. The swiotlb tree gained a conflict against the powerpc tree. The rpmsg

linux-next: Tree for Feb 22

2018-02-21 Thread Stephen Rothwell
Hi all, Changes since 20180221: The akpm-current tree gained a build failure for which I applied a patch. Non-merge commits (relative to Linus' tree): 2962 3399 files changed, 117276 insertions(+), 61145 deletions(-)

linux-next: Tree for Feb 22

2017-02-21 Thread Stephen Rothwell
Hi all, Please do not add any material intended for v4.12 to your linux-next included branches until after v4.11-rc1 has been released. Changes since 20170221: The net-next tree gained a conflict against the s390 tree. The kspp tree gained conflicts against the net-next tree. The scsi-mkp tree

linux-next: Tree for Feb 22

2016-02-21 Thread Stephen Rothwell
Hi all, Changes since 20160219: The net-next tree lost its build failure. The wireless-drivers-next tree lost its build failure. The crypto tree gained conflicts against Linus' tree. The drm tree gained conflicts against Linus' tree and a build failure for which I applied a merge fix patch. T

linux-next: Tree for Feb 22

2015-02-21 Thread Stephen Rothwell
Hi all, Please do not add any material destined for v3.21 to your linux-next included trees until after v3.20-rc1 has been released. Changes since 20150220: The mips tree gained conflist against Linus' tree. The s390 tree gained a conflict against Linus' tree. The vfs tree gained conflicts aga

Re: linux-next: Tree for Feb 22

2008-02-23 Thread Andrew Morton
On Thu, 21 Feb 2008 23:30:15 -0800 (PST) David Miller <[EMAIL PROTECTED]> wrote: > From: Al Viro <[EMAIL PROTECTED]> > Date: Fri, 22 Feb 2008 07:25:54 + > > > On Fri, Feb 22, 2008 at 06:21:16PM +1100, Stephen Rothwell wrote: > > > On Fri, 22 Feb 2008 17:04:21 +1100 Stephen Rothwell <[EMAIL PR

Re: linux-next: Tree for Feb 22

2008-02-22 Thread Randy Dunlap
On Fri, 22 Feb 2008 17:04:21 +1100 Stephen Rothwell wrote: > Hi all, > > I have created today's linux-next tree at > git://git.kernel.org/pub/scm/linux/kernel/git/sfr/linux-next.git. > > > I am now including tarballs in > http://www.kernel.org/pub/linux/kernel/people/sfr/linux-next/. Thanks fo

Re: linux-next: Tree for Feb 22

2008-02-21 Thread David Miller
From: Al Viro <[EMAIL PROTECTED]> Date: Fri, 22 Feb 2008 07:25:54 + > On Fri, Feb 22, 2008 at 06:21:16PM +1100, Stephen Rothwell wrote: > > On Fri, 22 Feb 2008 17:04:21 +1100 Stephen Rothwell <[EMAIL PROTECTED]> > > wrote: > > > > > > Status of my local build tests is at > > > http://kisskb.e

Re: linux-next: Tree for Feb 22

2008-02-21 Thread Al Viro
On Fri, Feb 22, 2008 at 06:21:16PM +1100, Stephen Rothwell wrote: > On Fri, 22 Feb 2008 17:04:21 +1100 Stephen Rothwell <[EMAIL PROTECTED]> wrote: > > > > Status of my local build tests is at > > http://kisskb.ellerman.id.au/kisskb/branch/9/. The sparc builds have > > been mostly disabled while I

Re: linux-next: Tree for Feb 22

2008-02-21 Thread Stephen Rothwell
On Fri, 22 Feb 2008 17:04:21 +1100 Stephen Rothwell <[EMAIL PROTECTED]> wrote: > > Status of my local build tests is at > http://kisskb.ellerman.id.au/kisskb/branch/9/. The sparc builds have > been mostly disabled while I obtain a working cross compiler. I have reenabled the sparc and sparc64 bui

Re: linux-next: Tree for Feb 22

2008-02-21 Thread Stephen Rothwell
Hi Frank, On Fri, 22 Feb 2008 07:43:58 +0100 Frank Seidel <[EMAIL PROTECTED]> wrote: > > at least the bz2 tar i just looked at from that URL has a problem > with the prefix resulting to this toplevel extraction: > > next-20080222arch > next-20080222block > ... > next-20080222virt > > So, i guess

Re: linux-next: Tree for Feb 22

2008-02-21 Thread Stephen Rothwell
Hi Frank, On Fri, 22 Feb 2008 07:32:58 +0100 Frank Seidel <[EMAIL PROTECTED]> wrote: > > Looks great :-) Of course i also just put a ref to it on the > wiki. Thanks. -- Cheers, Stephen Rothwell[EMAIL PROTECTED] pgp0b6xYVxwV7.pgp Description: PGP signature

Re: linux-next: Tree for Feb 22

2008-02-21 Thread Frank Seidel
Hi Stephen, Stephen Rothwell schrieb: > I am now including tarballs in > http://www.kernel.org/pub/linux/kernel/people/sfr/linux-next/. at least the bz2 tar i just looked at from that URL has a problem with the prefix resulting to this toplevel extraction: next-20080222arch next-20080222block ..

Re: linux-next: Tree for Feb 22

2008-02-21 Thread Frank Seidel
Stephen Rothwell schrieb: > I am now including tarballs in > http://www.kernel.org/pub/linux/kernel/people/sfr/linux-next/. Looks great :-) Of course i also just put a ref to it on the wiki. Thanks, Frank -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a

linux-next: Tree for Feb 22

2008-02-21 Thread Stephen Rothwell
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