From: John Ogness <john.ogness@linutronix.de>
To: paulmck@kernel.org, Petr Mladek <pmladek@suse.com>
Cc: Naresh Kamboju <naresh.kamboju@linaro.org>,
open list <linux-kernel@vger.kernel.org>,
Nathan Chancellor <nathan@kernel.org>,
Sergey Senozhatsky <senozhatsky@chromium.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]
Date: Wed, 23 Nov 2022 00:20:19 +0106 [thread overview]
Message-ID: <87wn7m7fas.fsf@jogness.linutronix.de> (raw)
In-Reply-To: <20221122220053.GO4001@paulmck-ThinkPad-P17-Gen-1>
On 2022-11-22, "Paul E. McKenney" <paulmck@kernel.org> wrote:
> And here is a first cut. There will be more patches removing uses
> of CONFIG_SRCU.
>
> Thoughts?
I am happy with it. Thanks!
> rcu: Make SRCU mandatory
>
> Kernels configured with CONFIG_PRINTK=n and CONFIG_SRCU=n get build
> failures. This causes trouble for deep embedded systems. But given
> that there are more than 25 instances of "select SRCU" in the kernel,
> it is hard to believe that there are many kernels running in production
> without SRCU. This commit therefore makes SRCU mandatory. The SRCU
> Kconfig option remains for backwards compatibility, and will be removed
> when it is no longer used.
>
> Reported-by: John Ogness <john.ogness@linutronix.de>
> Reported-by: Petr Mladek <pmladek@suse.com>
> Signed-off-by: Paul E. McKenney <paulmck@kernel.org>
Reviewed-by: John Ogness <john.ogness@linutronix.de>
next prev parent reply other threads:[~2022-11-22 23:14 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-22 9:08 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] Naresh Kamboju
2022-11-22 14:27 ` John Ogness
2022-11-22 14:48 ` Paul E. McKenney
2022-11-22 15:27 ` John Ogness
2022-11-22 15:55 ` Petr Mladek
2022-11-22 18:20 ` Paul E. McKenney
2022-11-22 22:00 ` Paul E. McKenney
2022-11-22 22:11 ` Randy Dunlap
2022-11-22 23:14 ` John Ogness [this message]
2022-11-22 23:42 ` Paul E. McKenney
2022-11-30 0:18 ` Paul E. McKenney
2022-11-30 8:53 ` John Ogness
2022-11-30 10:37 ` Petr Mladek
2022-11-30 21:59 ` Paul E. McKenney
2022-11-22 16:35 ` Paul E. McKenney
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87wn7m7fas.fsf@jogness.linutronix.de \
--to=john.ogness@linutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=naresh.kamboju@linaro.org \
--cc=nathan@kernel.org \
--cc=paulmck@kernel.org \
--cc=pmladek@suse.com \
--cc=senozhatsky@chromium.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox