Re: linux-next: Tree for Nov 14 (sound/soc/amd/raven/)

2018-11-14 Thread Randy Dunlap
On 11/13/18 9:26 PM, Stephen Rothwell wrote: > Hi all, > > Changes since 20181113: > on i386 or x86_64: when CONFIG_PCI is not enabled. ../sound/soc/amd/raven/pci-acp3x.c: In function 'snd_acp3x_probe': ../sound/soc/amd/raven/pci-acp3x.c:59:2: error: implicit declaration of function 'pci_enab

Re: linux-next: Tree for Nov 14 (net/sched/sch_netem)

2017-11-14 Thread Randy Dunlap
On 11/13/2017 10:20 PM, Stephen Rothwell wrote: > Hi all, > > Please do not add any v4.16 material to your linux-next included trees > until v4.15-rc1 has been released. > > Changes since 20171113: on i386: ERROR: "__moddi3" [net/sched/sch_netem.ko] undefined! -- ~Randy

Re: linux-next: Tree for Nov 14 (drivers/cpufreq/intel_pstate.c)

2016-11-14 Thread Srinivas Pandruvada
On Mon, 2016-11-14 at 09:48 -0800, Randy Dunlap wrote: > On 11/13/16 23:23, Stephen Rothwell wrote: > > > > Hi all, > > > > Changes since 2016: > > > > on i386, when CONFIG_ACPI is not enabled: > > ../drivers/cpufreq/intel_pstate.c: In function 'copy_cpu_funcs': > ../drivers/cpufreq/intel_

Re: linux-next: Tree for Nov 14 (drivers/cpufreq/intel_pstate.c)

2016-11-14 Thread Randy Dunlap
On 11/13/16 23:23, Stephen Rothwell wrote: > Hi all, > > Changes since 2016: > on i386, when CONFIG_ACPI is not enabled: ../drivers/cpufreq/intel_pstate.c: In function 'copy_cpu_funcs': ../drivers/cpufreq/intel_pstate.c:1798:2: error: too few arguments to function 'intel_pstate_use_acpi_pr

Re: linux-next: Tree for Nov 14

2014-11-17 Thread Guenter Roeck
On Mon, Nov 17, 2014 at 01:12:17PM +0800, Jiang Liu wrote: > On 2014/11/16 11:22, Guenter Roeck wrote: > > On 11/15/2014 06:33 PM, Jiang Liu wrote: > >> Hi Guenter, > >> Could you please help to provide the config file and > >> error messages? > > > > Config file: > > > > https://github.c

Re: linux-next: Tree for Nov 14

2014-11-16 Thread Jiang Liu
On 2014/11/16 11:22, Guenter Roeck wrote: > On 11/15/2014 06:33 PM, Jiang Liu wrote: >> Hi Guenter, >> Could you please help to provide the config file and >> error messages? > > Config file: > > https://github.com/groeck/linux-build-test/blob/master/rootfs/x86/qemu_x86_pc_nosmp_defconfig

Re: linux-next: Tree for Nov 14

2014-11-16 Thread Guenter Roeck
On 11/16/2014 08:01 AM, Guenter Roeck wrote: On 11/16/2014 12:24 AM, Jiang Liu wrote: On 2014/11/16 14:56, Guenter Roeck wrote: On 11/15/2014 08:20 PM, Jiang Liu wrote: On 2014/11/16 11:22, Guenter Roeck wrote: On 11/15/2014 06:33 PM, Jiang Liu wrote: Hi Guenter, Could you please help

Re: linux-next: Tree for Nov 14

2014-11-16 Thread Guenter Roeck
On 11/16/2014 12:24 AM, Jiang Liu wrote: On 2014/11/16 14:56, Guenter Roeck wrote: On 11/15/2014 08:20 PM, Jiang Liu wrote: On 2014/11/16 11:22, Guenter Roeck wrote: On 11/15/2014 06:33 PM, Jiang Liu wrote: Hi Guenter, Could you please help to provide the config file and error messages

Re: linux-next: Tree for Nov 14

2014-11-16 Thread Guenter Roeck
On 11/16/2014 12:37 AM, Jiang Liu wrote: On 2014/11/16 16:24, Jiang Liu wrote: On 2014/11/16 14:56, Guenter Roeck wrote: On 11/15/2014 08:20 PM, Jiang Liu wrote: I took the configuration file I had for the SMP case (located in the same directory in the git repository), disabled SMP, and ran

Re: linux-next: Tree for Nov 14

2014-11-16 Thread Jiang Liu
On 2014/11/16 16:24, Jiang Liu wrote: > On 2014/11/16 14:56, Guenter Roeck wrote: >> On 11/15/2014 08:20 PM, Jiang Liu wrote: >> >> I took the configuration file I had for the SMP case (located in the same >> directory in the git repository), disabled SMP, and ran "make >> savedefconfig". >> "old

Re: linux-next: Tree for Nov 14

