From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Petr Mladek <pmladek@suse.com>
Cc: 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: Tue, 15 Sep 2020 15:54:29 +0300 [thread overview]
Message-ID: <20200915125429.GV3956970@smile.fi.intel.com> (raw)
In-Reply-To: <20200915122125.GG11154@alley>
On Tue, Sep 15, 2020 at 02:21:25PM +0200, Petr Mladek wrote:
> On Mon 2020-09-14 18:00:18, Andy Shevchenko wrote:
> > On Mon, Sep 14, 2020 at 10:43:32AM +0200, Petr Mladek wrote:
> > > On Fri 2020-09-11 20:02:02, Andy Shevchenko wrote:
> > > > The oops_in_progress is defined in printk.c, so it's logical
> > > > to move oops_in_progress to printk.h.
> > > >
> > > > Signed-off-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
> > >
> > > Yeah, it makes sense.
> > >
> > > Acked-by: Petr Mladek <pmladek@suse.com>
> > >
> > > I am always a bit afraid of messing with these heavily used includes.
> > > Let's see if boots complain about some build failure.
> >
> > Agree.
> >
> > Just to clarify: I assumed, might be wrongly, that this will go via PRINTK
> > tree. If you have something else in mind, please tell, I will route it to
> > the corresponding maintainer(s).
>
> I have just pushed the patch into printk/linux.git, branch for-5.10.
>
> I am sorry that I was not clear enough. I wanted to wait at least one
> day just in case anyone (human or robot) complains.
Thank you, Petr, for clarification and applying it!
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2020-09-15 13:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-11 17:02 [PATCH v1] kernel.h: Move oops_in_progress to printk.h 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 [this message]
2020-09-14 9:28 ` Sergey Senozhatsky
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=20200915125429.GV3956970@smile.fi.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=john.ogness@linutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=pmladek@suse.com \
--cc=rostedt@goodmis.org \
--cc=sergey.senozhatsky@gmail.com \
/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