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

Great, thanks! Oded On Tue, Jul 28, 2020 at 8:19 PM Greg KH wrote: > > On Tue, Jul 28, 2020 at 07:17:05PM +0200, Greg KH wrote: > > On Tue, Jul 28, 2020 at 06:23:59PM +1000, Stephen Rothwell wrote: > > > Hi Greg, > > > > > > On Tue, 28 Jul 2020 09:53:36 +0200 Greg KH wrote: > > > > > > > > On

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

On Tue, Jul 28, 2020 at 07:17:05PM +0200, Greg KH wrote: > On Tue, Jul 28, 2020 at 06:23:59PM +1000, Stephen Rothwell wrote: > > Hi Greg, > > > > On Tue, 28 Jul 2020 09:53:36 +0200 Greg KH wrote: > > > > > > On Tue, Jul 28, 2020 at 05:33:31PM +1000, Stephen Rothwell wrote: > > > > Hi Greg, > > >

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

On Tue, Jul 28, 2020 at 06:23:59PM +1000, Stephen Rothwell wrote: > Hi Greg, > > On Tue, 28 Jul 2020 09:53:36 +0200 Greg KH wrote: > > > > On Tue, Jul 28, 2020 at 05:33:31PM +1000, Stephen Rothwell wrote: > > > Hi Greg, > > > > > > On Mon, 27 Jul 2020 11:24:48 +0200 Greg KH wrote: > > > > >

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

Hi Greg, On Tue, 28 Jul 2020 09:53:36 +0200 Greg KH wrote: > > On Tue, Jul 28, 2020 at 05:33:31PM +1000, Stephen Rothwell wrote: > > Hi Greg, > > > > On Mon, 27 Jul 2020 11:24:48 +0200 Greg KH wrote: > > > > > > On Mon, Jul 27, 2020 at 06:08:31PM +1000, Stephen Rothwell wrote: > > > > Hi

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

On Tue, Jul 28, 2020 at 05:33:31PM +1000, Stephen Rothwell wrote: > Hi Greg, > > On Mon, 27 Jul 2020 11:24:48 +0200 Greg KH wrote: > > > > On Mon, Jul 27, 2020 at 06:08:31PM +1000, Stephen Rothwell wrote: > > > Hi all, > > > > > > After merging the char-misc tree, today's linux-next build

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

Hi Greg, On Mon, 27 Jul 2020 11:24:48 +0200 Greg KH wrote: > > On Mon, Jul 27, 2020 at 06:08:31PM +1000, Stephen Rothwell wrote: > > Hi all, > > > > After merging the char-misc tree, today's linux-next build (x86_64 > > allmodconfig) failed like this: > > > > In file included from

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

On Mon, Jul 27, 2020 at 1:05 PM Greg KH wrote: > > On Mon, Jul 27, 2020 at 12:28:14PM +0300, Oded Gabbay wrote: > > On Mon, Jul 27, 2020 at 12:24 PM Greg KH wrote: > > > > > > On Mon, Jul 27, 2020 at 06:08:31PM +1000, Stephen Rothwell wrote: > > > > Hi all, > > > > > > > > After merging the

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

On Mon, Jul 27, 2020 at 12:28:14PM +0300, Oded Gabbay wrote: > On Mon, Jul 27, 2020 at 12:24 PM Greg KH wrote: > > > > On Mon, Jul 27, 2020 at 06:08:31PM +1000, Stephen Rothwell wrote: > > > Hi all, > > > > > > After merging the char-misc tree, today's linux-next build (x86_64 > > > allmodconfig)

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

On Mon, Jul 27, 2020 at 12:24 PM Greg KH wrote: > > On Mon, Jul 27, 2020 at 06:08:31PM +1000, Stephen Rothwell wrote: > > Hi all, > > > > After merging the char-misc tree, today's linux-next build (x86_64 > > allmodconfig) failed like this: > > > > In file included from

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

On Mon, Jul 27, 2020 at 06:08:31PM +1000, Stephen Rothwell wrote: > Hi all, > > After merging the char-misc tree, today's linux-next build (x86_64 > allmodconfig) failed like this: > > In file included from drivers/misc/habanalabs/goya/goya.c:8: > drivers/misc/habanalabs/goya/goyaP.h:12:10:

linux-next: build failure after merge of the char-misc tree

Hi all, After merging the char-misc tree, today's linux-next build (x86_64 allmodconfig) failed like this: In file included from drivers/misc/habanalabs/goya/goya.c:8: drivers/misc/habanalabs/goya/goyaP.h:12:10: fatal error: habanalabs.h: No such file or directory 12 | #include

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

On Mon, May 04, 2020 at 07:05:50AM +, Rajan Vaja wrote: > Hi Greg, A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing in e-mail? A: No. Q: Should I include quotations after my

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

On Mon, May 04, 2020 at 11:47:56AM +1000, Stephen Rothwell wrote: > Hi all, > > [Just adding cc] > > On Mon, 4 May 2020 11:46:25 +1000 Stephen Rothwell > wrote: > > > > Hi all, > > > > After merging the char-misc tree, Friday's linux-next build (arm64 > > allmodconfig) failed like this: > >

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

Hi all, [Just adding cc] On Mon, 4 May 2020 11:46:25 +1000 Stephen Rothwell wrote: > > Hi all, > > After merging the char-misc tree, Friday's linux-next build (arm64 > allmodconfig) failed like this: > > ERROR: modpost: "zynqmp_pm_fpga_get_status" [drivers/fpga/zynqmp-fpga.ko] > undefined!

linux-next: build failure after merge of the char-misc tree

Hi all, After merging the char-misc tree, Friday's linux-next build (arm64 allmodconfig) failed like this: ERROR: modpost: "zynqmp_pm_fpga_get_status" [drivers/fpga/zynqmp-fpga.ko] undefined! ERROR: modpost: "zynqmp_pm_fpga_load" [drivers/fpga/zynqmp-fpga.ko] undefined! Presumably caused by

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

On Fri, Jul 12, 2019 at 10:44:30AM +1000, Stephen Rothwell wrote: > Hi all, > > On Mon, 8 Jul 2019 19:23:45 +1000 Stephen Rothwell > wrote: > > > > After merging the char-misc tree, today's linux-next build (x86_64 > > allmodconfig) failed like this: > > > > drivers/misc/vmw_balloon.c: In

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

Hi all, On Mon, 8 Jul 2019 19:23:45 +1000 Stephen Rothwell wrote: > > After merging the char-misc tree, today's linux-next build (x86_64 > allmodconfig) failed like this: > > drivers/misc/vmw_balloon.c: In function 'vmballoon_mount': > drivers/misc/vmw_balloon.c:1736:14: error: 'simple_dname'

linux-next: build failure after merge of the char-misc tree

Hi all, After merging the char-misc tree, today's linux-next build (x86_64 allmodconfig) failed like this: drivers/misc/vmw_balloon.c: In function 'vmballoon_mount': drivers/misc/vmw_balloon.c:1736:14: error: 'simple_dname' undeclared (first use in this function); did you mean 'simple_rename'?

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

On Wed, Apr 12, 2017 at 03:18:59PM +1000, Stephen Rothwell wrote: > Hi all, > > After merging the char-misc tree, today's linux-next build (x86_64 > allmodconfig) failed like this: > > In file included from drivers/firmware/google/memconsole-x86-legacy.c:23:0: >

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

On Wed, Apr 12, 2017 at 03:18:59PM +1000, Stephen Rothwell wrote: > Hi all, > > After merging the char-misc tree, today's linux-next build (x86_64 > allmodconfig) failed like this: > > In file included from drivers/firmware/google/memconsole-x86-legacy.c:23:0: >

linux-next: build failure after merge of the char-misc tree

Hi all, After merging the char-misc tree, today's linux-next build (x86_64 allmodconfig) failed like this: In file included from drivers/firmware/google/memconsole-x86-legacy.c:23:0: arch/x86/include/uapi/asm/e820.h:66:23: error: 'E820_X_MAX' undeclared here (not in a function) struct

linux-next: build failure after merge of the char-misc tree

Hi all, After merging the char-misc tree, today's linux-next build (x86_64 allmodconfig) failed like this: In file included from drivers/firmware/google/memconsole-x86-legacy.c:23:0: arch/x86/include/uapi/asm/e820.h:66:23: error: 'E820_X_MAX' undeclared here (not in a function) struct

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

On Tue, Mar 21, 2017 at 11:06 AM, Cyril Bur wrote: > On Tue, 2017-03-21 at 11:18 +1100, Benjamin Herrenschmidt wrote: >> On Mon, 2017-03-20 at 13:23 +0100, Arnd Bergmann wrote: >> > On Mon, Mar 20, 2017 at 3:44 AM, Stephen Rothwell >> > wrote: >> > >

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

On Tue, Mar 21, 2017 at 11:06 AM, Cyril Bur wrote: > On Tue, 2017-03-21 at 11:18 +1100, Benjamin Herrenschmidt wrote: >> On Mon, 2017-03-20 at 13:23 +0100, Arnd Bergmann wrote: >> > On Mon, Mar 20, 2017 at 3:44 AM, Stephen Rothwell >> > wrote: >> > > Hi all, >> > > >> > > After merging the

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

On Tue, 2017-03-21 at 11:18 +1100, Benjamin Herrenschmidt wrote: > On Mon, 2017-03-20 at 13:23 +0100, Arnd Bergmann wrote: > > On Mon, Mar 20, 2017 at 3:44 AM, Stephen Rothwell > > wrote: > > > Hi all, > > > > > > After merging the char-misc tree, today's linux-next build

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

On Tue, 2017-03-21 at 11:18 +1100, Benjamin Herrenschmidt wrote: > On Mon, 2017-03-20 at 13:23 +0100, Arnd Bergmann wrote: > > On Mon, Mar 20, 2017 at 3:44 AM, Stephen Rothwell > > wrote: > > > Hi all, > > > > > > After merging the char-misc tree, today's linux-next build (x86_64 > > >

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

On Mon, 2017-03-20 at 13:23 +0100, Arnd Bergmann wrote: > On Mon, Mar 20, 2017 at 3:44 AM, Stephen Rothwell > wrote: > > Hi all, > > > > After merging the char-misc tree, today's linux-next build (x86_64 > > allmodconfig) failed like this: > > > >

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

On Mon, 2017-03-20 at 13:23 +0100, Arnd Bergmann wrote: > On Mon, Mar 20, 2017 at 3:44 AM, Stephen Rothwell > wrote: > > Hi all, > > > > After merging the char-misc tree, today's linux-next build (x86_64 > > allmodconfig) failed like this: > > > > drivers/misc/aspeed-lpc-ctrl.c: In function

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

On Mon, Mar 20, 2017 at 3:44 AM, Stephen Rothwell wrote: > Hi all, > > After merging the char-misc tree, today's linux-next build (x86_64 > allmodconfig) failed like this: > > drivers/misc/aspeed-lpc-ctrl.c: In function 'aspeed_lpc_ctrl_mmap': >

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

On Mon, Mar 20, 2017 at 3:44 AM, Stephen Rothwell wrote: > Hi all, > > After merging the char-misc tree, today's linux-next build (x86_64 > allmodconfig) failed like this: > > drivers/misc/aspeed-lpc-ctrl.c: In function 'aspeed_lpc_ctrl_mmap': > drivers/misc/aspeed-lpc-ctrl.c:51:9: error:

