Re: linux-next: build failure after merge of the staging tree

On Mon, 29 Mar 2021 at 09:15, Greg KH wrote: > > On Mon, Mar 29, 2021 at 04:55:25PM +1100, Stephen Rothwell wrote: > > Hi all, > > > > After merging the staging tree, today's linux-next build (x86_64 > > allmodconfig) failed like this: > > > > drivers/iio/adc/ti-ads131e08.c: In function

Re: linux-next: build failure after merge of the staging tree

On Mon, Mar 29, 2021 at 04:55:25PM +1100, Stephen Rothwell wrote: > Hi all, > > After merging the staging tree, today's linux-next build (x86_64 > allmodconfig) failed like this: > > drivers/iio/adc/ti-ads131e08.c: In function 'ads131e08_read_reg': > drivers/iio/adc/ti-ads131e08.c:180:5: error:

linux-next: build failure after merge of the staging tree

Hi all, After merging the staging tree, today's linux-next build (x86_64 allmodconfig) failed like this: drivers/iio/adc/ti-ads131e08.c: In function 'ads131e08_read_reg': drivers/iio/adc/ti-ads131e08.c:180:5: error: 'struct spi_transfer' has no member named 'delay_usecs' 180 |.delay_usecs

Re: linux-next: build failure after merge of the staging tree

Hi all, On Mon, 7 Dec 2020 16:46:01 +1100 Stephen Rothwell wrote: > > Hi all, > > After merging the staging tree, today's linux-next build (x86_64 > allmodconfig) failed like this: > > drivers/iio/trigger/iio-trig-sysfs.c: In function 'iio_sysfs_trigger_probe': >

Re: linux-next: build failure after merge of the staging tree

Hi Greg, On Mon, 7 Dec 2020 10:26:06 +0100 Greg KH wrote: > > > diff --git a/drivers/iio/trigger/iio-trig-sysfs.c > > b/drivers/iio/trigger/iio-trig-sysfs.c > > index 10a3fd29362b..0f6b512a5c37 100644 > > --- a/drivers/iio/trigger/iio-trig-sysfs.c > > +++ b/drivers/iio/trigger/iio-trig-sysfs.c

Re: linux-next: build failure after merge of the staging tree

On Mon, Dec 07, 2020 at 04:46:01PM +1100, Stephen Rothwell wrote: > Hi all, > > After merging the staging tree, today's linux-next build (x86_64 > allmodconfig) failed like this: > > drivers/iio/trigger/iio-trig-sysfs.c: In function 'iio_sysfs_trigger_probe': >

linux-next: build failure after merge of the staging tree

Hi all, After merging the staging tree, today's linux-next build (x86_64 allmodconfig) failed like this: drivers/iio/trigger/iio-trig-sysfs.c: In function 'iio_sysfs_trigger_probe': drivers/iio/trigger/iio-trig-sysfs.c:164:21: error: 'struct irq_work' has no member named 'flags' 164 |

Re: linux-next: build failure after merge of the staging tree

On Tue, Oct 08, 2019 at 01:49:07PM +1100, Stephen Rothwell wrote: > Hi all, > > After merging the staging tree, today's linux-next build (powerpc > allyesconfig) failed like this: > > In file included from include/linux/byteorder/big_endian.h:5, > from

linux-next: build failure after merge of the staging tree

Hi all, After merging the staging tree, today's linux-next build (powerpc allyesconfig) failed like this: In file included from include/linux/byteorder/big_endian.h:5, from arch/powerpc/include/uapi/asm/byteorder.h:14, from include/asm-generic/bitops/le.h:6,

Re: linux-next: build failure after merge of the staging tree

On Mon, Jun 24, 2019 at 05:38:55PM +1000, Stephen Rothwell wrote: > Hi all, > > After merging the staging tree, today's linux-next build (arm > multi_v7_defconfig) failed like this: > > lib/Kconfig:132:error: recursive dependency detected! > lib/Kconfig:132:symbol CRC32 is selected by

linux-next: build failure after merge of the staging tree

Hi all, After merging the staging tree, today's linux-next build (arm multi_v7_defconfig) failed like this: lib/Kconfig:132:error: recursive dependency detected! lib/Kconfig:132:symbol CRC32 is selected by XZ_DEC lib/xz/Kconfig:2: symbol XZ_DEC is selected by FW_LOADER_COMPRESS

Re: linux-next: build failure after merge of the staging tree

On 2018/8/2 15:14, Greg KH wrote: > On Thu, Aug 02, 2018 at 03:01:59PM +0800, Chao Yu wrote: >> Hi Greg, >> >> On 2018/8/2 14:15, Greg KH wrote: >>> On Wed, Aug 01, 2018 at 05:09:13PM +0800, Chao Yu wrote: Hi Stephen, On 2018/7/30 14:31, Gao Xiang wrote: > Hi Stephen, >

Re: linux-next: build failure after merge of the staging tree

