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

2019-10-03 Thread Stephen Rothwell
Hi all, After merging the rtc tree, today's linux-next build (powerpc allyesconfig) failed like this: drivers/rtc/rtc-mc146818-lib.c: In function 'mc146818_set_time': drivers/rtc/rtc-mc146818-lib.c:176:6: error: 'boot_cpu_data' undeclared (first use in this function); did you mean

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

2019-02-10 Thread Stephen Rothwell
Hi all, After merging the rtc tree, today's linux-next build (x86_64 allmodconfig) failed like this: ERROR: "rtc_nvmem_unregister" [drivers/rtc/rtc-meson.ko] undefined! Caused by commit 21358403bb29 ("rtc: support for the Amlogic Meson RTC") I have reverted that commit for today. --

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

2019-02-07 Thread Stephen Rothwell
Hi Alexandre, After merging the rtc tree, today's linux-next build (x86_64 allmodconfig) failed like this: drivers/rtc/rtc-x1205: struct of_device_id is 200 bytes. The last of 1 is: 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00

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

2017-05-31 Thread Alexandre Belloni
Hi, On 31/05/2017 at 07:45:07 +0200, Heiner Kallweit wrote: > Am 31.05.2017 um 06:33 schrieb Stephen Rothwell: > > Hi Alexandre, > > > > After merging the rtc tree, today's linux-next build (arm > > multi_v7_defconfig) failed like this: > > > > drivers/rtc/rtc-ds1307.c: In function

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

2017-05-31 Thread Alexandre Belloni
Hi, On 31/05/2017 at 07:45:07 +0200, Heiner Kallweit wrote: > Am 31.05.2017 um 06:33 schrieb Stephen Rothwell: > > Hi Alexandre, > > > > After merging the rtc tree, today's linux-next build (arm > > multi_v7_defconfig) failed like this: > > > > drivers/rtc/rtc-ds1307.c: In function

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

2017-05-30 Thread Heiner Kallweit
Am 31.05.2017 um 06:33 schrieb Stephen Rothwell: > Hi Alexandre, > > After merging the rtc tree, today's linux-next build (arm > multi_v7_defconfig) failed like this: > > drivers/rtc/rtc-ds1307.c: In function 'ds1307_probe': > drivers/rtc/rtc-ds1307.c:1410:29: error: 'struct ds1307' has no

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

2017-05-30 Thread Heiner Kallweit
Am 31.05.2017 um 06:33 schrieb Stephen Rothwell: > Hi Alexandre, > > After merging the rtc tree, today's linux-next build (arm > multi_v7_defconfig) failed like this: > > drivers/rtc/rtc-ds1307.c: In function 'ds1307_probe': > drivers/rtc/rtc-ds1307.c:1410:29: error: 'struct ds1307' has no

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

2017-05-30 Thread Stephen Rothwell
Hi Alexandre, After merging the rtc tree, today's linux-next build (arm multi_v7_defconfig) failed like this: drivers/rtc/rtc-ds1307.c: In function 'ds1307_probe': drivers/rtc/rtc-ds1307.c:1410:29: error: 'struct ds1307' has no member named 'client' if (chip->alarm && (ds1307->client->irq >

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

2017-05-30 Thread Stephen Rothwell
Hi Alexandre, After merging the rtc tree, today's linux-next build (arm multi_v7_defconfig) failed like this: drivers/rtc/rtc-ds1307.c: In function 'ds1307_probe': drivers/rtc/rtc-ds1307.c:1410:29: error: 'struct ds1307' has no member named 'client' if (chip->alarm && (ds1307->client->irq >

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

2017-04-14 Thread Stephen Rothwell
Hi Alexandre, On Fri, 14 Apr 2017 12:09:47 +0200 Alexandre Belloni wrote: > > On 11/04/2017 at 17:52:20 +1000, Stephen Rothwell wrote: > > But it is a fix for a build failure caused by a commit in your tree ... > > so you should probably get an ack from the

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

2017-04-14 Thread Stephen Rothwell
Hi Alexandre, On Fri, 14 Apr 2017 12:09:47 +0200 Alexandre Belloni wrote: > > On 11/04/2017 at 17:52:20 +1000, Stephen Rothwell wrote: > > But it is a fix for a build failure caused by a commit in your tree ... > > so you should probably get an ack from the x86 maintainers and add it > > to

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

2017-04-14 Thread Alexandre Belloni
On 11/04/2017 at 17:52:20 +1000, Stephen Rothwell wrote: > But it is a fix for a build failure caused by a commit in your tree ... > so you should probably get an ack from the x86 maintainers and add it > to your tree. Or do some other fix in your tree. > It is now in my tree. -- Alexandre

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

2017-04-14 Thread Alexandre Belloni
On 11/04/2017 at 17:52:20 +1000, Stephen Rothwell wrote: > But it is a fix for a build failure caused by a commit in your tree ... > so you should probably get an ack from the x86 maintainers and add it > to your tree. Or do some other fix in your tree. > It is now in my tree. -- Alexandre

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

