Linux-Next discussions
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: Dave Airlie <airlied@redhat.com>, DRI <dri-devel@lists.freedesktop.org>
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: Tue, 9 Jun 2026 18:53:54 +0100	[thread overview]
Message-ID: <aihTMkjR4v3MgwFa@sirena.co.uk> (raw)

[-- Attachment #1: Type: text/plain, Size: 518 bytes --]

Hi all,

The following commit is also in the drm-fixes tree as a different commit
(but the same patch):

  01112e241e37f9 ("drm/amdkfd: Unwind debug trap enable on copy_to_user failure")
  0ac98160dfb6ab ("drm/amdgpu/userq: Fix reading timeline points in wait ioctl")
  115bf5ca318e18 ("drm/amd/display: Consult MCCS FreeSync cap only if requested & supported")
  39eb6da7acee8d ("drm/amdkfd: Add bounds check for AMDKFD_IOC_WAIT_EVENTS")
  92a8dba246d371 ("drm/amdkfd: fix SMI event cross-process information leak")


[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

                 reply	other threads:[~2026-06-09 17:53 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=aihTMkjR4v3MgwFa@sirena.co.uk \
    --to=broonie@kernel.org \
    --cc=airlied@redhat.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