From: "Luis Claudio R. Goncalves" <lgoncalv@redhat.com>
To: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
Cc: linux-rt-users <linux-rt-users@vger.kernel.org>,
stable-rt <stable-rt@vger.kernel.org>,
Steven Rostedt <rostedt@goodmis.org>,
Thomas Gleixner <tglx@linutronix.de>,
Daniel Wagner <daniel.wagner@suse.com>,
Mark Gross <markgross@kernel.org>
Subject: Re: [PATCH RT 0/3] Linux v4.14.320-rt152-rc1
Date: Wed, 9 Aug 2023 10:50:59 -0300 [thread overview]
Message-ID: <ZNOZw6ubyVkrqw+J@uudg.org> (raw)
In-Reply-To: <20230809081738.qhWKi8Os@linutronix.de>
On Wed, Aug 09, 2023 at 10:17:38AM +0200, Sebastian Andrzej Siewior wrote:
> On 2023-08-08 13:35:17 [-0300], Luis Claudio R. Goncalves wrote:
> > Dear RT Folks,
> >
> > This is the RT stable review cycle of patch 4.14.320-rt152-rc1.
> >
> > Please scream at me if I messed something up. Please test the patches
> > too.
>
> Looks good, just a nitpick: If you add 2/3 you don't need 1/3.
Agreed. I just kept 1/3 because I wanted to both give credit to André Pribil
for reporting the problem and also highlight the symptom he observed.
Should I add that as a note on 2/3 and drop the first patch?
Thanks for reviewing the RC!
Luis
next prev parent reply other threads:[~2023-08-09 13:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-08 16:35 [PATCH RT 0/3] Linux v4.14.320-rt152-rc1 Luis Claudio R. Goncalves
2023-08-08 16:35 ` [PATCH RT 1/3] rt: timers: use CONFIG_PREEMPT_RT_FULL instead of CONFIG_PREEMPT_RT Luis Claudio R. Goncalves
2023-08-08 16:35 ` [PATCH RT 2/3] rt: PREEMPT_RT safety net for backported patches Luis Claudio R. Goncalves
2023-08-08 16:35 ` [PATCH RT 3/3] Linux 4.14.320-rt152-rc1 Luis Claudio R. Goncalves
2023-08-09 8:17 ` [PATCH RT 0/3] Linux v4.14.320-rt152-rc1 Sebastian Andrzej Siewior
2023-08-09 13:50 ` Luis Claudio R. Goncalves [this message]
2023-08-09 14:10 ` Sebastian Andrzej Siewior
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=ZNOZw6ubyVkrqw+J@uudg.org \
--to=lgoncalv@redhat.com \
--cc=bigeasy@linutronix.de \
--cc=daniel.wagner@suse.com \
--cc=linux-rt-users@vger.kernel.org \
--cc=markgross@kernel.org \
--cc=rostedt@goodmis.org \
--cc=stable-rt@vger.kernel.org \
--cc=tglx@linutronix.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;
as well as URLs for NNTP newsgroup(s).