From: Joseph Salisbury <joseph.salisbury@canonical.com>
To: Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
paul.gortmaker@windriver.com
Cc: Clark Williams <williams@redhat.com>,
linux-rt-users@vger.kernel.org,
Tvrtko Ursulin <tvrtko.ursulin@intel.com>
Subject: Re: [PATCH 6.1-rt/5.15-rt 0/1] Backport i915 reset fix from v6.4-rt
Date: Wed, 18 Oct 2023 15:58:44 -0400 [thread overview]
Message-ID: <74328823-62b4-451b-a106-b9e3f1cb8f68@canonical.com> (raw)
In-Reply-To: <20230823133915.gu_SxqTS@linutronix.de>
On 8/23/23 09:39, Sebastian Andrzej Siewior wrote:
> On 2023-08-18 22:45:24 [-0400], paul.gortmaker@windriver.com wrote:
>> From: Paul Gortmaker <paul.gortmaker@windriver.com>
> Hi Paul,
>
>> However, the original regression was reported on v5.15-rt. This closes
>> the loop by backporting the v6.4-rt change to v5.15-rt/v6.1-rt -- as it
>> turns out, the same backport applies cleanly to both baselines.
> Thanks for the ping. I've sent a backport request
> https://lore.kernel.org/all/20230727105040.4V9DQ5pM@linutronix.de/
>
> which includes the patch. It didn't go very so far but I am full of hope
> ;)
>
> Sebastian
Hi Paul,
I just announced a release candidate that has this patch. The version
is: v5.15.133-rt70-rc1.
If there are no negative reports, this will be the next v5.15-rt
release, which only contains the patches in the announcement.
Thanks,
Joe
prev parent reply other threads:[~2023-10-18 19:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-19 2:45 [PATCH 6.1-rt/5.15-rt 0/1] Backport i915 reset fix from v6.4-rt paul.gortmaker
2023-08-19 2:45 ` [PATCH 1/1] drm/i915: Do not disable preemption for resets paul.gortmaker
2023-08-23 13:39 ` [PATCH 6.1-rt/5.15-rt 0/1] Backport i915 reset fix from v6.4-rt Sebastian Andrzej Siewior
2023-08-23 17:57 ` Joseph Salisbury
2023-10-18 19:58 ` Joseph Salisbury [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=74328823-62b4-451b-a106-b9e3f1cb8f68@canonical.com \
--to=joseph.salisbury@canonical.com \
--cc=bigeasy@linutronix.de \
--cc=linux-rt-users@vger.kernel.org \
--cc=paul.gortmaker@windriver.com \
--cc=tvrtko.ursulin@intel.com \
--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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).