From: "Paul E. McKenney" <paulmck@kernel.org>
To: John Ogness <john.ogness@linutronix.de>
Cc: Petr Mladek <pmladek@suse.com>,
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: Tue, 22 Nov 2022 08:35:14 -0800 [thread overview]
Message-ID: <20221122163514.GL4001@paulmck-ThinkPad-P17-Gen-1> (raw)
In-Reply-To: <87leo3ovpw.fsf@jogness.linutronix.de>
On Tue, Nov 22, 2022 at 04:33:39PM +0106, John Ogness wrote:
> On 2022-11-22, "Paul E. McKenney" <paulmck@kernel.org> 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?
As an alternative, I will queue the patch making SRCU unconditional. ;-)
Thanx, Paul
prev parent reply other threads:[~2022-11-22 16:35 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-22 9:08 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
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 [this message]
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=20221122163514.GL4001@paulmck-ThinkPad-P17-Gen-1 \
--to=paulmck@kernel.org \
--cc=john.ogness@linutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=naresh.kamboju@linaro.org \
--cc=nathan@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
all inboxes | Powered by JetHome®