2017-04-11 Thread Stephen Rothwell
Hi Alexandre, On Tue, 11 Apr 2017 07:55:09 +0200 Alexandre Belloni wrote: > > On 11/04/2017 at 10:22:38 +1000, Stephen Rothwell wrote: > > > > On Mon, 10 Apr 2017 09:45:45 +0200 Hans de Goede > > wrote: > > > > > > On 10-04-17

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

2017-04-11 Thread Stephen Rothwell
Hi Alexandre, On Tue, 11 Apr 2017 07:55:09 +0200 Alexandre Belloni wrote: > > On 11/04/2017 at 10:22:38 +1000, Stephen Rothwell wrote: > > > > On Mon, 10 Apr 2017 09:45:45 +0200 Hans de Goede > > wrote: > > > > > > On 10-04-17 08:04, Stephen Rothwell wrote: > > > > > > > > After merging

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

2017-04-10 Thread Alexandre Belloni
On 11/04/2017 at 10:22:38 +1000, Stephen Rothwell wrote: > Hi Hans, > > On Mon, 10 Apr 2017 09:45:45 +0200 Hans de Goede wrote: > > > > On 10-04-17 08:04, Stephen Rothwell wrote: > > > > > > After merging the rtc tree, today's linux-next build (x86_64 allmodconfig) > > >

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

2017-04-10 Thread Alexandre Belloni
On 11/04/2017 at 10:22:38 +1000, Stephen Rothwell wrote: > Hi Hans, > > On Mon, 10 Apr 2017 09:45:45 +0200 Hans de Goede wrote: > > > > On 10-04-17 08:04, Stephen Rothwell wrote: > > > > > > After merging the rtc tree, today's linux-next build (x86_64 allmodconfig) > > > failed like this: > > >

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

2017-04-10 Thread Stephen Rothwell
Hi Hans, On Mon, 10 Apr 2017 09:45:45 +0200 Hans de Goede wrote: > > On 10-04-17 08:04, Stephen Rothwell wrote: > > > > After merging the rtc tree, today's linux-next build (x86_64 allmodconfig) > > failed like this: > > > > ERROR: "legacy_pic" [drivers/rtc/rtc-cmos.ko]

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

2017-04-10 Thread Stephen Rothwell
Hi Hans, On Mon, 10 Apr 2017 09:45:45 +0200 Hans de Goede wrote: > > On 10-04-17 08:04, Stephen Rothwell wrote: > > > > After merging the rtc tree, today's linux-next build (x86_64 allmodconfig) > > failed like this: > > > > ERROR: "legacy_pic" [drivers/rtc/rtc-cmos.ko] undefined! > > > > Caused

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

2017-04-10 Thread Hans de Goede
Hi, On 10-04-17 08:04, Stephen Rothwell wrote: Hi Alexandre, After merging the rtc tree, today's linux-next build (x86_64 allmodconfig) failed like this: ERROR: "legacy_pic" [drivers/rtc/rtc-cmos.ko] undefined! Caused by commit d3e3a65c6a96 ("rtc: cmos: Do not assume irq 8 for rtc when

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

2017-04-10 Thread Hans de Goede
Hi, On 10-04-17 08:04, Stephen Rothwell wrote: Hi Alexandre, After merging the rtc tree, today's linux-next build (x86_64 allmodconfig) failed like this: ERROR: "legacy_pic" [drivers/rtc/rtc-cmos.ko] undefined! Caused by commit d3e3a65c6a96 ("rtc: cmos: Do not assume irq 8 for rtc when

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

2017-04-10 Thread Stephen Rothwell
Hi Alexandre, After merging the rtc tree, today's linux-next build (x86_64 allmodconfig) failed like this: ERROR: "legacy_pic" [drivers/rtc/rtc-cmos.ko] undefined! Caused by commit d3e3a65c6a96 ("rtc: cmos: Do not assume irq 8 for rtc when there are no legacy irqs") "legacy_pic" is not

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

2017-04-10 Thread Stephen Rothwell
Hi Alexandre, After merging the rtc tree, today's linux-next build (x86_64 allmodconfig) failed like this: ERROR: "legacy_pic" [drivers/rtc/rtc-cmos.ko] undefined! Caused by commit d3e3a65c6a96 ("rtc: cmos: Do not assume irq 8 for rtc when there are no legacy irqs") "legacy_pic" is not

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

2016-11-08 Thread Alexandre Belloni
Hi, On 08/11/2016 at 17:41:52 +1100, Stephen Rothwell wrote : > Hi Alexandre, > > After merging the rtc tree, today's linux-next build (x86_64 allmodconfig) > failed like this: > > > Caused by commit > > f9eb69d1ae2f ("rtc: jz4740: Add support for acting as the system power > controller")

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

