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]

From: John Ogness
Date: Tue Nov 22 2022 - 09:27:34 EST

Next message: tip-bot2 for Julian Pidancet: "[tip: x86/alternatives] x86/alternative: Consistently patch SMP locks in vmlinux and modules"
Previous message: Benjamin Coddington: "Re: [PATCH v1 2/3] Treewide: Stop corrupting socket's task_frag"
In reply to: Naresh Kamboju: "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]"
Next in thread: Paul E. McKenney: "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]"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

Hi Petr,

On 2022-11-22, Naresh Kamboju <naresh.kamboju@xxxxxxxxxx> 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