2014-11-16 Thread Jiang Liu
On 2014/11/16 14:56, Guenter Roeck wrote: > On 11/15/2014 08:20 PM, Jiang Liu wrote: >> >> On 2014/11/16 11:22, Guenter Roeck wrote: >>> On 11/15/2014 06:33 PM, Jiang Liu wrote: Hi Guenter, Could you please help to provide the config file and error messages? >>> >>> Config file:

Re: linux-next: Tree for Nov 14

2014-11-15 Thread Guenter Roeck
On 11/15/2014 08:20 PM, Jiang Liu wrote: On 2014/11/16 11:22, Guenter Roeck wrote: On 11/15/2014 06:33 PM, Jiang Liu wrote: Hi Guenter, Could you please help to provide the config file and error messages? Config file: https://github.com/groeck/linux-build-test/blob/master/rootfs/x

Re: linux-next: Tree for Nov 14

2014-11-15 Thread Jiang Liu
On 2014/11/16 11:22, Guenter Roeck wrote: > On 11/15/2014 06:33 PM, Jiang Liu wrote: >> Hi Guenter, >> Could you please help to provide the config file and >> error messages? > > Config file: > > https://github.com/groeck/linux-build-test/blob/master/rootfs/x86/qemu_x86_pc_nosmp_defconfi

Re: linux-next: Tree for Nov 14

2014-11-15 Thread Guenter Roeck
On 11/15/2014 06:33 PM, Jiang Liu wrote: Hi Guenter, Could you please help to provide the config file and error messages? Config file: https://github.com/groeck/linux-build-test/blob/master/rootfs/x86/qemu_x86_pc_nosmp_defconfig Error log: http://server.roeck-us.net:8

Re: linux-next: Tree for Nov 14

2014-11-15 Thread Jiang Liu
Hi Guenter, Could you please help to provide the config file and error messages? Thanks! Gerry On 2014/11/16 5:19, Guenter Roeck wrote: > On Fri, Nov 14, 2014 at 07:27:38PM +1100, Stephen Rothwell wrote: >> Hi all, >> >> Changes since 20141113: >> >> New tree: overlayfs >> >> The idle tree

Re: linux-next: Tree for Nov 14

2014-11-15 Thread Guenter Roeck
On Fri, Nov 14, 2014 at 07:27:38PM +1100, Stephen Rothwell wrote: > Hi all, > > Changes since 20141113: > > New tree: overlayfs > > The idle tree gained a conflict against Linus' tree. > > The scsi tree gained a conflict against the usb tree. > > Non-merge commits (relative to Linus' tree): 62

RE: linux-next: Tree for Nov 14 (lustre)

2013-11-14 Thread Peng, Tao
>-Original Message- >From: Randy Dunlap [mailto:rdun...@infradead.org] >Sent: Friday, November 15, 2013 3:04 AM >To: Stephen Rothwell; linux-n...@vger.kernel.org >Cc: LKML; peng tao; Peng, Tao; Greg Kroah-Hartman; >andreas.dil...@intel.com; hpdd-discuss >Subject: Re:

Re: linux-next: Tree for Nov 14 (lustre)

2013-11-14 Thread Randy Dunlap
On 11/13/13 20:22, Stephen Rothwell wrote: > Hi all, > > Please do *not* add any v3.14 material to linux-next until after > v3.13-rc1 is released. > > Changes since 20131113: > Please fix MANY build errors that show up when CONFIG_PROC_FS is not enabled. thanks. -- ~Randy -- To unsubscribe fr

Re: linux-next: Tree for Nov 14

2012-11-15 Thread Mel Gorman
On Wed, Nov 14, 2012 at 12:05:15PM -0500, Rik van Riel wrote: > On 11/14/2012 03:13 AM, Hugh Dickins wrote: > > >Please, Ingo, stop trying to force this in ahead of time, yet again. > > > >People are still reviewing and comparing competing solutions. > >Maybe this latest will prove to be closest t

Re: linux-next: Tree for Nov 14 (gpu/drm/i915)

