From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Daniel Lezcano <daniel.lezcano@linaro•org>
Cc: Linux Next Mailing List <linux-next@vger•kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger•kernel.org>,
Alexandre Belloni <alexandre.belloni@bootlin•com>
Subject: linux-next: build failure after merge of the clockevents tree
Date: Mon, 3 Jun 2019 12:13:50 +1000 [thread overview]
Message-ID: <20190603121350.653cacce@canb.auug.org.au> (raw)
[-- 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 --]
next reply other threads:[~2019-06-03 2:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-03 2:13 Stephen Rothwell [this message]
2019-06-04 5:56 ` linux-next: build failure after merge of the clockevents tree 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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20190603121350.653cacce@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=alexandre.belloni@bootlin$(echo .)com \
--cc=daniel.lezcano@linaro$(echo .)org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox