From: Greg KH <gregkh@linuxfoundation.org>
To: Andrzej Hajda <andrzej.hajda@intel.com>
Cc: chris.p.wilson@intel.com, daniel.vetter@ffwll.ch,
torvalds@linux-foundation.org, stable@vger.kernel.org
Subject: Re: FAILED: patch "[PATCH] drm/i915: fix TLB invalidation for Gen12 video and compute" failed to apply to 5.15-stable tree
Date: Thu, 1 Dec 2022 13:16:09 +0100 [thread overview]
Message-ID: <Y4ibCXKoanYDVU81@kroah.com> (raw)
In-Reply-To: <958bb07e-1cc5-d97b-5480-6d8ce09c27d8@intel.com>
On Thu, Dec 01, 2022 at 11:26:05AM +0100, Andrzej Hajda wrote:
>
>
> On 30.11.2022 19:05, Greg KH wrote:
> > On Wed, Nov 30, 2022 at 06:59:57PM +0100, gregkh@linuxfoundation.org wrote:
> > > The patch below does not apply to the 5.15-stable tree.
> > > If someone wants it applied there, or to any other stable or longterm
> > > tree, then please email the backport, including the original git commit
> > > id to <stable@vger.kernel.org>.
> > >
> > > Possible dependencies:
> > >
> > > 04aa64375f48 ("drm/i915: fix TLB invalidation for Gen12 video and compute engines")
> > > 33da97894758 ("drm/i915/gt: Serialize TLB invalidates with GT resets")
> > > 7938d61591d3 ("drm/i915: Flush TLBs before releasing backing store")
> > > 1176d15f0f6e ("Merge tag 'drm-intel-gt-next-2021-10-08' of git://anongit.freedesktop.org/drm/drm-intel into drm-next")
> > >
> > Ah, wait, I found the tarball you sent for these, and have taken them
> > for 5.4, 5.10, and 5.15 now (the original broke the build.) We still
> > need them for older kernels though, that's still an issue.
>
> Thanks for applying patches.
> Older kernels ( < 5.4) do not have the patch to fix ("drm/i915: Flush TLBs
> before releasing backing store"), and they do not support Gen12 AFAIK,
> so it should be fine.
The Fixes: tag in this commit references a commit that has been
backported into a lot of older kernels:
git id: '7938d61591d33394a21bdd7797a245b65428f44c' is in: 4.4.301 4.9.299 4.14.264 4.19.227 5.4.175 5.10.95 5.15.18 5.16.4 5.17
So is the Fixes tag incorrect?
thanks,
greg k-h
next prev parent reply other threads:[~2022-12-01 12:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-30 17:59 FAILED: patch "[PATCH] drm/i915: fix TLB invalidation for Gen12 video and compute" failed to apply to 5.15-stable tree gregkh
2022-11-30 18:05 ` Greg KH
2022-12-01 10:26 ` Andrzej Hajda
2022-12-01 12:16 ` Greg KH [this message]
2022-12-01 12:48 ` Andrzej Hajda
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=Y4ibCXKoanYDVU81@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=andrzej.hajda@intel.com \
--cc=chris.p.wilson@intel.com \
--cc=daniel.vetter@ffwll.ch \
--cc=stable@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
/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.