All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sergey Senozhatsky <sergey.senozhatsky.work@gmail.com>
To: John Ogness <john.ogness@linutronix.de>
Cc: Petr Mladek <pmladek@suse.com>,
	Sergey Senozhatsky <sergey.senozhatsky.work@gmail.com>,
	Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
	Sergey Senozhatsky <sergey.senozhatsky@gmail.com>,
	linux-kernel@vger.kernel.org,
	Steven Rostedt <rostedt@goodmis.org>
Subject: Re: [PATCH v1] printk: Declare log_wait as external variable
Date: Thu, 13 Feb 2020 21:02:14 +0900	[thread overview]
Message-ID: <20200213120214.GD36551@google.com> (raw)
In-Reply-To: <8736bfdgsz.fsf@linutronix.de>

On (20/02/12 15:24), John Ogness wrote:
> On 2020-02-12, Petr Mladek <pmladek@suse.com> wrote:
[..]
> >> I can take a look at dev_ksmg.c/proc_kmsg.c option, unless
> >> someone else wants to spend their time on this.
> >
> > It would be lovely from my POV. I am only concerned about
> > the lockless printk() stuff. I would prefer to avoid creating
> > too many conflicts in the same merge window. Well, I am
> > not sure how many conflicts there would be. Adding John
> > into CC.
>
> I would also love to see these changes. But can we _please_ focus on the
> lockless printk ringbuffer merge first?

Agreed.

> The patches already exist and are (hopefully) being reviewed.
				^^^
				are (hopefully) being tested.

	-ss

      reply	other threads:[~2020-02-13 12:02 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-03 13:15 [PATCH v1] printk: Declare log_wait as external variable Andy Shevchenko
2020-02-04  2:16 ` Sergey Senozhatsky
2020-02-04  9:05   ` Andy Shevchenko
2020-02-04 11:22     ` Sergey Senozhatsky
2020-02-04 11:31       ` Andy Shevchenko
2020-02-11 12:43 ` Petr Mladek
2020-02-12  1:31   ` Sergey Senozhatsky
2020-02-12 14:03     ` Petr Mladek
2020-02-12 14:24       ` John Ogness
2020-02-13 12:02         ` 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=20200213120214.GD36551@google.com \
    --to=sergey.senozhatsky.work@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 \
    --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 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.