[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAK8P3a1fEq6n1pBqkY4CqxpSZnMLOQsNHFyhB_L4uo-oZVu4sw@mail.gmail.com>
Date: Fri, 29 May 2020 23:07:56 +0200
From: Arnd Bergmann <arnd@...db.de>
To: Tony Lindgren <tony@...mide.com>
Cc: SoC Team <soc@...nel.org>, Olof Johansson <olof@...om.net>,
Stefan Agner <stefan@...er.ch>,
Linux ARM <linux-arm-kernel@...ts.infradead.org>,
linux-omap <linux-omap@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] ARM: omap2: fix omap5_realtime_timer_init definition
On Fri, May 29, 2020 at 10:44 PM Tony Lindgren <tony@...mide.com> wrote:
>
> * Arnd Bergmann <arnd@...db.de> [200529 20:18]:
> > There is one more regression introduced by the last build fix:
>
> Argh.. I did run make randconfig for like 10 builds
> after the last fix.
>
> > Address this by removing the now obsolete #ifdefs in that file and
> > just building the entire file based on the flag that controls the
> > omap5_realtime_timer_init function declaration.
>
> I think this will introduce other randconfig build failures
> as SOC_HAS_REALTIME_COUNTER is bool in Kconfig.
I did a few hundred randconfig builds with the patch and have
not yet seen any further problems.
> We still need to call omap5_realtime_timer_init() even if
> SOC_HAS_REALTIME_COUNTER is not set.
This is what's in the header file:
#ifdef CONFIG_SOC_HAS_REALTIME_COUNTER
extern void omap5_realtime_timer_init(void);
#else
static inline void omap5_realtime_timer_init(void)
{
}
#endif
In fact, the inline stub is what that caused the regression,
so I think it's ok with my patch.
Arnd
Powered by blists - more mailing lists