linux-next: build failure after merge of the char-misc tree

Hi all, After merging the char-misc tree, today's linux-next build (x86_64 allmodconfig) failed like this: drivers/misc/aspeed-lpc-ctrl.c: In function 'aspeed_lpc_ctrl_mmap': drivers/misc/aspeed-lpc-ctrl.c:51:9: error: implicit declaration of function 'pgprot_dmacoherent'

linux-next: build failure after merge of the char-misc tree

Hi all, After merging the char-misc tree, today's linux-next build (x86_64 allmodconfig) failed like this: drivers/misc/aspeed-lpc-ctrl.c: In function 'aspeed_lpc_ctrl_mmap': drivers/misc/aspeed-lpc-ctrl.c:51:9: error: implicit declaration of function 'pgprot_dmacoherent'

linux-next: build failure after merge of the char-misc tree

Hi all, After merging the char-misc tree, today's linux-next build (x86_64 allmodconfig) failed like this: drivers/hv/hv.c: In function 'read_hv_clock_tsc': drivers/hv/hv.c:154:4: error: implicit declaration of function 'rdtscll' [-Werror=implicit-function-declaration] rdtscll(cur_tsc);

linux-next: build failure after merge of the char-misc tree

Hi all, After merging the char-misc tree, today's linux-next build (x86_64 allmodconfig) failed like this: drivers/hv/hv.c: In function 'read_hv_clock_tsc': drivers/hv/hv.c:154:4: error: implicit declaration of function 'rdtscll' [-Werror=implicit-function-declaration] rdtscll(cur_tsc);

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

On Wed, May 27, 2015 at 07:08:06AM +, Winkler, Tomas wrote: > > > > Hi all, > > > > After merging the char-misc tree, today's linux-next build (x86_64 > > allmodconfig) > > failed like this: > > > Might be the case that this one was left out ? > https://lkml.org/lkml/2015/5/7/522 > uuid:

RE: linux-next: build failure after merge of the char-misc tree

> Hi all, > > After merging the char-misc tree, today's linux-next build (x86_64 > allmodconfig) > failed like this: > Might be the case that this one was left out ? https://lkml.org/lkml/2015/5/7/522 uuid: extract macros for assigning raw arrays Tomas -- To unsubscribe from this list:

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

On Wed, May 27, 2015 at 07:08:06AM +, Winkler, Tomas wrote: Hi all, After merging the char-misc tree, today's linux-next build (x86_64 allmodconfig) failed like this: Might be the case that this one was left out ? https://lkml.org/lkml/2015/5/7/522 uuid: extract macros

RE: linux-next: build failure after merge of the char-misc tree

Hi all, After merging the char-misc tree, today's linux-next build (x86_64 allmodconfig) failed like this: Might be the case that this one was left out ? https://lkml.org/lkml/2015/5/7/522 uuid: extract macros for assigning raw arrays Tomas -- To unsubscribe from this list: send the

linux-next: build failure after merge of the char-misc tree

Hi all, After merging the char-misc tree, today's linux-next build (x86_64 allmodconfig) failed like this: drivers/nfc/microread/mei.c:70:2: error: implicit declaration of function '__UUID_LE' [-Werror=implicit-function-declaration] { MICROREAD_DRIVER_NAME, MEI_NFC_UUID}, ^

linux-next: build failure after merge of the char-misc tree

Hi all, After merging the char-misc tree, today's linux-next build (x86_64 allmodconfig) failed like this: drivers/nfc/microread/mei.c:70:2: error: implicit declaration of function '__UUID_LE' [-Werror=implicit-function-declaration] { MICROREAD_DRIVER_NAME, MEI_NFC_UUID}, ^

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

Hi Greg, On Wed, 26 Feb 2014 19:37:16 -0800 Greg KH wrote: > > On Wed, Feb 26, 2014 at 05:47:21PM +1100, Stephen Rothwell wrote: > > > > On Fri, 21 Feb 2014 16:47:11 +1100 Stephen Rothwell > > wrote: > > > > > > After merging the char-misc tree, today's linux-next build (x86_64 > > >

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

