From: John Ogness <john.ogness@linutronix.de>
To: Petr Mladek <pmladek@suse.com>
Cc: Sergey Senozhatsky <senozhatsky@chromium.org>,
Steven Rostedt <rostedt@goodmis.org>,
Thomas Gleixner <tglx@linutronix.de>,
linux-kernel@vger.kernel.org,
Todd Brandt <todd.e.brandt@intel.com>
Subject: Re: [PATCH printk] printk: flush consoles before checking progress
Date: Wed, 04 Oct 2023 14:53:23 +0206 [thread overview]
Message-ID: <87h6n6y2p0.fsf@jogness.linutronix.de> (raw)
In-Reply-To: <ZR1dBAOMmMUNgY6Q@alley>
On 2023-10-04, Petr Mladek <pmladek@suse.com> wrote:
> Are you going to prepare them or should I?
Really it was your version that we are taking. I suppose you should post
them and I can review them.
Also, the Closes tag probably should just be on the lock/unlock patch.
John
prev parent reply other threads:[~2023-10-04 12:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-29 11:32 John Ogness
2023-09-29 13:43 ` Petr Mladek
2023-10-02 13:05 ` Petr Mladek
2023-10-04 10:25 ` John Ogness
2023-10-04 12:39 ` Petr Mladek
2023-10-04 12:47 ` John Ogness [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=87h6n6y2p0.fsf@jogness.linutronix.de \
--to=john.ogness@linutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=pmladek@suse.com \
--cc=rostedt@goodmis.org \
--cc=senozhatsky@chromium.org \
--cc=tglx@linutronix.de \
--cc=todd.e.brandt@intel.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
all inboxes | Powered by JetHome®