LinuxPPC-Dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Petr Mladek <pmladek@suse.com>
To: John Ogness <john.ogness@linutronix.de>
Cc: linux-fbdev@vger.kernel.org, linux-efi@vger.kernel.org,
	"Geert Uytterhoeven" <geert+renesas@glider.be>,
	"Peter Zijlstra" <peterz@infradead.org>,
	kgdb-bugreport@lists.sourceforge.net,
	dri-devel@lists.freedesktop.org,
	"Douglas Anderson" <dianders@chromium.org>,
	"Eric Dumazet" <edumazet@google.com>,
	netdev@vger.kernel.org, "Alim Akhtar" <alim.akhtar@samsung.com>,
	"Jiri Slaby" <jirislaby@kernel.org>,
	"Ard Biesheuvel" <ardb@kernel.org>,
	"Anton Ivanov" <anton.ivanov@cambridgegreys.com>,
	"Daniel Thompson" <daniel.thompson@linaro.org>,
	linux-samsung-soc@vger.kernel.org, "Tom Rix" <trix@redhat.com>,
	"Richard Weinberger" <richard@nod.at>,
	"Helge Deller" <deller@gmx.de>,
	"Krzysztof Kozlowski" <krzysztof.kozlowski@linaro.org>,
	"Geert Uytterhoeven" <geert@linux-m68k.org>,
	linux-serial@vger.kernel.org, "Aaron Tomlin" <atomlin@redhat.com>,
	"Miguel Ojeda" <ojeda@kernel.org>,
	"Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>,
	"Paolo Abeni" <pabeni@redhat.com>,
	"Michal Simek" <michal.simek@xilinx.com>,
	linux-um@lists.infradead.org,
	"Steven Rostedt" <rostedt@goodmis.org>,
	linux-m68k@lists.linux-m68k.org,
	"Jakub Kicinski" <kuba@kernel.org>,
	"Thomas Gleixner" <tglx@linutronix.de>,
	"Andy Shevchenko" <andriy.shevchenko@linux.intel.com>,
	linux-arm-kernel@lists.infradead.org,
	"Juergen Gross" <jgross@suse.com>,
	"Mathias Nyman" <mathias.nyman@linux.intel.com>,
	"Boris Ostrovsky" <boris.ostrovsky@oracle.com>,
	"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
	linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org,
	"Sergey Senozhatsky" <senozhatsky@chromium.org>,
	"Luis Chamberlain" <mcgrof@kernel.org>,
	"Lukas Wunner" <lukas@wunner.de>,
	"Thomas Zimmermann" <tzimmermann@suse.de>,
	"Jason Wessel" <jason.wessel@windriver.com>,
	linux-fsdevel@vger.kernel.org,
	"Javier Martinez Canillas" <javierm@redhat.com>,
	"Johannes Berg" <johannes@sipsolutions.net>,
	linuxppc-dev@lists.ozlabs.org,
	"David S. Miller" <davem@davemloft.net>
Subject: Re: [PATCH printk v5 00/40] reduce console_lock scope
Date: Fri, 18 Nov 2022 12:22:56 +0100	[thread overview]
Message-ID: <Y3drEOkD1fuZcvV2@alley> (raw)
In-Reply-To: <20221116162152.193147-1-john.ogness@linutronix.de>

On Wed 2022-11-16 17:27:12, John Ogness wrote:
> This is v5 of a series to prepare for threaded/atomic
> printing. v4 is here [0]. This series focuses on reducing the
> scope of the BKL console_lock. It achieves this by switching to
> SRCU and a dedicated mutex for console list iteration and
> modification, respectively. The console_lock will no longer
> offer this protection.

The patchset looks ready for linux-next from my POV.

I am going to push it there right now to get as much testing
as possible before the merge window.

Any review and comments are still appreciate. We could always
take it back if some critical problems are discovered and
can't be solved easily.

Best Regards,
Petr

  parent reply	other threads:[~2022-11-18 11:24 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-16 16:21 [PATCH printk v5 00/40] reduce console_lock scope John Ogness
2022-11-16 16:21 ` [PATCH printk v5 25/40] tty: hvc: use console_is_registered() John Ogness
2022-11-18 11:22 ` Petr Mladek [this message]
2022-11-18 14:55   ` [PATCH printk v5 00/40] reduce console_lock scope Petr Mladek
2022-11-22 16:43 ` Greg Kroah-Hartman

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=Y3drEOkD1fuZcvV2@alley \
    --to=pmladek@suse.com \
    --cc=alim.akhtar@samsung.com \
    --cc=andriy.shevchenko@linux.intel.com \
    --cc=anton.ivanov@cambridgegreys.com \
    --cc=ardb@kernel.org \
    --cc=atomlin@redhat.com \
    --cc=boris.ostrovsky@oracle.com \
    --cc=daniel.thompson@linaro.org \
    --cc=davem@davemloft.net \
    --cc=deller@gmx.de \
    --cc=dianders@chromium.org \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=edumazet@google.com \
    --cc=geert+renesas@glider.be \
    --cc=geert@linux-m68k.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=ilpo.jarvinen@linux.intel.com \
    --cc=jason.wessel@windriver.com \
    --cc=javierm@redhat.com \
    --cc=jgross@suse.com \
    --cc=jirislaby@kernel.org \
    --cc=johannes@sipsolutions.net \
    --cc=john.ogness@linutronix.de \
    --cc=kgdb-bugreport@lists.sourceforge.net \
    --cc=krzysztof.kozlowski@linaro.org \
    --cc=kuba@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-efi@vger.kernel.org \
    --cc=linux-fbdev@vger.kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-m68k@lists.linux-m68k.org \
    --cc=linux-samsung-soc@vger.kernel.org \
    --cc=linux-serial@vger.kernel.org \
    --cc=linux-um@lists.infradead.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=lukas@wunner.de \
    --cc=mathias.nyman@linux.intel.com \
    --cc=mcgrof@kernel.org \
    --cc=michal.simek@xilinx.com \
    --cc=netdev@vger.kernel.org \
    --cc=ojeda@kernel.org \
    --cc=pabeni@redhat.com \
    --cc=peterz@infradead.org \
    --cc=richard@nod.at \
    --cc=rostedt@goodmis.org \
    --cc=senozhatsky@chromium.org \
    --cc=tglx@linutronix.de \
    --cc=trix@redhat.com \
    --cc=tzimmermann@suse.de \
    /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