From: Greg KH <gregkh@linuxfoundation.org>
To: andrzej.hajda@intel.com, chris.p.wilson@intel.com,
daniel.vetter@ffwll.ch, torvalds@linux-foundation.org
Cc: 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: Wed, 30 Nov 2022 19:05:55 +0100 [thread overview]
Message-ID: <Y4ebgwSCQPeCPtFY@kroah.com> (raw)
In-Reply-To: <1669831197124193@kroah.com>
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,
greg k-h
next prev parent reply other threads:[~2022-11-30 18:06 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 [this message]
2022-12-01 10:26 ` Andrzej Hajda
2022-12-01 12:16 ` Greg KH
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=Y4ebgwSCQPeCPtFY@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 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).