linux-next: Tree for Feb 17

2021-02-17 Thread Stephen Rothwell
Hi all, Changes since 20210216: The pm tree gained a conflict against the i3c tree. The net-next tree gained conflicts against the net tree. The tip tree gained a conflict against the pm tree. Non-merge commits (relative to Linus' tree): 10598 10682 files changed, 464339 insertions(+),

linux-next: Tree for Feb 17

2017-02-16 Thread Stephen Rothwell
Hi all, Changes since 20170216: The powerpc tree gained a conflict against Linus' tree. The tip tree gained conflicts against the drm, kspp, openrisc and powerpc trees. The akpm-current tree gained conflicts against the kspp and tip trees. I dropped 3 patches from the akpm tree that turned up

linux-next: Tree for Feb 17

2017-02-16 Thread Stephen Rothwell
Hi all, Changes since 20170216: The powerpc tree gained a conflict against Linus' tree. The tip tree gained conflicts against the drm, kspp, openrisc and powerpc trees. The akpm-current tree gained conflicts against the kspp and tip trees. I dropped 3 patches from the akpm tree that turned up

Re: linux-next: Tree for Feb 17

2016-02-23 Thread Sudip Mukherjee
On Wednesday 17 February 2016 11:07 PM, David Daney wrote: On 02/17/2016 03:52 AM, Sudip Mukherjee wrote: On Wed, Feb 17, 2016 at 04:39:21PM +1100, Stephen Rothwell wrote: Hi all, Changes since 20160216: since last few days build of mips cavium_octeon_defconfig is failing with the error:

Re: linux-next: Tree for Feb 17

2016-02-23 Thread Sudip Mukherjee
On Wednesday 17 February 2016 11:07 PM, David Daney wrote: On 02/17/2016 03:52 AM, Sudip Mukherjee wrote: On Wed, Feb 17, 2016 at 04:39:21PM +1100, Stephen Rothwell wrote: Hi all, Changes since 20160216: since last few days build of mips cavium_octeon_defconfig is failing with the error:

Re: linux-next: Tree for Feb 17

2016-02-17 Thread David Daney
On 02/17/2016 03:52 AM, Sudip Mukherjee wrote: On Wed, Feb 17, 2016 at 04:39:21PM +1100, Stephen Rothwell wrote: Hi all, Changes since 20160216: since last few days build of mips cavium_octeon_defconfig is failing with the error: arch/mips/include/asm/octeon/cvmx.h:60:39: fatal error:

Re: linux-next: Tree for Feb 17

2016-02-17 Thread David Daney
On 02/17/2016 03:52 AM, Sudip Mukherjee wrote: On Wed, Feb 17, 2016 at 04:39:21PM +1100, Stephen Rothwell wrote: Hi all, Changes since 20160216: since last few days build of mips cavium_octeon_defconfig is failing with the error: arch/mips/include/asm/octeon/cvmx.h:60:39: fatal error:

Re: linux-next: Tree for Feb 17

2016-02-17 Thread Sudip Mukherjee
On Wed, Feb 17, 2016 at 04:39:21PM +1100, Stephen Rothwell wrote: > Hi all, > > Changes since 20160216: since last few days build of mips cavium_octeon_defconfig is failing with the error: arch/mips/include/asm/octeon/cvmx.h:60:39: fatal error: asm/octeon/cvmx-ciu3-defs.h: No such file

Re: linux-next: Tree for Feb 17

2016-02-17 Thread Sudip Mukherjee
On Wed, Feb 17, 2016 at 04:39:21PM +1100, Stephen Rothwell wrote: > Hi all, > > Changes since 20160216: since last few days build of mips cavium_octeon_defconfig is failing with the error: arch/mips/include/asm/octeon/cvmx.h:60:39: fatal error: asm/octeon/cvmx-ciu3-defs.h: No such file

linux-next: Tree for Feb 17

2016-02-16 Thread Stephen Rothwell
Hi all, Changes since 20160216: The net-next tree gained a conflict against the net tree. The crypto tree gained a build failure so I used the version from next-20160216. The clockevents tree gained a conflict against Linus' tree. The gpio tree lost its build failure. The aio tree still had

linux-next: Tree for Feb 17

2016-02-16 Thread Stephen Rothwell
Hi all, Changes since 20160216: The net-next tree gained a conflict against the net tree. The crypto tree gained a build failure so I used the version from next-20160216. The clockevents tree gained a conflict against Linus' tree. The gpio tree lost its build failure. The aio tree still had

Re: linux-next: Tree for Feb 17 (mips build failures)

2015-02-18 Thread Markos Chandras
On Wed, Feb 18, 2015 at 05:54:57AM -0800, Guenter Roeck wrote: > On 02/18/2015 01:14 AM, Markos Chandras wrote: > > On Wed, Feb 18, 2015 at 07:37:40AM +1100, Stephen Rothwell wrote: > >> Hi Guenter, > >> > >> [Add Ralf to cc] > >> > >> On Tue, 17 Feb 2015 09:20:36 -0800 Guenter Roeck > >> wrote:

Re: linux-next: Tree for Feb 17 (mips build failures)

2015-02-18 Thread Guenter Roeck
On 02/18/2015 01:14 AM, Markos Chandras wrote: On Wed, Feb 18, 2015 at 07:37:40AM +1100, Stephen Rothwell wrote: Hi Guenter, [Add Ralf to cc] On Tue, 17 Feb 2015 09:20:36 -0800 Guenter Roeck wrote: Build results: total: 121 pass: 109 fail: 12 Failed builds: mips:defconfig

Re: linux-next: Tree for Feb 17 (mips build failures)

2015-02-18 Thread Markos Chandras
On Wed, Feb 18, 2015 at 07:37:40AM +1100, Stephen Rothwell wrote: > Hi Guenter, > > [Add Ralf to cc] > > On Tue, 17 Feb 2015 09:20:36 -0800 Guenter Roeck wrote: > > > > Build results: > > total: 121 pass: 109 fail: 12 > > Failed builds: > > mips:defconfig > > mips:allmodconfig > >

Re: linux-next: Tree for Feb 17 (mips build failures)

2015-02-18 Thread Markos Chandras
On Wed, Feb 18, 2015 at 07:37:40AM +1100, Stephen Rothwell wrote: Hi Guenter, [Add Ralf to cc] On Tue, 17 Feb 2015 09:20:36 -0800 Guenter Roeck li...@roeck-us.net wrote: Build results: total: 121 pass: 109 fail: 12 Failed builds: mips:defconfig mips:allmodconfig

Re: linux-next: Tree for Feb 17 (mips build failures)

2015-02-18 Thread Guenter Roeck
On 02/18/2015 01:14 AM, Markos Chandras wrote: On Wed, Feb 18, 2015 at 07:37:40AM +1100, Stephen Rothwell wrote: Hi Guenter, [Add Ralf to cc] On Tue, 17 Feb 2015 09:20:36 -0800 Guenter Roeck li...@roeck-us.net wrote: Build results: total: 121 pass: 109 fail: 12 Failed builds:

Re: linux-next: Tree for Feb 17 (mips build failures)

2015-02-18 Thread Markos Chandras
On Wed, Feb 18, 2015 at 05:54:57AM -0800, Guenter Roeck wrote: On 02/18/2015 01:14 AM, Markos Chandras wrote: On Wed, Feb 18, 2015 at 07:37:40AM +1100, Stephen Rothwell wrote: Hi Guenter, [Add Ralf to cc] On Tue, 17 Feb 2015 09:20:36 -0800 Guenter Roeck li...@roeck-us.net wrote:

Re: linux-next: Tree for Feb 17 (i2c-designware-baytrail.c)

2015-02-17 Thread David E. Box
Hi Wolfram, On Tue, Feb 17, 2015 at 08:11:58PM +0100, Wolfram Sang wrote: > Randy, > > thanks for the report! > > > I suppose someone could make that: > > > > depends on I2C_DESIGNWARE_PLATFORM && IOSF_MBI=y && ACPI > > > > or even make I2C_DESIGNWARE_BAYTRAIL be a tristate symbol. > >

Re: linux-next: Tree for Feb 17 (mips build failures)

2015-02-17 Thread Stephen Rothwell
Hi Guenter, [Add Ralf to cc] On Tue, 17 Feb 2015 09:20:36 -0800 Guenter Roeck wrote: > > Build results: > total: 121 pass: 109 fail: 12 > Failed builds: > mips:defconfig > mips:allmodconfig > mips:bcm47xx_defconfig > mips:bcm63xx_defconfig >

Re: linux-next: Tree for Feb 17 (i2c-designware-baytrail.c)

2015-02-17 Thread Wolfram Sang
Randy, thanks for the report! > I suppose someone could make that: > > depends on I2C_DESIGNWARE_PLATFORM && IOSF_MBI=y && ACPI > > or even make I2C_DESIGNWARE_BAYTRAIL be a tristate symbol. I'll wait a day for input from David what he prefers, because I don't own/know this platform. If

Re: linux-next: Tree for Feb 17 (i2c-designware-baytrail.c)

2015-02-17 Thread Randy Dunlap
On 02/16/15 21:02, Stephen Rothwell wrote: > 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 20150216: > on i386, when CONFIG_IOSF_MBI=m and CONFIG_I2C_DESIGNWARE_BAYTRAIL=y:

Re: linux-next: Tree for Feb 17 (mips build failures)

2015-02-17 Thread Guenter Roeck
On Tue, Feb 17, 2015 at 04:02:21PM +1100, Stephen Rothwell wrote: > 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 20150216: > > The slave-dma tree lost its build failure. > >

Re: linux-next: Tree for Feb 17 (mips build failures)

2015-02-17 Thread Guenter Roeck
On Tue, Feb 17, 2015 at 04:02:21PM +1100, Stephen Rothwell wrote: 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 20150216: The slave-dma tree lost its build failure. Non-merge commits

Re: linux-next: Tree for Feb 17 (mips build failures)

2015-02-17 Thread Stephen Rothwell
Hi Guenter, [Add Ralf to cc] On Tue, 17 Feb 2015 09:20:36 -0800 Guenter Roeck li...@roeck-us.net wrote: Build results: total: 121 pass: 109 fail: 12 Failed builds: mips:defconfig mips:allmodconfig mips:bcm47xx_defconfig mips:bcm63xx_defconfig

Re: linux-next: Tree for Feb 17 (i2c-designware-baytrail.c)

2015-02-17 Thread Randy Dunlap
On 02/16/15 21:02, Stephen Rothwell wrote: 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 20150216: on i386, when CONFIG_IOSF_MBI=m and CONFIG_I2C_DESIGNWARE_BAYTRAIL=y:

Re: linux-next: Tree for Feb 17 (i2c-designware-baytrail.c)

2015-02-17 Thread Wolfram Sang
Randy, thanks for the report! I suppose someone could make that: depends on I2C_DESIGNWARE_PLATFORM IOSF_MBI=y ACPI or even make I2C_DESIGNWARE_BAYTRAIL be a tristate symbol. I'll wait a day for input from David what he prefers, because I don't own/know this platform. If there is

Re: linux-next: Tree for Feb 17 (i2c-designware-baytrail.c)

2015-02-17 Thread David E. Box
Hi Wolfram, On Tue, Feb 17, 2015 at 08:11:58PM +0100, Wolfram Sang wrote: Randy, thanks for the report! I suppose someone could make that: depends on I2C_DESIGNWARE_PLATFORM IOSF_MBI=y ACPI or even make I2C_DESIGNWARE_BAYTRAIL be a tristate symbol. I'll wait a day for

linux-next: Tree for Feb 17

2015-02-16 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 20150216: The slave-dma tree lost its build failure. Non-merge commits (relative to Linus' tree): 2980 2871 files changed, 124415 insertions(+),

linux-next: Tree for Feb 17

2015-02-16 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 20150216: The slave-dma tree lost its build failure. Non-merge commits (relative to Linus' tree): 2980 2871 files changed, 124415 insertions(+),

Re: linux-next: Tree for Feb 17 (pinctrl-msm)

2014-02-25 Thread Linus Walleij
On Mon, Feb 24, 2014 at 8:28 PM, Bjorn Andersson wrote: > This comes from the request of having everything as a module, to reduce the > size of the multi-platform ARM builds. I would say that the important part > related to that would be to keep the platform specific tables in modules. > > But

Re: linux-next: Tree for Feb 17 (pinctrl-msm)

2014-02-25 Thread Linus Walleij
On Mon, Feb 24, 2014 at 7:41 PM, Josh Cartwright wrote: > On Mon, Feb 24, 2014 at 10:14:45AM -0800, Randy Dunlap wrote: > Without too much effort, I can get this to fail just by making > CONFIG_PINCTRL_MSM=m. handle_bad_irq isn't marked EXPORT_SYMBOL*, so > hence the warning. > > Whether or not

Re: linux-next: Tree for Feb 17 (pinctrl-msm)

2014-02-25 Thread Linus Walleij
On Mon, Feb 24, 2014 at 7:41 PM, Josh Cartwright jo...@codeaurora.org wrote: On Mon, Feb 24, 2014 at 10:14:45AM -0800, Randy Dunlap wrote: Without too much effort, I can get this to fail just by making CONFIG_PINCTRL_MSM=m. handle_bad_irq isn't marked EXPORT_SYMBOL*, so hence the warning.

Re: linux-next: Tree for Feb 17 (pinctrl-msm)

2014-02-25 Thread Linus Walleij
On Mon, Feb 24, 2014 at 8:28 PM, Bjorn Andersson bjorn.anders...@sonymobile.com wrote: This comes from the request of having everything as a module, to reduce the size of the multi-platform ARM builds. I would say that the important part related to that would be to keep the platform specific

Re: linux-next: Tree for Feb 17 (pinctrl-msm)

2014-02-24 Thread Bjorn Andersson
On Mon 24 Feb 10:41 PST 2014, Josh Cartwright wrote: [...] > > Without too much effort, I can get this to fail just by making > CONFIG_PINCTRL_MSM=m. handle_bad_irq isn't marked EXPORT_SYMBOL*, so > hence the warning. > Ohh, yeah I missed that. > Whether or not this is intentional is not

Re: linux-next: Tree for Feb 17 (pinctrl-msm)

2014-02-24 Thread Randy Dunlap
On 02/24/2014 10:41 AM, Josh Cartwright wrote: > On Mon, Feb 24, 2014 at 10:14:45AM -0800, Randy Dunlap wrote: >> On 02/24/2014 09:46 AM, Bjorn Andersson wrote: >>> On Mon 24 Feb 06:46 PST 2014, Linus Walleij wrote: On Mon, Feb 17, 2014 at 6:33 PM, Randy Dunlap wrote: > On

Re: linux-next: Tree for Feb 17 (pinctrl-msm)

2014-02-24 Thread Josh Cartwright
On Mon, Feb 24, 2014 at 10:14:45AM -0800, Randy Dunlap wrote: > On 02/24/2014 09:46 AM, Bjorn Andersson wrote: > > On Mon 24 Feb 06:46 PST 2014, Linus Walleij wrote: > >> On Mon, Feb 17, 2014 at 6:33 PM, Randy Dunlap > >> wrote: > >>> On 02/16/2014 10:23 PM, Stephen Rothwell wrote: > >>> ERROR:

Re: linux-next: Tree for Feb 17 (pinctrl-msm)

2014-02-24 Thread Randy Dunlap
On 02/24/2014 09:46 AM, Bjorn Andersson wrote: > On Mon 24 Feb 06:46 PST 2014, Linus Walleij wrote: > >> On Mon, Feb 17, 2014 at 6:33 PM, Randy Dunlap wrote: >>> On 02/16/2014 10:23 PM, Stephen Rothwell wrote: Hi all, If you see failures in building this tree due to missing

Re: linux-next: Tree for Feb 17 (pinctrl-msm)

2014-02-24 Thread Bjorn Andersson
On Mon 24 Feb 06:46 PST 2014, Linus Walleij wrote: > On Mon, Feb 17, 2014 at 6:33 PM, Randy Dunlap wrote: > > On 02/16/2014 10:23 PM, Stephen Rothwell wrote: > >> Hi all, > >> > >> If you see failures in building this tree due to missing declarations of > >> k..alloc/free, then it may be caused

Re: linux-next: Tree for Feb 17 (pinctrl-msm)

2014-02-24 Thread Linus Walleij
On Mon, Feb 17, 2014 at 6:33 PM, Randy Dunlap wrote: > On 02/16/2014 10:23 PM, Stephen Rothwell wrote: >> Hi all, >> >> If you see failures in building this tree due to missing declarations of >> k..alloc/free, then it may be caused by commit 2bd59d48ebfb ("cgroup: >> convert to kernfs"). Please

Re: linux-next: Tree for Feb 17 (pinctrl-msm)

2014-02-24 Thread Linus Walleij
On Mon, Feb 17, 2014 at 6:33 PM, Randy Dunlap rdun...@infradead.org wrote: On 02/16/2014 10:23 PM, Stephen Rothwell wrote: Hi all, If you see failures in building this tree due to missing declarations of k..alloc/free, then it may be caused by commit 2bd59d48ebfb (cgroup: convert to kernfs).

Re: linux-next: Tree for Feb 17 (pinctrl-msm)

2014-02-24 Thread Bjorn Andersson
On Mon 24 Feb 06:46 PST 2014, Linus Walleij wrote: On Mon, Feb 17, 2014 at 6:33 PM, Randy Dunlap rdun...@infradead.org wrote: On 02/16/2014 10:23 PM, Stephen Rothwell wrote: Hi all, If you see failures in building this tree due to missing declarations of k..alloc/free, then it may be

Re: linux-next: Tree for Feb 17 (pinctrl-msm)

2014-02-24 Thread Randy Dunlap
On 02/24/2014 09:46 AM, Bjorn Andersson wrote: On Mon 24 Feb 06:46 PST 2014, Linus Walleij wrote: On Mon, Feb 17, 2014 at 6:33 PM, Randy Dunlap rdun...@infradead.org wrote: On 02/16/2014 10:23 PM, Stephen Rothwell wrote: Hi all, If you see failures in building this tree due to missing

Re: linux-next: Tree for Feb 17 (pinctrl-msm)

2014-02-24 Thread Josh Cartwright
On Mon, Feb 24, 2014 at 10:14:45AM -0800, Randy Dunlap wrote: On 02/24/2014 09:46 AM, Bjorn Andersson wrote: On Mon 24 Feb 06:46 PST 2014, Linus Walleij wrote: On Mon, Feb 17, 2014 at 6:33 PM, Randy Dunlap rdun...@infradead.org wrote: On 02/16/2014 10:23 PM, Stephen Rothwell wrote:

Re: linux-next: Tree for Feb 17 (pinctrl-msm)

2014-02-24 Thread Randy Dunlap
On 02/24/2014 10:41 AM, Josh Cartwright wrote: On Mon, Feb 24, 2014 at 10:14:45AM -0800, Randy Dunlap wrote: On 02/24/2014 09:46 AM, Bjorn Andersson wrote: On Mon 24 Feb 06:46 PST 2014, Linus Walleij wrote: On Mon, Feb 17, 2014 at 6:33 PM, Randy Dunlap rdun...@infradead.org wrote: On

Re: linux-next: Tree for Feb 17 (pinctrl-msm)

2014-02-24 Thread Bjorn Andersson
On Mon 24 Feb 10:41 PST 2014, Josh Cartwright wrote: [...] Without too much effort, I can get this to fail just by making CONFIG_PINCTRL_MSM=m. handle_bad_irq isn't marked EXPORT_SYMBOL*, so hence the warning. Ohh, yeah I missed that. Whether or not this is intentional is not clear.

Re: linux-next: Tree for Feb 17 (pinctrl-msm)

2014-02-17 Thread Randy Dunlap
On 02/16/2014 10:23 PM, Stephen Rothwell wrote: > Hi all, > > If you see failures in building this tree due to missing declarations of > k..alloc/free, then it may be caused by commit 2bd59d48ebfb ("cgroup: > convert to kernfs"). Please send Tejun Heo a patch > adding an inclusion of

Re: linux-next: Tree for Feb 17 (pinctrl-msm)

2014-02-17 Thread Randy Dunlap
On 02/16/2014 10:23 PM, Stephen Rothwell wrote: Hi all, If you see failures in building this tree due to missing declarations of k..alloc/free, then it may be caused by commit 2bd59d48ebfb (cgroup: convert to kernfs). Please send Tejun Heo t...@kernel.org a patch adding an inclusion of

linux-next: Tree for Feb 17

2014-02-16 Thread Stephen Rothwell
Hi all, If you see failures in building this tree due to missing declarations of k..alloc/free, then it may be caused by commit 2bd59d48ebfb ("cgroup: convert to kernfs"). Please send Tejun Heo a patch adding an inclusion of linux/slab.h to the appropriate file(s). This tree fails (more than

linux-next: Tree for Feb 17

2014-02-16 Thread Stephen Rothwell
Hi all, If you see failures in building this tree due to missing declarations of k..alloc/free, then it may be caused by commit 2bd59d48ebfb (cgroup: convert to kernfs). Please send Tejun Heo t...@kernel.org a patch adding an inclusion of linux/slab.h to the appropriate file(s). This tree fails