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 - 10:28:02 EST

Next message: Palmer Dabbelt: "Re: [PATCH] cpuidle: riscv-sbi: Stop using non-retentive suspend"
Previous message: Xiu Jianfeng: "[PATCH] clk: visconti: Fix memory leak in visconti_register_pll()"
In reply to: 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]"
Next in thread: Petr Mladek: "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 ]

On 2022-11-22, "Paul E. McKenney" <paulmck@xxxxxxxxxx> wrote:
>> @paulmck: Do you have a problem with permanently activating CONFIG_SRCU?
>
> The people wanting it separate back in the day were those wanting very
> tiny kernels. I have not heard from them in a long time, so maybe it
> is now OK to just make SRCU unconditional.

Who decides this? Or maybe I should create a semaphore-based Variant of
console_srcu_read_lock()/console_srcu_read_unlock() for the
"!CONFIG_PRINTK && !CONFIG_SRCU" case?

John