On 2018/8/2 15:14, Greg KH wrote: > On Thu, Aug 02, 2018 at 03:01:59PM +0800, Chao Yu wrote: >> Hi Greg, >> >> On 2018/8/2 14:15, Greg KH wrote: >>> On Wed, Aug 01, 2018 at 05:09:13PM +0800, Chao Yu wrote: Hi Stephen, On 2018/7/30 14:31, Gao Xiang wrote: > Hi Stephen, >

Re: linux-next: build failure after merge of the staging tree

On Thu, Aug 02, 2018 at 03:01:59PM +0800, Chao Yu wrote: > Hi Greg, > > On 2018/8/2 14:15, Greg KH wrote: > > On Wed, Aug 01, 2018 at 05:09:13PM +0800, Chao Yu wrote: > >> Hi Stephen, > >> > >> On 2018/7/30 14:31, Gao Xiang wrote: > >>> Hi Stephen, > >>> > >>> On 2018/7/30 14:16, Stephen Rothwell

Re: linux-next: build failure after merge of the staging tree

On Thu, Aug 02, 2018 at 03:01:59PM +0800, Chao Yu wrote: > Hi Greg, > > On 2018/8/2 14:15, Greg KH wrote: > > On Wed, Aug 01, 2018 at 05:09:13PM +0800, Chao Yu wrote: > >> Hi Stephen, > >> > >> On 2018/7/30 14:31, Gao Xiang wrote: > >>> Hi Stephen, > >>> > >>> On 2018/7/30 14:16, Stephen Rothwell

Re: linux-next: build failure after merge of the staging tree

Hi Greg, On 2018/8/2 14:15, Greg KH wrote: > On Wed, Aug 01, 2018 at 05:09:13PM +0800, Chao Yu wrote: >> Hi Stephen, >> >> On 2018/7/30 14:31, Gao Xiang wrote: >>> Hi Stephen, >>> >>> On 2018/7/30 14:16, Stephen Rothwell wrote: Hi Greg, After merging the staging tree, today's

Re: linux-next: build failure after merge of the staging tree

Hi Greg, On 2018/8/2 14:15, Greg KH wrote: > On Wed, Aug 01, 2018 at 05:09:13PM +0800, Chao Yu wrote: >> Hi Stephen, >> >> On 2018/7/30 14:31, Gao Xiang wrote: >>> Hi Stephen, >>> >>> On 2018/7/30 14:16, Stephen Rothwell wrote: Hi Greg, After merging the staging tree, today's

Re: linux-next: build failure after merge of the staging tree

On Wed, Aug 01, 2018 at 05:09:13PM +0800, Chao Yu wrote: > Hi Stephen, > > On 2018/7/30 14:31, Gao Xiang wrote: > > Hi Stephen, > > > > On 2018/7/30 14:16, Stephen Rothwell wrote: > >> Hi Greg, > >> > >> After merging the staging tree, today's linux-next build (x86_64 > >> allmodconfig) failed

Re: linux-next: build failure after merge of the staging tree

On Wed, Aug 01, 2018 at 05:09:13PM +0800, Chao Yu wrote: > Hi Stephen, > > On 2018/7/30 14:31, Gao Xiang wrote: > > Hi Stephen, > > > > On 2018/7/30 14:16, Stephen Rothwell wrote: > >> Hi Greg, > >> > >> After merging the staging tree, today's linux-next build (x86_64 > >> allmodconfig) failed

Re: linux-next: build failure after merge of the staging tree

Hi Stephen, Sorry, yesterday I missed this email due to my email filter. On 2018/8/1 23:07, Stephen Rothwell wrote: > Hi Chao, > > On Wed, 1 Aug 2018 17:09:13 +0800 Chao Yu wrote: >> >> Xiang has submitted several patches as below to fix compiling error on -next >> tree, could you consider to

Re: linux-next: build failure after merge of the staging tree

Hi Stephen, Sorry, yesterday I missed this email due to my email filter. On 2018/8/1 23:07, Stephen Rothwell wrote: > Hi Chao, > > On Wed, 1 Aug 2018 17:09:13 +0800 Chao Yu wrote: >> >> Xiang has submitted several patches as below to fix compiling error on -next >> tree, could you consider to

Re: linux-next: build failure after merge of the staging tree

Hi Chao, On Wed, 1 Aug 2018 17:09:13 +0800 Chao Yu wrote: > > Xiang has submitted several patches as below to fix compiling error on -next > tree, could you consider to merge those temporary fixes into -next after > merging > staging-next's updates, and reenable CONFIG_EROFS_FS for further

Re: linux-next: build failure after merge of the staging tree

Hi Chao, On Wed, 1 Aug 2018 17:09:13 +0800 Chao Yu wrote: > > Xiang has submitted several patches as below to fix compiling error on -next > tree, could you consider to merge those temporary fixes into -next after > merging > staging-next's updates, and reenable CONFIG_EROFS_FS for further

Re: linux-next: build failure after merge of the staging tree

Hi Stephen, On 2018/7/30 14:31, Gao Xiang wrote: > Hi Stephen, > > On 2018/7/30 14:16, Stephen Rothwell wrote: >> Hi Greg, >> >> After merging the staging tree, today's linux-next build (x86_64 >> allmodconfig) failed like this: >> >> drivers/staging/erofs/super.c: In function

Re: linux-next: build failure after merge of the staging tree

Hi Stephen, On 2018/7/30 14:31, Gao Xiang wrote: > Hi Stephen, > > On 2018/7/30 14:16, Stephen Rothwell wrote: >> Hi Greg, >> >> After merging the staging tree, today's linux-next build (x86_64 >> allmodconfig) failed like this: >> >> drivers/staging/erofs/super.c: In function

Re: linux-next: build failure after merge of the staging tree

On 2018/7/30 19:18, David Howells wrote: > Gao Xiang wrote: > >> struct erofs_mount_private priv = { >> .dev_name = dev_name, >> .options = data >> }; >> return mount_bdev(fs_type, flags, dev_name, , erofs_fill_super); >> >> >> However, I have no idea if it is safe to do so in the

Re: linux-next: build failure after merge of the staging tree

On 2018/7/30 19:18, David Howells wrote: > Gao Xiang wrote: > >> struct erofs_mount_private priv = { >> .dev_name = dev_name, >> .options = data >> }; >> return mount_bdev(fs_type, flags, dev_name, , erofs_fill_super); >> >> >> However, I have no idea if it is safe to do so in the

Re: linux-next: build failure after merge of the staging tree

Gao Xiang wrote: > struct erofs_mount_private priv = { > .dev_name = dev_name, > .options = data > }; > return mount_bdev(fs_type, flags, dev_name, , erofs_fill_super); > > > However, I have no idea if it is safe to do so in the future, so I also > change it into a more stardard

Re: linux-next: build failure after merge of the staging tree

Gao Xiang wrote: > struct erofs_mount_private priv = { > .dev_name = dev_name, > .options = data > }; > return mount_bdev(fs_type, flags, dev_name, , erofs_fill_super); > > > However, I have no idea if it is safe to do so in the future, so I also > change it into a more stardard

Re: linux-next: build failure after merge of the staging tree

Hi David, Thanks for your reply :) On 2018/7/30 17:47, David Howells wrote: > Gao Xiang wrote: > >>> sb->s_flags |= MS_RDONLY | MS_NOATIME; > > This should be using SB_* rather than MS_* for interaction with sb->s_flags. Yes, I saw the related discussion and your submission in the

Re: linux-next: build failure after merge of the staging tree

Hi David, Thanks for your reply :) On 2018/7/30 17:47, David Howells wrote: > Gao Xiang wrote: > >>> sb->s_flags |= MS_RDONLY | MS_NOATIME; > > This should be using SB_* rather than MS_* for interaction with sb->s_flags. Yes, I saw the related discussion and your submission in the

Re: linux-next: build failure after merge of the staging tree

Gao Xiang wrote: > > sb->s_flags |= MS_RDONLY | MS_NOATIME; This should be using SB_* rather than MS_* for interaction with sb->s_flags. > > drivers/staging/erofs/super.c: In function 'erofs_mount': > > drivers/staging/erofs/super.c:501:10: warning: passing argument 5 of > > 'mount_bdev'

Re: linux-next: build failure after merge of the staging tree

Gao Xiang wrote: > > sb->s_flags |= MS_RDONLY | MS_NOATIME; This should be using SB_* rather than MS_* for interaction with sb->s_flags. > > drivers/staging/erofs/super.c: In function 'erofs_mount': > > drivers/staging/erofs/super.c:501:10: warning: passing argument 5 of > > 'mount_bdev'

Re: linux-next: build failure after merge of the staging tree

Hi Stephen, On 2018/7/30 14:16, Stephen Rothwell wrote: > Hi Greg, > > After merging the staging tree, today's linux-next build (x86_64 > allmodconfig) failed like this: > > drivers/staging/erofs/super.c: In function 'erofs_read_super': > drivers/staging/erofs/super.c:343:17: error: 'MS_RDONLY'

Re: linux-next: build failure after merge of the staging tree

Hi Stephen, On 2018/7/30 14:16, Stephen Rothwell wrote: > Hi Greg, > > After merging the staging tree, today's linux-next build (x86_64 > allmodconfig) failed like this: > > drivers/staging/erofs/super.c: In function 'erofs_read_super': > drivers/staging/erofs/super.c:343:17: error: 'MS_RDONLY'

linux-next: build failure after merge of the staging tree

Hi Greg, After merging the staging tree, today's linux-next build (x86_64 allmodconfig) failed like this: drivers/staging/erofs/super.c: In function 'erofs_read_super': drivers/staging/erofs/super.c:343:17: error: 'MS_RDONLY' undeclared (first use in this function); did you mean 'IS_RDONLY'?

