From: Linus Walleij <linus.walleij@linaro.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Olof Johansson <olof@lixom.net>, Arnd Bergmann <arnd@arndb.de>,
ARM <linux-arm-kernel@lists.infradead.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: linux-next: build warning after merge of the arm-soc tree
Date: Fri, 3 May 2019 07:49:33 +0100 [thread overview]
Message-ID: <CACRpkdYBuBf7jA2nUitiZWRriXVTPWCyB93q2CzmP4tbVZXqHA@mail.gmail.com> (raw)
In-Reply-To: <20190430092839.767e5bf8@canb.auug.org.au>
On Tue, Apr 30, 2019 at 12:28 AM Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> After merging the arm-soc tree, today's linux-next build
> (x86_64 allmodconfig) produced this warning:
>
> drivers/clocksource/timer-ixp4xx.c:78:20: warning: 'ixp4xx_read_sched_clock' defined but not used [-Wunused-function]
> static u64 notrace ixp4xx_read_sched_clock(void)
> ^~~~~~~~~~~~~~~~~~~~~~~
This is kind of normal for timer drivers, as the sched_clock() call is #ifdef:ed
for CONFIG_ARM, it is not uniformly available on all archs. This appears
as a side effect of COMPILE_TEST which I think is fair to produce
things like this.
Yours,
Linus Walleij
next prev parent reply other threads:[~2019-05-03 6:49 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-29 23:28 linux-next: build warning after merge of the arm-soc tree Stephen Rothwell
2019-05-03 6:49 ` Linus Walleij [this message]
2019-05-03 12:57 ` Arnd Bergmann
-- strict thread matches above, loose matches on Subject: below --
2023-06-22 0:48 Stephen Rothwell
2023-06-22 8:19 ` Arnd Bergmann
2023-06-22 8:26 ` Krzysztof Kozlowski
2023-06-22 13:55 ` Rob Herring
2021-12-22 21:59 Stephen Rothwell
2021-12-22 23:22 ` Arnd Bergmann
2021-12-22 23:58 ` Florian Fainelli
2021-12-23 8:50 ` Arınç ÜNAL
2021-12-23 18:18 ` Florian Fainelli
2021-10-25 23:39 Stephen Rothwell
2021-10-26 6:15 ` Joel Stanley
2022-01-20 3:22 ` Stephen Rothwell
2022-01-20 6:03 ` ChiaWei Wang
2021-04-06 0:45 Stephen Rothwell
2021-04-06 6:34 ` Krzysztof Kozlowski
2019-08-15 23:25 Stephen Rothwell
2019-08-15 23:23 Stephen Rothwell
2014-01-19 23:39 Stephen Rothwell
2012-03-19 7:39 Stephen Rothwell
2012-03-19 9:40 ` Arnd Bergmann
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=CACRpkdYBuBf7jA2nUitiZWRriXVTPWCyB93q2CzmP4tbVZXqHA@mail.gmail.com \
--to=linus.walleij@linaro.org \
--cc=arnd@arndb.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=olof@lixom.net \
--cc=sfr@canb.auug.org.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
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;
as well as URLs for NNTP newsgroup(s).