[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CAK8P3a1dy92NYX=bo6LYUGkFmKjGq65HjomOq7cCYDgx6ceoaA@mail.gmail.com>
Date: Fri, 3 May 2019 08:57:35 -0400
From: Arnd Bergmann <arnd@...db.de>
To: Linus Walleij <linus.walleij@...aro.org>
Cc: Stephen Rothwell <sfr@...b.auug.org.au>,
Olof Johansson <olof@...om.net>,
ARM <linux-arm-kernel@...ts.infradead.org>,
Linux Next Mailing List <linux-next@...r.kernel.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: linux-next: build warning after merge of the arm-soc tree
On Fri, May 3, 2019 at 2:49 AM Linus Walleij <linus.walleij@...aro.org> wrote:
>
> On Tue, Apr 30, 2019 at 12:28 AM Stephen Rothwell <sfr@...b.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.
Could you send a fixup patch to mark the function __maybe_unused or
move it into the #ifdef?
Arnd
Powered by blists - more mailing lists