public inbox for stable-rt@vger.kernel.org
 help / color / mirror / Atom feed
From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
To: "Luis Claudio R. Goncalves" <lgoncalv@redhat.com>,
	Clark Williams <williams@redhat.com>
Cc: Steven Rostedt <rostedt@goodmis.org>,
	stable-rt <stable-rt@vger.kernel.org>
Subject: Re: rt: printk: create bogus deferred print functions (V2)
Date: Tue, 6 Jun 2023 11:53:08 +0200	[thread overview]
Message-ID: <20230606095308.ITricJVs@linutronix.de> (raw)
In-Reply-To: <ZG7EefZxJPa5fbjB@uudg.org>

On 2023-05-24 23:14:17 [-0300], Luis Claudio R. Goncalves wrote:
> > My question is whether I should use the workaround or something like
> > what Clark did in v5.15-rt:
> > 
> >     449f5e1c4ddef Revert "printk: remove deferred printing"
> > 
> > Which brings back all of deferred printing. I do hope, for my sanity, that
> > the answer is "workaround", but whatever you suggest is good for me :)
> 
> The original patch failed on aarch64. So I expanded the patch a bit and
> changed description, making it an extension of the deferred printing
> removal already in tree. The question remains the same. :)

I missed that this got reverted in the v5.15 tree. Please see what I
wrote to your release email. And this deferred thingy needs to go back
into v5.15.

Sebastian

      reply	other threads:[~2023-06-06  9:53 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-23 23:01 rt: printk: create bogus deferred print functions Luis Claudio R. Goncalves
2023-05-25  2:14 ` rt: printk: create bogus deferred print functions (V2) Luis Claudio R. Goncalves
2023-06-06  9:53   ` Sebastian Andrzej Siewior [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=20230606095308.ITricJVs@linutronix.de \
    --to=bigeasy@linutronix.de \
    --cc=lgoncalv@redhat.com \
    --cc=rostedt@goodmis.org \
    --cc=stable-rt@vger.kernel.org \
    --cc=williams@redhat.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