[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <87o7szoyij.fsf@jogness.linutronix.de>
Date: Tue, 22 Nov 2022 15:33:16 +0106
From: John Ogness <john.ogness@...utronix.de>
To: Petr Mladek <pmladek@...e.com>
Cc: "Paul E . McKenney" <paulmck@...nel.org>,
Naresh Kamboju <naresh.kamboju@...aro.org>,
open list <linux-kernel@...r.kernel.org>,
Nathan Chancellor <nathan@...nel.org>,
Sergey Senozhatsky <senozhatsky@...omium.org>
Subject: Re: next-20221122: tinyconfig: ppc n s390:
kernel/printk/printk.c:95:1: error: type specifier missing, defaults to
'int'; ISO C99 and later do not support implicit int
[-Werror,-Wimplicit-int]
Hi Petr,
On 2022-11-22, Naresh Kamboju <naresh.kamboju@...aro.org> wrote:
> Today's Linux next 20221122 tag clang-15 tinyconfig builds fails on
> powerpc and s390 architectures.
The problem is that CONFIG_SRCU is not selected. This must be selected
by any modules that requires SRCU. However, printk.c is _always_ built
into the kernel (even if !CONFIG_PRINTK). The registration of consoles
and the console list (which uses SRCU) is _always_ built into the
kernel.
So should CONFIG_SRCU now always be active?
@paulmck: Do you have a problem with permanently activating CONFIG_SRCU?
John Ogness
Powered by blists - more mailing lists