* linux-next: build failure after merge of the clockevents tree
@ 2019-06-03 2:13 Stephen Rothwell
2019-06-04 5:56 ` Daniel Lezcano
0 siblings, 1 reply; 6+ messages in thread
From: Stephen Rothwell @ 2019-06-03 2:13 UTC (permalink / raw)
To: Daniel Lezcano
Cc: Linux Next Mailing List, Linux Kernel Mailing List, Alexandre Belloni
[-- Attachment #1: Type: text/plain, Size: 1479 bytes --]
Hi Daniel,
After merging the clockevents tree, today's linux-next build (x86_64
allmodconfig) failed like this:
drivers/clocksource/timer-atmel-tcb.c: In function 'tcb_clksrc_init':
drivers/clocksource/timer-atmel-tcb.c:448:17: error: invalid use of undefined type 'struct delay_timer'
tc_delay_timer.read_current_timer = tc_delay_timer_read32;
^
drivers/clocksource/timer-atmel-tcb.c:461:17: error: invalid use of undefined type 'struct delay_timer'
tc_delay_timer.read_current_timer = tc_delay_timer_read;
^
drivers/clocksource/timer-atmel-tcb.c:476:16: error: invalid use of undefined type 'struct delay_timer'
tc_delay_timer.freq = divided_rate;
^
drivers/clocksource/timer-atmel-tcb.c:477:2: error: implicit declaration of function 'register_current_timer_delay'; did you mean 'read_current_timer'? [-Werror=implicit-function-declaration]
register_current_timer_delay(&tc_delay_timer);
^~~~~~~~~~~~~~~~~~~~~~~~~~~~
read_current_timer
drivers/clocksource/timer-atmel-tcb.c: At top level:
drivers/clocksource/timer-atmel-tcb.c:129:27: error: storage size of 'tc_delay_timer' isn't known
static struct delay_timer tc_delay_timer;
^~~~~~~~~~~~~~
cc1: some warnings being treated as errors
Caused by commit
dd40f5020581 ("clocksource/drivers/tcb_clksrc: Register delay timer")
I have reverted that commit for today.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: linux-next: build failure after merge of the clockevents tree
2019-06-03 2:13 linux-next: build failure after merge of the clockevents tree Stephen Rothwell
@ 2019-06-04 5:56 ` Daniel Lezcano
2019-06-04 6:02 ` Stephen Rothwell
0 siblings, 1 reply; 6+ messages in thread
From: Daniel Lezcano @ 2019-06-04 5:56 UTC (permalink / raw)
To: Stephen Rothwell
Cc: Linux Next Mailing List, Linux Kernel Mailing List, Alexandre Belloni
[-- Attachment #1.1: Type: text/plain, Size: 1880 bytes --]
Hi Stephen,
I dropped the patch from my tree.
Thanks
-- Daniel
On 03/06/2019 04:13, Stephen Rothwell wrote:
> Hi Daniel,
>
> After merging the clockevents tree, today's linux-next build (x86_64
> allmodconfig) failed like this:
>
> drivers/clocksource/timer-atmel-tcb.c: In function 'tcb_clksrc_init':
> drivers/clocksource/timer-atmel-tcb.c:448:17: error: invalid use of undefined type 'struct delay_timer'
> tc_delay_timer.read_current_timer = tc_delay_timer_read32;
> ^
> drivers/clocksource/timer-atmel-tcb.c:461:17: error: invalid use of undefined type 'struct delay_timer'
> tc_delay_timer.read_current_timer = tc_delay_timer_read;
> ^
> drivers/clocksource/timer-atmel-tcb.c:476:16: error: invalid use of undefined type 'struct delay_timer'
> tc_delay_timer.freq = divided_rate;
> ^
> drivers/clocksource/timer-atmel-tcb.c:477:2: error: implicit declaration of function 'register_current_timer_delay'; did you mean 'read_current_timer'? [-Werror=implicit-function-declaration]
> register_current_timer_delay(&tc_delay_timer);
> ^~~~~~~~~~~~~~~~~~~~~~~~~~~~
> read_current_timer
> drivers/clocksource/timer-atmel-tcb.c: At top level:
> drivers/clocksource/timer-atmel-tcb.c:129:27: error: storage size of 'tc_delay_timer' isn't known
> static struct delay_timer tc_delay_timer;
> ^~~~~~~~~~~~~~
> cc1: some warnings being treated as errors
>
> Caused by commit
>
> dd40f5020581 ("clocksource/drivers/tcb_clksrc: Register delay timer")
>
> I have reverted that commit for today.
>
--
<http://www.linaro.org/> Linaro.org │ Open source software for ARM SoCs
Follow Linaro: <http://www.facebook.com/pages/Linaro> Facebook |
<http://twitter.com/#!/linaroorg> Twitter |
<http://www.linaro.org/linaro-blog/> Blog
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: linux-next: build failure after merge of the clockevents tree
2019-06-04 5:56 ` Daniel Lezcano
@ 2019-06-04 6:02 ` Stephen Rothwell
0 siblings, 0 replies; 6+ messages in thread
From: Stephen Rothwell @ 2019-06-04 6:02 UTC (permalink / raw)
To: Daniel Lezcano
Cc: Linux Next Mailing List, Linux Kernel Mailing List, Alexandre Belloni
[-- Attachment #1: Type: text/plain, Size: 182 bytes --]
Hi Daniel,
On Tue, 4 Jun 2019 07:56:45 +0200 Daniel Lezcano <daniel.lezcano@linaro.org> wrote:
>
> I dropped the patch from my tree.
Thanks.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
^ permalink raw reply [flat|nested] 6+ messages in thread
* linux-next: build failure after merge of the clockevents tree
@ 2016-06-07 3:12 Stephen Rothwell
0 siblings, 0 replies; 6+ messages in thread
From: Stephen Rothwell @ 2016-06-07 3:12 UTC (permalink / raw)
To: Daniel Lezcano; +Cc: linux-next, linux-kernel
Hi Daniel,
After merging the clockevents tree, today's linux-next build (arm
multi_v7_defconfig) failed like this:
drivers/clocksource/versatile.c: In function 'versatile_sched_clock_init':
drivers/clocksource/versatile.c:33:11: error: 'EXNIO' undeclared (first use in this function)
return -EXNIO;
^
drivers/clocksource/versatile.c:33:11: note: each undeclared identifier is reported only once for each function it appears in
drivers/clocksource/versatile.c:33:10: warning: 'return' with a value, in function returning void
return -EXNIO;
^
drivers/clocksource/versatile.c:39:9: warning: 'return' with a value, in function returning void
return 0;
^
In file included from include/linux/clocksource.h:18:0,
from drivers/clocksource/versatile.c:14:
drivers/clocksource/versatile.c: At top level:
include/linux/of.h:1002:20: warning: comparison of distinct pointer types lacks a cast
.data = (fn == (fn_type)NULL) ? fn : fn }
^
include/linux/of.h:1018:3: note: in expansion of macro '_OF_DECLARE'
_OF_DECLARE(table, name, compat, fn, of_init_fn_1_ret)
^
include/linux/clocksource.h:247:2: note: in expansion of macro 'OF_DECLARE_1_RET'
OF_DECLARE_1_RET(clksrc_ret, name, compat, fn)
^
drivers/clocksource/versatile.c:41:1: note: in expansion of macro 'CLOCKSOURCE_OF_DECLARE'
CLOCKSOURCE_OF_DECLARE(vexpress, "arm,vexpress-sysreg",
^
include/linux/of.h:1002:20: warning: comparison of distinct pointer types lacks a cast
.data = (fn == (fn_type)NULL) ? fn : fn }
^
include/linux/of.h:1018:3: note: in expansion of macro '_OF_DECLARE'
_OF_DECLARE(table, name, compat, fn, of_init_fn_1_ret)
^
include/linux/clocksource.h:247:2: note: in expansion of macro 'OF_DECLARE_1_RET'
OF_DECLARE_1_RET(clksrc_ret, name, compat, fn)
^
drivers/clocksource/versatile.c:43:1: note: in expansion of macro 'CLOCKSOURCE_OF_DECLARE'
CLOCKSOURCE_OF_DECLARE(versatile, "arm,versatile-sysreg",
^
Caused by commit
339ecd4051c3 ("clocksource/drivers/versatile: Convert init function to return error")
I have used the clockevents tree from next-20160606 for today.
--
Cheers,
Stephen Rothwell
^ permalink raw reply [flat|nested] 6+ messages in thread
* linux-next: build failure after merge of the clockevents tree
@ 2015-12-17 2:55 Stephen Rothwell
0 siblings, 0 replies; 6+ messages in thread
From: Stephen Rothwell @ 2015-12-17 2:55 UTC (permalink / raw)
To: Daniel Lezcano; +Cc: linux-next, linux-kernel, Yoshinori Sato
Hi Daniel,
After merging the clockevents tree, today's linux-next build (x86_64
allmodconfig) failed like this:
drivers/clocksource/h8300_timer16.c: In function 'timer16_interrupt':
drivers/clocksource/h8300_timer16.c:64:2: error: implicit declaration of function 'ctrl_bclr' [-Werror=implicit-function-declaration]
ctrl_bclr(p->ovf, p->mapcommon + TISRC);
^
Caused by commit
1ddca16cc5b3 ("clocksource/drivers/h8300: Use ioread / iowrite")
ctrl_bclr is only defined for the h8300 arch ...
I have used the clocksource tree from next-20151216 for today.
--
Cheers,
Stephen Rothwell sfr@canb.auug.org.au
^ permalink raw reply [flat|nested] 6+ messages in thread
* linux-next: build failure after merge of the clockevents tree
@ 2014-05-26 6:07 Stephen Rothwell
0 siblings, 0 replies; 6+ messages in thread
From: Stephen Rothwell @ 2014-05-26 6:07 UTC (permalink / raw)
To: Daniel Lezcano; +Cc: linux-next, linux-kernel, Maxime Ripard
[-- Attachment #1: Type: text/plain, Size: 567 bytes --]
Hi Daniel,
After merging the clockevents tree, today's linux-next build (arm
multi_v7_defconfig) failed like this:
drivers/clocksource/timer-sun5i.c: In function 'sun5i_timer_init':
drivers/clocksource/timer-sun5i.c:167:2: error: implicit declaration of function 'of_reset_control_get' [-Werror=implicit-function-declaration]
Caused by commit e50a00be5c42 ("clocksource: sun5i: Add support for
reset controller").
I have used the clockevents tree from next-20140523 for today.
--
Cheers,
Stephen Rothwell sfr@canb.auug.org.au
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~2019-06-04 6:02 UTC | newest]
Thread overview: 6+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2019-06-03 2:13 linux-next: build failure after merge of the clockevents tree Stephen Rothwell
2019-06-04 5:56 ` Daniel Lezcano
2019-06-04 6:02 ` Stephen Rothwell
-- strict thread matches above, loose matches on Subject: below --
2016-06-07 3:12 Stephen Rothwell
2015-12-17 2:55 Stephen Rothwell
2014-05-26 6:07 Stephen Rothwell
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).