linux-next: build failure after merge of the staging tree

Hi Greg, After merging the staging tree, today's linux-next build (x86_64 allmodconfig) failed like this: drivers/staging/erofs/super.c: In function 'erofs_read_super': drivers/staging/erofs/super.c:343:17: error: 'MS_RDONLY' undeclared (first use in this function); did you mean 'IS_RDONLY'?

Re: linux-next: build failure after merge of the staging tree

On Tue, Jul 17, 2018 at 09:49:45AM +0300, Ivan Safonov wrote: > On 07/17/2018 09:28 AM, Stephen Rothwell wrote: > > Hi Greg, > > > > After merging the staging tree, today's linux-next build (x86_64 > > allmodconfig) failed like this: > > > > drivers/staging/rtl8188eu/core/rtw_security.c: In

Re: linux-next: build failure after merge of the staging tree

On Tue, Jul 17, 2018 at 09:49:45AM +0300, Ivan Safonov wrote: > On 07/17/2018 09:28 AM, Stephen Rothwell wrote: > > Hi Greg, > > > > After merging the staging tree, today's linux-next build (x86_64 > > allmodconfig) failed like this: > > > > drivers/staging/rtl8188eu/core/rtw_security.c: In

Re: linux-next: build failure after merge of the staging tree

On 07/17/2018 09:28 AM, Stephen Rothwell wrote: Hi Greg, After merging the staging tree, today's linux-next build (x86_64 allmodconfig) failed like this: drivers/staging/rtl8188eu/core/rtw_security.c: In function 'rtw_tkip_decrypt': drivers/staging/rtl8188eu/core/rtw_security.c:399:21: error:

Re: linux-next: build failure after merge of the staging tree

On 07/17/2018 09:28 AM, Stephen Rothwell wrote: Hi Greg, After merging the staging tree, today's linux-next build (x86_64 allmodconfig) failed like this: drivers/staging/rtl8188eu/core/rtw_security.c: In function 'rtw_tkip_decrypt': drivers/staging/rtl8188eu/core/rtw_security.c:399:21: error:

linux-next: build failure after merge of the staging tree

Hi Greg, After merging the staging tree, today's linux-next build (x86_64 allmodconfig) failed like this: drivers/staging/rtl8188eu/core/rtw_security.c: In function 'rtw_tkip_decrypt': drivers/staging/rtl8188eu/core/rtw_security.c:399:21: error: storage size of 'mycontext' isn't known struct

linux-next: build failure after merge of the staging tree

Hi Greg, After merging the staging tree, today's linux-next build (x86_64 allmodconfig) failed like this: drivers/staging/rtl8188eu/core/rtw_security.c: In function 'rtw_tkip_decrypt': drivers/staging/rtl8188eu/core/rtw_security.c:399:21: error: storage size of 'mycontext' isn't known struct

Re: linux-next: build failure after merge of the staging tree

On 26 September 2017 04:54:41 BST, Stephen Rothwell wrote: >Hi Greg, > >After merging the staging tree, today's linux-next build (x86_64 >allmodconfig) failed like this: > >drivers/iio/counter/stm32-lptimer-cnt.c:181:2: error: unknown field >'driver_module' specified in

Re: linux-next: build failure after merge of the staging tree

On 26 September 2017 04:54:41 BST, Stephen Rothwell wrote: >Hi Greg, > >After merging the staging tree, today's linux-next build (x86_64 >allmodconfig) failed like this: > >drivers/iio/counter/stm32-lptimer-cnt.c:181:2: error: unknown field >'driver_module' specified in initializer >

linux-next: build failure after merge of the staging tree

Hi Greg, After merging the staging tree, today's linux-next build (x86_64 allmodconfig) failed like this: drivers/iio/counter/stm32-lptimer-cnt.c:181:2: error: unknown field 'driver_module' specified in initializer .driver_module = THIS_MODULE, ^ In file included from

linux-next: build failure after merge of the staging tree

Hi Greg, After merging the staging tree, today's linux-next build (x86_64 allmodconfig) failed like this: drivers/iio/counter/stm32-lptimer-cnt.c:181:2: error: unknown field 'driver_module' specified in initializer .driver_module = THIS_MODULE, ^ In file included from

Re: linux-next: build failure after merge of the staging tree

On Mon, May 01, 2017 at 02:42:18PM +1000, Stephen Rothwell wrote: > Hi Greg, > > After merging the staging tree, today's linux-next build (x86_64 > allmodconfig) failed like this: > > drivers/staging/rtl8723bs/os_dep/ioctl_cfg80211.c: In function > 'rtw_cfg80211_indicate_connect': >

Re: linux-next: build failure after merge of the staging tree

On Mon, May 01, 2017 at 02:42:18PM +1000, Stephen Rothwell wrote: > Hi Greg, > > After merging the staging tree, today's linux-next build (x86_64 > allmodconfig) failed like this: > > drivers/staging/rtl8723bs/os_dep/ioctl_cfg80211.c: In function > 'rtw_cfg80211_indicate_connect': >