2012-11-14 Thread Andrew Morton
On Wed, 14 Nov 2012 11:41:49 -0800 Randy Dunlap wrote: > On 11/13/2012 09:30 PM, Stephen Rothwell wrote: > > > Hi all, > > > > News: next-20121115 (i.e. tomorrow) will be the last release until > > next-20121126 (which should be just be after -rc7, I guess - assuming > > that Linus does not rel

Re: linux-next: Tree for Nov 14 (gpu/drm/i915)

2012-11-14 Thread Randy Dunlap
On 11/13/2012 09:30 PM, Stephen Rothwell wrote: > Hi all, > > News: next-20121115 (i.e. tomorrow) will be the last release until > next-20121126 (which should be just be after -rc7, I guess - assuming > that Linus does not release v3.7 before then), so if you want something > in linux-next for a

Re: linux-next: Tree for Nov 14

2012-11-14 Thread Linus Torvalds
On Tue, Nov 13, 2012 at 10:56 PM, Andrew Morton wrote: > > That solves one problem, but I still need to route around the numa > stuff when preparing the 3.8-rc1 merge. Again! Btw - and this is tangential/unrelated - I really think that your should strive to *not* base -mm on top of next, but ins

Re: linux-next: Tree for Nov 14

2012-11-14 Thread Rik van Riel
On 11/14/2012 03:13 AM, Hugh Dickins wrote: Please, Ingo, stop trying to force this in ahead of time, yet again. People are still reviewing and comparing competing solutions. Maybe this latest will prove to be closest to the right answer, maybe it will not. It's, what, about two days old right

Re: linux-next: Tree for Nov 14

2012-11-14 Thread Hugh Dickins
On Wed, 14 Nov 2012, Ingo Molnar wrote: > * Andrew Morton wrote: > > On Wed, 14 Nov 2012 07:47:26 +0100 Ingo Molnar wrote: > > > * Andrew Morton wrote: > > > > On Wed, 14 Nov 2012 16:30:42 +1100 Stephen Rothwell > > > > wrote: > > > > > > > > > News: next-20121115 (i.e. tomorrow) will be the

Re: linux-next: Tree for Nov 14

2012-11-13 Thread Ingo Molnar
* Andrew Morton wrote: > On Wed, 14 Nov 2012 07:47:26 +0100 Ingo Molnar wrote: > > > > > * Andrew Morton wrote: > > > > > On Wed, 14 Nov 2012 16:30:42 +1100 Stephen Rothwell > > > wrote: > > > > > > > News: next-20121115 (i.e. tomorrow) will be the last release until > > > > next-2012112

Re: linux-next: Tree for Nov 14

2012-11-13 Thread Andrew Morton
On Wed, 14 Nov 2012 18:15:36 +1100 Stephen Rothwell wrote: > Hi Andrew, > > On Tue, 13 Nov 2012 22:56:35 -0800 Andrew Morton > wrote: > > > > On Wed, 14 Nov 2012 07:47:26 +0100 Ingo Molnar wrote: > > > > > * Andrew Morton wrote: > > > > > > > It would help if the old sched/numa code wasn'

Re: linux-next: Tree for Nov 14

2012-11-13 Thread Stephen Rothwell
Hi Andrew, On Tue, 13 Nov 2012 22:56:35 -0800 Andrew Morton wrote: > > On Wed, 14 Nov 2012 07:47:26 +0100 Ingo Molnar wrote: > > > * Andrew Morton wrote: > > > > > It would help if the old sched/numa code wasn't in -next while > > > you're away. That would give me a clean run at 3.7 and wi

Re: linux-next: Tree for Nov 14

2012-11-13 Thread Stephen Rothwell
On Wed, 14 Nov 2012 17:55:28 +1100 Stephen Rothwell wrote: > > On Tue, 13 Nov 2012 21:37:42 -0800 Andrew Morton > wrote: > > > > It would help if the old sched/numa code wasn't in -next while you're > > away. That would give me a clean run at 3.7 and will make it easier > > for others to integ

Re: linux-next: Tree for Nov 14

2012-11-13 Thread Andrew Morton
On Wed, 14 Nov 2012 07:47:26 +0100 Ingo Molnar wrote: > > * Andrew Morton wrote: > > > On Wed, 14 Nov 2012 16:30:42 +1100 Stephen Rothwell > > wrote: > > > > > News: next-20121115 (i.e. tomorrow) will be the last release until > > > next-20121126 (which should be just be after -rc7, I guess

Re: linux-next: Tree for Nov 14

2012-11-13 Thread Stephen Rothwell
Hi Andrew, On Tue, 13 Nov 2012 21:37:42 -0800 Andrew Morton wrote: > > It would help if the old sched/numa code wasn't in -next while you're > away. That would give me a clean run at 3.7 and will make it easier > for others to integrate and test the four(!) different > autoschednumacore impleme

Re: linux-next: Tree for Nov 14

2012-11-13 Thread Ingo Molnar
* Andrew Morton wrote: > On Wed, 14 Nov 2012 16:30:42 +1100 Stephen Rothwell > wrote: > > > News: next-20121115 (i.e. tomorrow) will be the last release until > > next-20121126 (which should be just be after -rc7, I guess - assuming > > that Linus does not release v3.7 before then), so if you

Re: linux-next: Tree for Nov 14

2012-11-13 Thread Andrew Morton
On Tue, 13 Nov 2012 21:37:42 -0800 Andrew Morton wrote: > It would help if the old sched/numa code wasn't in -next while you're > away. Now I think about it, that's going to be hard. If I integrate against tomorrow's -next, the mmotm patches will be against next+schednuma. Then you'll need to

Re: linux-next: Tree for Nov 14

2012-11-13 Thread Andrew Morton
On Wed, 14 Nov 2012 16:30:42 +1100 Stephen Rothwell wrote: > News: next-20121115 (i.e. tomorrow) will be the last release until > next-20121126 (which should be just be after -rc7, I guess - assuming > that Linus does not release v3.7 before then), so if you want something > in linux-next for a