mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: Alex Deucher <alexdeucher@gmail.com>
Cc: Alex Deucher <alexander.deucher@amd.com>,
	Bhawanpreet Lakha <Bhawanpreet.Lakha@amd.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Next Mailing List <linux-next@vger.kernel.org>,
	Maxime Ripard <mripard@kernel.org>,
	Tom Chung <chiahsuan.chung@amd.com>
Subject: linux-next: manual merge of the amdgpu tree with the drm-misc tree
Date: Mon, 14 Sep 2026 13:57:36 +0100	[thread overview]
Message-ID: <aqfvQDZ288iSPpR0@sirena.co.uk> (raw)

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

Hi all,

Today's linux-next merge of the amdgpu tree got a conflict in:

  drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm_crtc.h

between commit:

  32fbec62a3e9f ("drm/amdgpu: dm: Convert to atomic_create_state")

from the drm-misc tree and commit:

  b40f65c12577b ("drm/amd/display: Cover crtc destroy callback")

from the amdgpu tree (there are furher fixups later).

I fixed it up (see below) and can carry the fix as necessary. This
is now fixed as far as linux-next is concerned, but any non trivial
conflicts should be mentioned to your upstream maintainer when your tree
is submitted for merging.  You may also want to consider cooperating
with the maintainer of the conflicting tree to minimise any particularly
complex conflicts.

diff --cc drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm_crtc.h
index ad516aeb9798e,91fdd262c2d2d..0000000000000
--- a/drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm_crtc.h
+++ b/drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm_crtc.h
@@@ -49,7 -49,8 +49,8 @@@ bool amdgpu_dm_crtc_helper_mode_fixup(s
  void amdgpu_dm_crtc_destroy_state(struct drm_crtc *crtc,
  				  struct drm_crtc_state *state);
  struct drm_crtc_state *amdgpu_dm_crtc_duplicate_state(struct drm_crtc *crtc);
 +struct drm_crtc_state *amdgpu_dm_crtc_create_state(struct drm_crtc *crtc);
+ void amdgpu_dm_crtc_destroy(struct drm_crtc *crtc);
 -void amdgpu_dm_crtc_reset_state(struct drm_crtc *crtc);
  int amdgpu_dm_crtc_count_crtc_active_planes(struct drm_crtc_state *new_crtc_state);
  void amdgpu_dm_crtc_update_crtc_active_planes(struct drm_crtc *crtc,
  					      struct drm_crtc_state *new_crtc_state);

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

             reply	other threads:[~2026-09-14 12:57 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-14 12:57 Mark Brown [this message]
  -- strict thread matches above, loose matches on Subject: below --
2026-09-14 13:31 Mark Brown
2026-09-08 16:34 Mark Brown
2026-09-08 17:16 ` Mark Brown
2026-09-08 18:22   ` Mark Brown
2026-06-30 15:27 Mark Brown
2025-07-17  2:46 Stephen Rothwell
2024-08-26  1:10 Stephen Rothwell
2024-08-28  2:11 ` Stephen Rothwell
2023-05-15  1:18 Stephen Rothwell
2023-01-16  0:48 Stephen Rothwell
2022-11-16  0:09 Stephen Rothwell
2022-04-06  0:34 Stephen Rothwell
2022-04-13  0:10 ` Stephen Rothwell
2022-04-29  1:13   ` Stephen Rothwell
2022-04-29 10:38     ` Christian König
2021-12-13 15:08 broonie
2021-06-03  2:48 Stephen Rothwell
2021-06-03  2:55 ` Stephen Rothwell
2021-06-04  2:33 ` Stephen Rothwell
2021-05-21  1:42 Stephen Rothwell
2021-05-21  1:38 Stephen Rothwell
2021-05-21  1:20 Stephen Rothwell
2021-05-21  1:16 Stephen Rothwell
2021-05-12  0:20 Stephen Rothwell

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=aqfvQDZ288iSPpR0@sirena.co.uk \
    --to=broonie@kernel.org \
    --cc=Bhawanpreet.Lakha@amd.com \
    --cc=alexander.deucher@amd.com \
    --cc=alexdeucher@gmail.com \
    --cc=chiahsuan.chung@amd.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=mripard@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

all inboxes | Powered by JetHome®