Linux kernel -stable discussions
 help / color / mirror / Atom feed
From: Sasha Levin <sashal@kernel.org>
To: Jia Yao <jia.yao@intel.com>
Cc: "Sasha Levin" <sashal@kernel.org>,
	stable@vger.kernel.org,
	"Gwan-gyeong Mun" <gwan-gyeong.mun@intel.com>,
	"Matthew Auld" <matthew.auld@intel.com>,
	"Thomas Hellström" <thomas.hellstrom@linux.intel.com>,
	"Greg KH" <gregkh@linuxfoundation.org>
Subject: Re: [PATCH 6.18.y] drm/xe/guc_ads: allocate UM queues in VRAM on dGFX
Date: Tue, 25 Aug 2026 07:49:32 -0400	[thread overview]
Message-ID: <202608250012.1a23d959422d0fa2@kernel.org> (raw)
In-Reply-To: <2026082417-chill-banshee-11e4@gregkh>

On Mon, Aug 24, 2026 at 08:10:49AM +0200, Greg KH wrote:
> Ah, it needed to be applied after a different one?  Can you send these 3
> patches as a patch series, as that will tell us what order to apply them
> in.  Same for the 6.12 versions.

Jia Yao, on top of the series formatting there is a second problem: the
set as sent does not build on either branch.

Patch 1 calls xe_guc_using_main_gamctrl_queues(), which has no definition
on 6.18 or 6.12 - it only exists on 7.1. On 6.12 the same patch also uses
XE_BO_FLAG_PINNED_NORESTORE, which is undefined there.

-- 
Thanks,
Sasha

      reply	other threads:[~2026-08-25 11:49 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-20 11:13 FAILED: patch "[PATCH] drm/xe/guc_ads: allocate UM queues in VRAM on dGFX" failed to apply to 6.18-stable tree gregkh
2026-08-20 16:11 ` [PATCH 6.18.y] drm/xe/guc_ads: allocate UM queues in VRAM on dGFX Jia Yao
2026-08-24  6:09   ` Greg KH
2026-08-24  6:10     ` Greg KH
2026-08-25 11:49       ` Sasha Levin [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=202608250012.1a23d959422d0fa2@kernel.org \
    --to=sashal@kernel.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=gwan-gyeong.mun@intel.com \
    --cc=jia.yao@intel.com \
    --cc=matthew.auld@intel.com \
    --cc=stable@vger.kernel.org \
    --cc=thomas.hellstrom@linux.intel.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