linux-next: build failure after merge of the staging tree

Hi Greg, After merging the staging tree, today's linux-next build (x86_64 allmodconfig) failed like this: drivers/staging/rtl8723bs/os_dep/ioctl_cfg80211.c: In function 'rtw_cfg80211_indicate_connect': drivers/staging/rtl8723bs/os_dep/ioctl_cfg80211.c:552:6: error: passing argument 2 of

linux-next: build failure after merge of the staging tree

Hi Greg, After merging the staging tree, today's linux-next build (x86_64 allmodconfig) failed like this: drivers/staging/rtl8723bs/os_dep/ioctl_cfg80211.c: In function 'rtw_cfg80211_indicate_connect': drivers/staging/rtl8723bs/os_dep/ioctl_cfg80211.c:552:6: error: passing argument 2 of

Re: linux-next: build failure after merge of the staging tree

On Thu, Apr 27, 2017 at 02:20:21PM +1000, Stephen Rothwell wrote: > Hi Greg, > > After merging the staging tree, today's linux-next build (x86_64 > allmodconfig) failed like this: > > drivers/staging/rtl8723bs/os_dep/ioctl_cfg80211.c: In function > 'rtw_cfg80211_preinit_wiphy': >

Re: linux-next: build failure after merge of the staging tree

On Thu, Apr 27, 2017 at 02:20:21PM +1000, Stephen Rothwell wrote: > Hi Greg, > > After merging the staging tree, today's linux-next build (x86_64 > allmodconfig) failed like this: > > drivers/staging/rtl8723bs/os_dep/ioctl_cfg80211.c: In function > 'rtw_cfg80211_preinit_wiphy': >

linux-next: build failure after merge of the staging tree

Hi Greg, After merging the staging tree, today's linux-next build (x86_64 allmodconfig) failed like this: drivers/staging/rtl8723bs/os_dep/ioctl_cfg80211.c: In function 'rtw_cfg80211_preinit_wiphy': drivers/staging/rtl8723bs/os_dep/ioctl_cfg80211.c:3409:18: error:

linux-next: build failure after merge of the staging tree

Hi Greg, After merging the staging tree, today's linux-next build (x86_64 allmodconfig) failed like this: drivers/staging/rtl8723bs/os_dep/ioctl_cfg80211.c: In function 'rtw_cfg80211_preinit_wiphy': drivers/staging/rtl8723bs/os_dep/ioctl_cfg80211.c:3409:18: error:

Re: linux-next: build failure after merge of the staging tree

On Tue, Apr 18, 2017 at 04:26:52PM +1000, Stephen Rothwell wrote: > Hi Greg, > > On Tue, 18 Apr 2017 07:54:40 +0200 Greg KH wrote: > > > > On Tue, Apr 18, 2017 at 03:32:20PM +1000, Stephen Rothwell wrote: > > > Hi Greg, > > > > > > After merging the staging tree, today's

Re: linux-next: build failure after merge of the staging tree

On Tue, Apr 18, 2017 at 04:26:52PM +1000, Stephen Rothwell wrote: > Hi Greg, > > On Tue, 18 Apr 2017 07:54:40 +0200 Greg KH wrote: > > > > On Tue, Apr 18, 2017 at 03:32:20PM +1000, Stephen Rothwell wrote: > > > Hi Greg, > > > > > > After merging the staging tree, today's linux-next build

Re: linux-next: build failure after merge of the staging tree

On Tue, 2017-04-18 at 15:53 +1000, Stephen Rothwell wrote: > Caused by commit > >   554c0a3abf21 ("staging: Add rtl8723bs sdio wifi driver") Oh, another new driver :) > interacting with commit > >   818a986e4eba ("cfg80211: move add/change interface monitor flags > into params") > > from the

Re: linux-next: build failure after merge of the staging tree

On Tue, 2017-04-18 at 15:53 +1000, Stephen Rothwell wrote: > Caused by commit > >   554c0a3abf21 ("staging: Add rtl8723bs sdio wifi driver") Oh, another new driver :) > interacting with commit > >   818a986e4eba ("cfg80211: move add/change interface monitor flags > into params") > > from the

Re: linux-next: build failure after merge of the staging tree

Hi Greg, On Tue, 18 Apr 2017 07:54:40 +0200 Greg KH wrote: > > On Tue, Apr 18, 2017 at 03:32:20PM +1000, Stephen Rothwell wrote: > > Hi Greg, > > > > After merging the staging tree, today's linux-next build (x86_64 > > allmodconfig) failed like this: > > > > make[7]: *** No

Re: linux-next: build failure after merge of the staging tree

