All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: Alex Deucher <alexdeucher@gmail.com>, Dave Airlie <airlied@redhat.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 amdgpu tree
Date: Mon, 22 Jun 2026 11:45:07 +0100	[thread overview]
Message-ID: <ajkSM2E3NMSYNc9M@sirena.org.uk> (raw)

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

Hi all,

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

  1b5e413713c0a ("drm/amdgpu: Fix context pstate override handling")

Please note that it is the merge window and you should not be adding any
commits not intended to be merged into Linus' tree during this merge
window.  Both copies of this commit were added on the same day, during
the merge window.

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

             reply	other threads:[~2026-06-22 10:45 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-22 10:45 Mark Brown [this message]
  -- strict thread matches above, loose matches on Subject: below --
2026-06-22 10:45 linux-next: duplicate patch in the amdgpu tree 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=ajkSM2E3NMSYNc9M@sirena.org.uk \
    --to=broonie@kernel.org \
    --cc=airlied@redhat.com \
    --cc=alexdeucher@gmail.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.