On Wed, Feb 26, 2014 at 05:47:21PM +1100, Stephen Rothwell wrote: > Hi Greg, > > On Fri, 21 Feb 2014 16:47:11 +1100 Stephen Rothwell > wrote: > > > > After merging the char-misc tree, today's linux-next build (x86_64 > > allmodconfig) failed like this: > > > > In file included from

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

On Wed, Feb 26, 2014 at 05:47:21PM +1100, Stephen Rothwell wrote: Hi Greg, On Fri, 21 Feb 2014 16:47:11 +1100 Stephen Rothwell s...@canb.auug.org.au wrote: After merging the char-misc tree, today's linux-next build (x86_64 allmodconfig) failed like this: In file included from

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

Hi Greg, On Wed, 26 Feb 2014 19:37:16 -0800 Greg KH g...@kroah.com wrote: On Wed, Feb 26, 2014 at 05:47:21PM +1100, Stephen Rothwell wrote: On Fri, 21 Feb 2014 16:47:11 +1100 Stephen Rothwell s...@canb.auug.org.au wrote: After merging the char-misc tree, today's linux-next build

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

Hi Greg, On Fri, 21 Feb 2014 16:47:11 +1100 Stephen Rothwell wrote: > > After merging the char-misc tree, today's linux-next build (x86_64 > allmodconfig) failed like this: > > In file included from drivers/misc/mei/hw-txe.c:25:0: > drivers/misc/mei/hw-txe.h:63:1: error: unknown type name

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

Hi Greg, On Fri, 21 Feb 2014 16:47:11 +1100 Stephen Rothwell s...@canb.auug.org.au wrote: After merging the char-misc tree, today's linux-next build (x86_64 allmodconfig) failed like this: In file included from drivers/misc/mei/hw-txe.c:25:0: drivers/misc/mei/hw-txe.h:63:1: error: unknown

linux-next: build failure after merge of the char-misc tree

Hi all, After merging the char-misc tree, today's linux-next build (x86_64 allmodconfig) failed like this: In file included from drivers/misc/mei/hw-txe.c:25:0: drivers/misc/mei/hw-txe.h:63:1: error: unknown type name 'irqreturn_t' irqreturn_t mei_txe_irq_quick_handler(int irq, void *dev_id);

linux-next: build failure after merge of the char-misc tree

Hi all, After merging the char-misc tree, today's linux-next build (x86_64 allmodconfig) failed like this: In file included from drivers/misc/mei/hw-txe.c:25:0: drivers/misc/mei/hw-txe.h:63:1: error: unknown type name 'irqreturn_t' irqreturn_t mei_txe_irq_quick_handler(int irq, void *dev_id);

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

On Fri, Sep 27, 2013 at 05:10:29PM +1000, Stephen Rothwell wrote: > Hi all, > > After merging the char-misc tree, today's linux-next build (x86_64 > allmodconfig) failed like this: > > drivers/misc/mic/host/mic_main.c: In function 'mic_probe': > drivers/misc/mic/host/mic_main.c:320:3: error: too

linux-next: build failure after merge of the char-misc tree

Hi all, After merging the char-misc tree, today's linux-next build (x86_64 allmodconfig) failed like this: drivers/misc/mic/host/mic_main.c: In function 'mic_probe': drivers/misc/mic/host/mic_main.c:320:3: error: too many arguments to function 'sysfs_get_dirent' NULL, "state"); ^ In file

linux-next: build failure after merge of the char-misc tree

Hi all, After merging the char-misc tree, today's linux-next build (x86_64 allmodconfig) failed like this: drivers/misc/mic/host/mic_main.c: In function 'mic_probe': drivers/misc/mic/host/mic_main.c:320:3: error: too many arguments to function 'sysfs_get_dirent' NULL, state); ^ In file

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

