From: Sasha Levin <sashal@kernel.org>
To: Shuicheng Lin <shuicheng.lin@intel.com>
Cc: stable@vger.kernel.org, Koen Koning <koen.koning@intel.com>,
Peter Senna Tschudin <peter.senna@linux.intel.com>,
Matthew Auld <matthew.auld@intel.com>,
Lucas De Marchi <lucas.demarchi@intel.com>
Subject: Re: [PATCH 6.12.y] drm/xe: Prevent BIT() overflow when handling invalid prefetch region
Date: Wed, 26 Nov 2025 07:07:22 -0500 [thread overview]
Message-ID: <20251126120722.1357962-1-sashal@kernel.org> (raw)
In-Reply-To: <20251124222827.901507-2-shuicheng.lin@intel.com>
This patch has been queued up for the 6.12 stable tree.
Subject: drm/xe: Prevent BIT() overflow when handling invalid prefetch region
Queue: 6.12
Thanks for the backport!
prev parent reply other threads:[~2025-11-26 12:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-24 13:55 FAILED: patch "[PATCH] drm/xe: Prevent BIT() overflow when handling invalid prefetch" failed to apply to 6.12-stable tree gregkh
2025-11-24 22:28 ` [PATCH 6.12.y] drm/xe: Prevent BIT() overflow when handling invalid prefetch region Shuicheng Lin
2025-11-26 12:07 ` 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=20251126120722.1357962-1-sashal@kernel.org \
--to=sashal@kernel.org \
--cc=koen.koning@intel.com \
--cc=lucas.demarchi@intel.com \
--cc=matthew.auld@intel.com \
--cc=peter.senna@linux.intel.com \
--cc=shuicheng.lin@intel.com \
--cc=stable@vger.kernel.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