All of lore.kernel.org
 help / color / mirror / Atom feed
From: John Ogness <john.ogness@linutronix.de>
To: Petr Mladek <pmladek@suse.com>
Cc: "Paul E . McKenney" <paulmck@kernel.org>,
	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 15:33:16 +0106	[thread overview]
Message-ID: <87o7szoyij.fsf@jogness.linutronix.de> (raw)
In-Reply-To: <CA+G9fYvCWwndXdsvuW7iJ25wgfN6_iMY-OC_z6ufSwiJkzFFMw@mail.gmail.com>

Hi Petr,

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

  reply	other threads:[~2022-11-22 14:27 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 [this message]
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

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=87o7szoyij.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.