On Fri, Sep 27, 2013 at 05:10:29PM +1000, Stephen Rothwell wrote: Hi all, After merging the char-misc tree, today's linux-next build (x86_64 allmodconfig) failed like this: drivers/misc/mic/host/mic_main.c: In function 'mic_probe': drivers/misc/mic/host/mic_main.c:320:3: error: too many

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

Am Tue, 2 Apr 2013 17:29:50 +1100 schrieb Stephen Rothwell : > Hi all, > > After merging the char-misc tree, today's linux-next build (x86_64 > allmodconfig) failed like this: > > drivers/misc/cs5535-mfgpt.c:30:3: warning: missing terminating " > character [enabled by default]

linux-next: build failure after merge of the char-misc tree

Hi all, After merging the char-misc tree, today's linux-next build (x86_64 allmodconfig) failed like this: drivers/misc/cs5535-mfgpt.c:30:3: warning: missing terminating " character [enabled by default] drivers/misc/cs5535-mfgpt.c:31:31: warning: missing terminating " character [enabled by

linux-next: build failure after merge of the char-misc tree

Hi all, After merging the char-misc tree, today's linux-next build (x86_64 allmodconfig) failed like this: drivers/misc/cs5535-mfgpt.c:30:3: warning: missing terminating character [enabled by default] drivers/misc/cs5535-mfgpt.c:31:31: warning: missing terminating character [enabled by

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

Am Tue, 2 Apr 2013 17:29:50 +1100 schrieb Stephen Rothwell s...@canb.auug.org.au: Hi all, After merging the char-misc tree, today's linux-next build (x86_64 allmodconfig) failed like this: drivers/misc/cs5535-mfgpt.c:30:3: warning: missing terminating character [enabled by default]

linux-next: build failure after merge of the char-misc tree

Hi all, After merging the char-misc tree, today's linux-next build (x86_64_allmodconfig) failed like this: drivers/input/keyboard/pmic8xxx-keypad.c:24:35: fatal error: linux/mfd/pm8xxx/gpio.h: No such file or directory Caused by commit e44b0ceee4cc ("add single-wire serial bus interface (SSBI)

linux-next: build failure after merge of the char-misc tree

Hi all, After merging the char-misc tree, today's linux-next build (x86_64_allmodconfig) failed like this: drivers/input/keyboard/pmic8xxx-keypad.c:24:35: fatal error: linux/mfd/pm8xxx/gpio.h: No such file or directory Caused by commit e44b0ceee4cc (add single-wire serial bus interface (SSBI)

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

On Mon, Mar 18, 2013 at 01:56:14PM +1100, Stephen Rothwell wrote: > Hi all, > > After merging the char-misc tree, today's linux-next build (x86_64 > allmodconfig) failed like this: > > drivers/net/can/softing/softing_cs.c:343:1: error: expected identifier or '(' > before '&' token >

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

On Mon, Mar 18, 2013 at 01:56:14PM +1100, Stephen Rothwell wrote: Hi all, After merging the char-misc tree, today's linux-next build (x86_64 allmodconfig) failed like this: drivers/net/can/softing/softing_cs.c:343:1: error: expected identifier or '(' before '' token

linux-next: build failure after merge of the char-misc tree

Hi all, After merging the char-misc tree, today's linux-next build (x86_64 allmodconfig) failed like this: drivers/net/can/softing/softing_cs.c:343:1: error: expected identifier or '(' before '&' token drivers/net/can/softing/softing_cs.c: In function '__inittest':

linux-next: build failure after merge of the char-misc tree

Hi all, After merging the char-misc tree, today's linux-next build (x86_64 allmodconfig) failed like this: drivers/net/can/softing/softing_cs.c:343:1: error: expected identifier or '(' before '' token drivers/net/can/softing/softing_cs.c: In function '__inittest':