All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jani Nikula <jani.nikula@linux.intel.com>
To: Maxime Ripard <mripard@kernel.org>,
	David Airlie <airlied@gmail.com>, Simona Vetter <simona@ffwll.ch>,
	Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
	Thomas Zimmermann <tzimmermann@suse.de>,
	Jonathan Corbet <corbet@lwn.net>
Cc: "Joonas Lahtinen" <joonas.lahtinen@linux.intel.com>,
	"Rodrigo Vivi" <rodrigo.vivi@intel.com>,
	"Tvrtko Ursulin" <tursulin@ursulin.net>,
	"Alex Deucher" <alexander.deucher@amd.com>,
	"Christian König" <christian.koenig@amd.com>,
	"Rob Clark" <robin.clark@oss.qualcomm.com>,
	"Dmitry Baryshkov" <lumag@kernel.org>,
	"Andrzej Hajda" <andrzej.hajda@intel.com>,
	"Neil Armstrong" <neil.armstrong@linaro.org>,
	"Robert Foss" <rfoss@kernel.org>,
	"Dave Stevenson" <dave.stevenson@raspberrypi.com>,
	"Laurent Pinchart" <laurent.pinchart@ideasonboard.com>,
	dri-devel@lists.freedesktop.org, linux-doc@vger.kernel.org,
	"Maxime Ripard" <mripard@kernel.org>,
	"Simona Vetter" <simona.vetter@ffwll.ch>
Subject: Re: [PATCH v2 0/2] drm: Rename drm_atomic_state
Date: Wed, 01 Apr 2026 15:41:42 +0300	[thread overview]
Message-ID: <5b2b2ff534b1994a3299be1daa7b4ec9db81ffbb@intel.com> (raw)
In-Reply-To: <20260331-drm-drm-atomic-update-v2-0-7e8fe6ddcd32@kernel.org>

On Tue, 31 Mar 2026, Maxime Ripard <mripard@kernel.org> wrote:
> We've been discussing for a long time about renaming drm_atomic_state
> to a better suited name, since the current one is a source of confusion
> and bugs.
>
> To minimize the impact, this should probably go through drm-next
> directly.
>
> Let me know what you think,

I don't really have strong opinions on this one, except I agree this
should go directly through drm-next before the merge window so everyone
can backmerge it. Otherwise it's going to be a conflicts galore.

IMO drivers can do the variable renames afterwards at leisure.

For the i915 parts,

Acked-by: Jani Nikula <jani.nikula@intel.com>

-- 
Jani Nikula, Intel

      parent reply	other threads:[~2026-04-01 12:41 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-31 14:41 [PATCH v2 0/2] drm: Rename drm_atomic_state Maxime Ripard
2026-03-31 14:41 ` [PATCH v2 1/2] " Maxime Ripard
2026-04-01  6:05   ` Thomas Zimmermann
2026-04-01  8:06     ` Maxime Ripard
2026-04-01  8:12       ` Thomas Zimmermann
2026-04-01 11:42   ` Luca Ceresoli
2026-03-31 14:41 ` [PATCH v2 2/2] Documentation: drm: Remove drm_atomic_state rename entry Maxime Ripard
2026-04-01 11:42   ` Luca Ceresoli
2026-04-01 12:41 ` Jani Nikula [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=5b2b2ff534b1994a3299be1daa7b4ec9db81ffbb@intel.com \
    --to=jani.nikula@linux.intel.com \
    --cc=airlied@gmail.com \
    --cc=alexander.deucher@amd.com \
    --cc=andrzej.hajda@intel.com \
    --cc=christian.koenig@amd.com \
    --cc=corbet@lwn.net \
    --cc=dave.stevenson@raspberrypi.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=joonas.lahtinen@linux.intel.com \
    --cc=laurent.pinchart@ideasonboard.com \
    --cc=linux-doc@vger.kernel.org \
    --cc=lumag@kernel.org \
    --cc=maarten.lankhorst@linux.intel.com \
    --cc=mripard@kernel.org \
    --cc=neil.armstrong@linaro.org \
    --cc=rfoss@kernel.org \
    --cc=robin.clark@oss.qualcomm.com \
    --cc=rodrigo.vivi@intel.com \
    --cc=simona.vetter@ffwll.ch \
    --cc=simona@ffwll.ch \
    --cc=tursulin@ursulin.net \
    --cc=tzimmermann@suse.de \
    /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.