2016-11-08 Thread Alexandre Belloni
Hi, On 08/11/2016 at 17:41:52 +1100, Stephen Rothwell wrote : > Hi Alexandre, > > After merging the rtc tree, today's linux-next build (x86_64 allmodconfig) > failed like this: > > > Caused by commit > > f9eb69d1ae2f ("rtc: jz4740: Add support for acting as the system power > controller")

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

2016-11-07 Thread Stephen Rothwell
Hi Alexandre, After merging the rtc tree, today's linux-next build (x86_64 allmodconfig) failed like this: Caused by commit f9eb69d1ae2f ("rtc: jz4740: Add support for acting as the system power controller") I have used the rtc tree from next-20161028 for today. -- Cheers, Stephen

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

2016-11-07 Thread Stephen Rothwell
Hi Alexandre, After merging the rtc tree, today's linux-next build (x86_64 allmodconfig) failed like this: Caused by commit f9eb69d1ae2f ("rtc: jz4740: Add support for acting as the system power controller") I have used the rtc tree from next-20161028 for today. -- Cheers, Stephen

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

2015-12-22 Thread Alexandre Belloni
Hi Sasha, On 18/12/2015 at 17:43:41 +0100, Alexandre Belloni wrote : > > > Sasha, I think I prefer having 32 bit platforms fail on the 21st of > > > January 11761191 rather than adding more uses of do_div in the function. > > > I'll have a look at the performance impact on 32 bit platforms. > >

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

2015-12-22 Thread Alexandre Belloni
Hi Sasha, On 18/12/2015 at 17:43:41 +0100, Alexandre Belloni wrote : > > > Sasha, I think I prefer having 32 bit platforms fail on the 21st of > > > January 11761191 rather than adding more uses of do_div in the function. > > > I'll have a look at the performance impact on 32 bit platforms. > >

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

2015-12-18 Thread Alexandre Belloni
On 18/12/2015 at 10:30:22 -0500, Sasha Levin wrote : > On 12/17/2015 06:21 AM, Alexandre Belloni wrote: > > On 17/12/2015 at 16:03:44 +1100, Stephen Rothwell wrote : > >> > Hi Alexandre, > >> > > >> > After merging the rtc tree, today's linux-next build (arm > >> > multi_v7_defconfig) failed like

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

2015-12-18 Thread Sasha Levin
On 12/17/2015 06:21 AM, Alexandre Belloni wrote: > On 17/12/2015 at 16:03:44 +1100, Stephen Rothwell wrote : >> > Hi Alexandre, >> > >> > After merging the rtc tree, today's linux-next build (arm >> > multi_v7_defconfig) failed like this: >> > >> > drivers/built-in.o: In function

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

2015-12-18 Thread Sasha Levin
On 12/17/2015 06:21 AM, Alexandre Belloni wrote: > On 17/12/2015 at 16:03:44 +1100, Stephen Rothwell wrote : >> > Hi Alexandre, >> > >> > After merging the rtc tree, today's linux-next build (arm >> > multi_v7_defconfig) failed like this: >> > >> > drivers/built-in.o: In function

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

2015-12-18 Thread Alexandre Belloni
On 18/12/2015 at 10:30:22 -0500, Sasha Levin wrote : > On 12/17/2015 06:21 AM, Alexandre Belloni wrote: > > On 17/12/2015 at 16:03:44 +1100, Stephen Rothwell wrote : > >> > Hi Alexandre, > >> > > >> > After merging the rtc tree, today's linux-next build (arm > >> > multi_v7_defconfig) failed like

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

2015-12-17 Thread Alexandre Belloni
On 17/12/2015 at 16:03:44 +1100, Stephen Rothwell wrote : > Hi Alexandre, > > After merging the rtc tree, today's linux-next build (arm > multi_v7_defconfig) failed like this: > > drivers/built-in.o: In function `rtc_time64_to_tm': > sunxi_sid.c:(.text+0x366e54): undefined reference to

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

2015-12-17 Thread Alexandre Belloni
On 17/12/2015 at 16:03:44 +1100, Stephen Rothwell wrote : > Hi Alexandre, > > After merging the rtc tree, today's linux-next build (arm > multi_v7_defconfig) failed like this: > > drivers/built-in.o: In function `rtc_time64_to_tm': > sunxi_sid.c:(.text+0x366e54): undefined reference to

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

2015-12-16 Thread Stephen Rothwell
Hi Alexandre, After merging the rtc tree, today's linux-next build (arm multi_v7_defconfig) failed like this: drivers/built-in.o: In function `rtc_time64_to_tm': sunxi_sid.c:(.text+0x366e54): undefined reference to `__aeabi_ldivmod' sunxi_sid.c:(.text+0x366e6c): undefined reference to

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

2015-12-16 Thread Stephen Rothwell
Hi Alexandre, After merging the rtc tree, today's linux-next build (arm multi_v7_defconfig) failed like this: drivers/built-in.o: In function `rtc_time64_to_tm': sunxi_sid.c:(.text+0x366e54): undefined reference to `__aeabi_ldivmod' sunxi_sid.c:(.text+0x366e6c): undefined reference to