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 'bootmem_data'
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.
--
Cheers
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 0x0
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 'ds1307_probe
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 member
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 > 0
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 your
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 Be
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 t
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:
> > >
>
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
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 the
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 expo
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")
>
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 Rothwel
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.
> >
>
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
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 `rtc_time64_to_t
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 `__aeabi_l
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 `__aeabi_ld
20 matches
Mail list logo