From: Mark Brown <broonie@kernel.org>
To: Dave Airlie <airlied@redhat.com>,
DRI <dri-devel@lists.freedesktop.org>,
David Francis <David.Francis@amd.com>,
Alex Deucher <alexander.deucher@amd.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: linux-next: duplicate patch in the drm tree
Date: Fri, 10 Jul 2026 15:05:32 +0100 [thread overview]
Message-ID: <alD8LLeWXZ5t9TgK@sirena.org.uk> (raw)
[-- Attachment #1: Type: text/plain, Size: 267 bytes --]
Hi all,
The following commit is also in the drm-fixes tree as a different commit
(but the same patch):
f19d8086f6644 (drm/amdkfd: Check bounds on CRIU restore queue type and mqd size)
1cafa8b29e029 (drm/amdkfd: Don't acquire buffers during CRIU queue restore.)
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2026-07-10 14:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-10 14:05 Mark Brown [this message]
-- strict thread matches above, loose matches on Subject: below --
2026-07-31 14:01 linux-next: duplicate patch in the drm tree Mark Brown
2026-06-09 17:53 Mark Brown
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=alD8LLeWXZ5t9TgK@sirena.org.uk \
--to=broonie@kernel.org \
--cc=David.Francis@amd.com \
--cc=airlied@redhat.com \
--cc=alexander.deucher@amd.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@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