Hi Greg, On Tue, 18 Apr 2017 07:54:40 +0200 Greg KH wrote: > > On Tue, Apr 18, 2017 at 03:32:20PM +1000, Stephen Rothwell wrote: > > Hi Greg, > > > > After merging the staging tree, today's linux-next build (x86_64 > > allmodconfig) failed like this: > > > > make[7]: *** No rule to make target

Re: linux-next: build failure after merge of the staging tree

On Tue, Apr 18, 2017 at 03:32:20PM +1000, Stephen Rothwell wrote: > Hi Greg, > > After merging the staging tree, today's linux-next build (x86_64 > allmodconfig) failed like this: > > make[7]: *** No rule to make target >

Re: linux-next: build failure after merge of the staging tree

On Tue, Apr 18, 2017 at 03:32:20PM +1000, Stephen Rothwell wrote: > Hi Greg, > > After merging the staging tree, today's linux-next build (x86_64 > allmodconfig) failed like this: > > make[7]: *** No rule to make target >

linux-next: build failure after merge of the staging tree

Hi all, After merging the staging tree, today's linux-next build (x86_64 allmodconfig) failed like this: drivers/staging/rtl8723bs/os_dep/ioctl_cfg80211.c:3426:25: error: initialization from incompatible pointer type [-Werror=incompatible-pointer-types] .change_virtual_intf =

linux-next: build failure after merge of the staging tree

Hi all, After merging the staging tree, today's linux-next build (x86_64 allmodconfig) failed like this: drivers/staging/rtl8723bs/os_dep/ioctl_cfg80211.c:3426:25: error: initialization from incompatible pointer type [-Werror=incompatible-pointer-types] .change_virtual_intf =

linux-next: build failure after merge of the staging tree

Hi Greg, After merging the staging tree, today's linux-next build (x86_64 allmodconfig) failed like this: make[7]: *** No rule to make target 'drivers/staging/media/atomisp/pci/atomisp2/css2400/isp/kernels/uds/uds_1.0/ia_css_uds.host.o', needed by

linux-next: build failure after merge of the staging tree

Hi Greg, After merging the staging tree, today's linux-next build (x86_64 allmodconfig) failed like this: make[7]: *** No rule to make target 'drivers/staging/media/atomisp/pci/atomisp2/css2400/isp/kernels/uds/uds_1.0/ia_css_uds.host.o', needed by

Re: linux-next: build failure after merge of the staging tree

Hi Greg, On Tue, 11 Apr 2017 07:38:32 +0200 Greg KH wrote: > > I should have this fixed now, sorry for taking so long. Thanks and no worries. -- Cheers, Stephen Rothwell

Re: linux-next: build failure after merge of the staging tree

Hi Greg, On Tue, 11 Apr 2017 07:38:32 +0200 Greg KH wrote: > > I should have this fixed now, sorry for taking so long. Thanks and no worries. -- Cheers, Stephen Rothwell

Re: linux-next: build failure after merge of the staging tree

On Tue, Apr 11, 2017 at 07:15:42AM +0200, Greg KH wrote: > On Tue, Apr 11, 2017 at 03:04:40PM +1000, Stephen Rothwell wrote: > > Hi Greg, > > > > After merging the staging tree, today's linux-next build (powerpc > > allyesconfig - I presume that an x86_64 allyesconfig will fail the > > same way)

Re: linux-next: build failure after merge of the staging tree

On Tue, Apr 11, 2017 at 07:15:42AM +0200, Greg KH wrote: > On Tue, Apr 11, 2017 at 03:04:40PM +1000, Stephen Rothwell wrote: > > Hi Greg, > > > > After merging the staging tree, today's linux-next build (powerpc > > allyesconfig - I presume that an x86_64 allyesconfig will fail the > > same way)

Re: linux-next: build failure after merge of the staging tree

On Tue, Apr 11, 2017 at 03:04:40PM +1000, Stephen Rothwell wrote: > Hi Greg, > > After merging the staging tree, today's linux-next build (powerpc > allyesconfig - I presume that an x86_64 allyesconfig will fail the > same way) failed like this: > >

Re: linux-next: build failure after merge of the staging tree

On Tue, Apr 11, 2017 at 03:04:40PM +1000, Stephen Rothwell wrote: > Hi Greg, > > After merging the staging tree, today's linux-next build (powerpc > allyesconfig - I presume that an x86_64 allyesconfig will fail the > same way) failed like this: > >

linux-next: build failure after merge of the staging tree

Hi Greg, After merging the staging tree, today's linux-next build (powerpc allyesconfig - I presume that an x86_64 allyesconfig will fail the same way) failed like this: drivers/staging/rtl8188eu/core/rtw_wlan_util.o: In function `.rtw_get_oper_ch': (.text+0x9d0): multiple definition of

linux-next: build failure after merge of the staging tree

Hi Greg, After merging the staging tree, today's linux-next build (powerpc allyesconfig - I presume that an x86_64 allyesconfig will fail the same way) failed like this: drivers/staging/rtl8188eu/core/rtw_wlan_util.o: In function `.rtw_get_oper_ch': (.text+0x9d0): multiple definition of

