From: Sergey Senozhatsky <sergey.senozhatsky@gmail.com>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Cc: Petr Mladek <pmladek@suse.com>,
Sergey Senozhatsky <sergey.senozhatsky@gmail.com>,
linux-kernel@vger.kernel.org,
Steven Rostedt <rostedt@goodmis.org>,
John Ogness <john.ogness@linutronix.de>
Subject: Re: [PATCH v1] kernel.h: Move oops_in_progress to printk.h
Date: Mon, 14 Sep 2020 18:28:41 +0900 [thread overview]
Message-ID: <20200914092841.GC535@jagdpanzerIV.localdomain> (raw)
In-Reply-To: <20200911170202.8565-1-andriy.shevchenko@linux.intel.com>
On (20/09/11 20:02), Andy Shevchenko wrote:
[..]
> extern void bust_spinlocks(int yes);
> -extern int oops_in_progress; /* If set, an oops, panic(), BUG() or die() is in progress */
> extern int panic_timeout;
> extern unsigned long panic_print;
> extern int panic_on_oops;
> diff --git a/include/linux/printk.h b/include/linux/printk.h
> index 34c1a7be3e01..f749a2c2e7a5 100644
> --- a/include/linux/printk.h
> +++ b/include/linux/printk.h
> @@ -12,6 +12,8 @@
> extern const char linux_banner[];
> extern const char linux_proc_banner[];
>
> +extern int oops_in_progress; /* If set, an oops, panic(), BUG() or die() is in progress */
This can also become __read_mostly, I guess.
FWIW,
Acked-by: Sergey Senozhatsky <sergey.senozhatsky@gmail.com>
-ss
prev parent reply other threads:[~2020-09-14 9:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-11 17:02 Andy Shevchenko
2020-09-14 8:43 ` Petr Mladek
2020-09-14 15:00 ` Andy Shevchenko
2020-09-15 12:21 ` Petr Mladek
2020-09-15 12:54 ` Andy Shevchenko
2020-09-14 9:28 ` Sergey Senozhatsky [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=20200914092841.GC535@jagdpanzerIV.localdomain \
--to=sergey.senozhatsky@gmail.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=john.ogness@linutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=pmladek@suse.com \
--cc=rostedt@goodmis.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®