linux-next: build failure after merge of the staging tree

Hi Greg, After merging the staging tree, today's linux-next build (x86_64 allmodconfig) failed like this: drivers/staging/rtl8723bs/core/rtw_ieee80211.c: In function 'rtw_macaddr_cfg': drivers/staging/rtl8723bs/core/rtw_ieee80211.c:1193:22: error: implicit declaration of function

linux-next: build failure after merge of the staging tree

Hi Greg, After merging the staging tree, today's linux-next build (x86_64 allmodconfig) failed like this: drivers/staging/rtl8723bs/core/rtw_ieee80211.c: In function 'rtw_macaddr_cfg': drivers/staging/rtl8723bs/core/rtw_ieee80211.c:1193:22: error: implicit declaration of function

Re: linux-next: build failure after merge of the staging tree

On Tue, Mar 07, 2017 at 08:49:47PM +1100, Stephen Rothwell wrote: > Hi Greg, > > On Tue, 7 Mar 2017 09:47:29 +0100 Greg KH wrote: > > > > I really can't duplicate this here, but you and the kbuild bot are > > hitting this now. in drivers/staging/media/atomisp/Makefile we have: >

Re: linux-next: build failure after merge of the staging tree

On Tue, Mar 07, 2017 at 08:49:47PM +1100, Stephen Rothwell wrote: > Hi Greg, > > On Tue, 7 Mar 2017 09:47:29 +0100 Greg KH wrote: > > > > I really can't duplicate this here, but you and the kbuild bot are > > hitting this now. in drivers/staging/media/atomisp/Makefile we have: > >

Re: linux-next: build failure after merge of the staging tree

Hi Greg, On Tue, 7 Mar 2017 09:47:29 +0100 Greg KH wrote: > > I really can't duplicate this here, but you and the kbuild bot are > hitting this now. in drivers/staging/media/atomisp/Makefile we have: > LINUXINCLUDE+= -I drivers/staging/media/atomisp/include/ > to

Re: linux-next: build failure after merge of the staging tree

Hi Greg, On Tue, 7 Mar 2017 09:47:29 +0100 Greg KH wrote: > > I really can't duplicate this here, but you and the kbuild bot are > hitting this now. in drivers/staging/media/atomisp/Makefile we have: > LINUXINCLUDE+= -I drivers/staging/media/atomisp/include/ > to point the include

Re: linux-next: build failure after merge of the staging tree

On Tue, Mar 07, 2017 at 12:25:42PM +1100, Stephen Rothwell wrote: > Hi Greg, > > After merging the staging tree, today's linux-next build (x86_64 > allmodconfig) failed like this: > > drivers/staging/media/atomisp/i2c/mt9m114.c:38:41: fatal error: > linux/atomisp_gmin_platform.h: No such file

Re: linux-next: build failure after merge of the staging tree

On Tue, Mar 07, 2017 at 12:25:42PM +1100, Stephen Rothwell wrote: > Hi Greg, > > After merging the staging tree, today's linux-next build (x86_64 > allmodconfig) failed like this: > > drivers/staging/media/atomisp/i2c/mt9m114.c:38:41: fatal error: > linux/atomisp_gmin_platform.h: No such file

Re: linux-next: build failure after merge of the staging tree

On Tue, Mar 07, 2017 at 12:25:42PM +1100, Stephen Rothwell wrote: > Hi Greg, > > After merging the staging tree, today's linux-next build (x86_64 > allmodconfig) failed like this: > > drivers/staging/media/atomisp/i2c/mt9m114.c:38:41: fatal error: > linux/atomisp_gmin_platform.h: No such file

Re: linux-next: build failure after merge of the staging tree

On Tue, Mar 07, 2017 at 12:25:42PM +1100, Stephen Rothwell wrote: > Hi Greg, > > After merging the staging tree, today's linux-next build (x86_64 > allmodconfig) failed like this: > > drivers/staging/media/atomisp/i2c/mt9m114.c:38:41: fatal error: > linux/atomisp_gmin_platform.h: No such file

linux-next: build failure after merge of the staging tree

Hi Greg, After merging the staging tree, today's linux-next build (x86_64 allmodconfig) failed like this: drivers/staging/media/atomisp/i2c/mt9m114.c:38:41: fatal error: linux/atomisp_gmin_platform.h: No such file or directory drivers/staging/media/atomisp/i2c/gc2235.c:32:41: fatal error:

linux-next: build failure after merge of the staging tree

Hi Greg, After merging the staging tree, today's linux-next build (x86_64 allmodconfig) failed like this: drivers/staging/media/atomisp/i2c/mt9m114.c:38:41: fatal error: linux/atomisp_gmin_platform.h: No such file or directory drivers/staging/media/atomisp/i2c/gc2235.c:32:41: fatal error:

Re: linux-next: build failure after merge of the staging tree

On Fri, May 13, 2016 at 01:15:38PM +1000, Stephen Rothwell wrote: > Hi Greg, > > After merging the staging tree, today's linux-next build (x86_64 > allmodconfig) failed like this: > > drivers/staging/lustre/lnet/klnds/o2iblnd/o2iblnd.c:1706:9: > error: too few arguments to function

Re: linux-next: build failure after merge of the staging tree

On Fri, May 13, 2016 at 01:15:38PM +1000, Stephen Rothwell wrote: > Hi Greg, > > After merging the staging tree, today's linux-next build (x86_64 > allmodconfig) failed like this: > > drivers/staging/lustre/lnet/klnds/o2iblnd/o2iblnd.c:1706:9: > error: too few arguments to function

linux-next: build failure after merge of the staging tree

Hi Greg, After merging the staging tree, today's linux-next build (x86_64 allmodconfig) failed like this: drivers/staging/lustre/lnet/klnds/o2iblnd/o2iblnd.c:1706:9: error: too few arguments to function 'ib_map_mr_sg' n = ib_map_mr_sg(mr, tx->tx_frags, ^ In file included from

linux-next: build failure after merge of the staging tree

Hi Greg, After merging the staging tree, today's linux-next build (x86_64 allmodconfig) failed like this: drivers/staging/lustre/lnet/klnds/o2iblnd/o2iblnd.c:1706:9: error: too few arguments to function 'ib_map_mr_sg' n = ib_map_mr_sg(mr, tx->tx_frags, ^ In file included from

Re: linux-next: build failure after merge of the staging tree

Hi Stephen, all, > Caused by commit c5c77ba18ea6 ("staging: wilc1000: Add SDIO/SPI 802.11 > driver") from the staging tree interacting with commit 80279fb7ba5b > ("cfg80211: properly send NL80211_ATTR_DISCONNECTED_BY_AP in > disconnect") from the net-next tree. I thought I fixed it all, but it

linux-next: build failure after merge of the staging tree

Hi Greg, After merging the staging tree, today's linux-next build (x86_64 allmodconfig) failed like this: drivers/staging/wilc1000/wilc_wfi_cfgoperations.c:681:3: error: too few arguments to function 'cfg80211_disconnected' cfg80211_disconnected(dev, pstrDisconnectNotifInfo->u16reason,

linux-next: build failure after merge of the staging tree

Hi Greg, After merging the staging tree, today's linux-next build (x86_64 allmodconfig) failed like this: drivers/staging/wilc1000/wilc_wfi_cfgoperations.c:681:3: error: too few arguments to function 'cfg80211_disconnected' cfg80211_disconnected(dev, pstrDisconnectNotifInfo-u16reason,

Re: linux-next: build failure after merge of the staging tree

Hi Stephen, all, Caused by commit c5c77ba18ea6 (staging: wilc1000: Add SDIO/SPI 802.11 driver) from the staging tree interacting with commit 80279fb7ba5b (cfg80211: properly send NL80211_ATTR_DISCONNECTED_BY_AP in disconnect) from the net-next tree. I thought I fixed it all, but it looks

Re: linux-next: build failure after merge of the staging tree

Hi Greg, On Tue, 10 Mar 2015 16:08:15 +0100 Greg KH wrote: > > Sorry about that. Yes, I know it's a mess. The build error on ppc > should now be fixed in my tree. The build warnings are still there > (some are gone). I should just go fix them up myself, and will do so > tonight if I don't

Re: linux-next: build failure after merge of the staging tree

On Tue, Mar 10, 2015 at 04:08:15PM +0100, Greg KH wrote: > On Tue, Mar 10, 2015 at 04:07:28PM +1100, Stephen Rothwell wrote: > > Hi Greg, > > > > After merging the staging tree, today's linux-next build (powerpc > > allyesconfig) failed like this: > > > > In file included from

Re: linux-next: build failure after merge of the staging tree

On Tue, Mar 10, 2015 at 04:07:28PM +1100, Stephen Rothwell wrote: > Hi Greg, > > After merging the staging tree, today's linux-next build (powerpc > allyesconfig) failed like this: > > In file included from include/linux/module.h:17:0, > from drivers/staging/sm750fb/sm750.c:2: >

Re: linux-next: build failure after merge of the staging tree

On Tue, Mar 10, 2015 at 04:07:28PM +1100, Stephen Rothwell wrote: Hi Greg, After merging the staging tree, today's linux-next build (powerpc allyesconfig) failed like this: In file included from include/linux/module.h:17:0, from drivers/staging/sm750fb/sm750.c:2:

Re: linux-next: build failure after merge of the staging tree

On Tue, Mar 10, 2015 at 04:08:15PM +0100, Greg KH wrote: On Tue, Mar 10, 2015 at 04:07:28PM +1100, Stephen Rothwell wrote: Hi Greg, After merging the staging tree, today's linux-next build (powerpc allyesconfig) failed like this: In file included from include/linux/module.h:17:0,

  1   2   >