From: Thomas Zimmermann <tzimmermann@suse.de>
To: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
Cc: "Sean Paul" <seanpaul@chromium.org>,
"Paul Kocialkowski" <paul.kocialkowski@bootlin.com>,
"Sui Jingfeng" <suijingfeng@loongson.cn>,
"Andrzej Hajda" <andrzej.hajda@intel.com>,
"Jani Nikula" <jani.nikula@intel.com>,
dri-devel@lists.freedesktop.org,
"Javier Martinez Canillas" <javierm@redhat.com>,
"Maxime Ripard" <mripard@kernel.org>,
"Russell King (Oracle)" <linux@armlinux.org.uk>,
"Julia Lawall" <julia.lawall@inria.fr>,
"Luben Tuikov" <luben.tuikov@amd.com>,
"Geert Uytterhoeven" <geert@linux-m68k.org>,
"Krzysztof Kozlowski" <krzk@kernel.org>,
kernel@pengutronix.de,
"Thierry Reding" <thierry.reding@gmail.com>,
"Christian König" <christian.koenig@amd.com>
Subject: Re: [PATCH 00/17] drm: rename various struct members "dev" -> "drm"
Date: Thu, 13 Jul 2023 16:08:43 +0200 [thread overview]
Message-ID: <4e985e56-ef32-5793-2f63-27804ff4bd65@suse.de> (raw)
In-Reply-To: <20230713131102.rj4s66yui7cvuw54@pengutronix.de>
[-- Attachment #1.1: Type: text/plain, Size: 2277 bytes --]
Hi
Am 13.07.23 um 15:11 schrieb Uwe Kleine-König:
> On Thu, Jul 13, 2023 at 12:41:15PM +0200, Thomas Zimmermann wrote:
>> Hi Uwe
>>
>> Am 13.07.23 um 12:22 schrieb Uwe Kleine-König:
>> [...]
>>>
>>> If that helps you: I plan to tackle these in a followup. I agree that's
>>> ugly, but fixing these in the same series is too much and if we agree
>>> that
>>>
>>> dev = crtc->dev;
>>>
>>> is ugly, there is then an intermediate state that either used
>>>
>>> drm = crtc->dev;
>>>
>>> or
>>>
>>> dev = crtc->drm;
>>>
>>> to finaly reach
>>>
>>> drm = crtc->drm;
>>>
>>> If you see a better way, please let me know. I don't see any.
>>
>> IF this renaming gets accepted, you could make a single patch
>> that adds a union with both names to all affected DRM data structures.
>>
>> struct drm_foo {
>> union {
>> struct drm_device *drm; // use this
>> struct drm_device *dev; // don't use this
>> };
>> }
>>
>> That patch prepares all of DRM for the renaming. And then you can go through
>> drivers one-by-one with a patch or a patchset for each to do all the
>> renaming there. Finally you send another DRM-wide patch to remove that
>> union.
>>
>> That would split the changes into smaller pieces without ugly intermediate
>> state. It also eases the problem for backporters and stable maintainers that
>> have to deal with the name changes.
>>
>> IIRC you already did something similar for remove or probe callbacks?
>
> Did you look at patch #1 of the initial series? That's exactly what I
> did there. People argued to make a single patch and not use an anonymous
> union though ...
I would disagree with them. It also seemed to me that the concern but
splitting up the change into multiple patches was about splitting up a
DRM-wide change into multiple patches. If you'd do per-driver patchsets
that cover all data structures, things might go different. OTOH I'm not
sure if the rename is welcome at all.
Best regards
Thomas
>
> Best regards
> Uwe
>
--
Thomas Zimmermann
Graphics Driver Developer
SUSE Software Solutions Germany GmbH
Frankenstrasse 146, 90461 Nuernberg, Germany
GF: Ivo Totev, Andrew Myers, Andrew McDonald, Boudien Moerman
HRB 36809 (AG Nuernberg)
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 840 bytes --]
next prev parent reply other threads:[~2023-07-13 14:08 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-13 8:23 [PATCH 00/17] drm: rename various struct members "dev" -> "drm" Uwe Kleine-König
2023-07-13 8:23 ` [PATCH 01/17] drm/atomic_state: Rename struct drm_atomic_state::dev to drm Uwe Kleine-König
2023-07-13 8:23 ` [PATCH 02/17] drm/bridge: Rename struct drm_bridge::dev " Uwe Kleine-König
2023-07-13 8:23 ` [PATCH 03/17] drm/client_dev: Rename struct drm_client_dev::dev " Uwe Kleine-König
2023-07-13 8:23 ` [PATCH 04/17] drm/connector: Rename struct drm_connector::dev " Uwe Kleine-König
2023-07-13 8:23 ` [PATCH 05/17] drm/crtc: Rename struct drm_crtc::dev " Uwe Kleine-König
2023-07-13 8:23 ` [PATCH 06/17] drm/debugfs_entry: Rename struct drm_debugfs_entry::dev " Uwe Kleine-König
2023-07-13 8:23 ` [PATCH 07/17] drm/dp_mst_topology_mgr: Rename struct drm_dp_mst_topology_mgr::dev " Uwe Kleine-König
2023-07-13 8:23 ` [PATCH 08/17] drm/encoder: Rename struct drm_encoder::dev " Uwe Kleine-König
2023-07-13 8:24 ` [PATCH 09/17] drm/fb_helper: Rename struct drm_fb_helper::dev " Uwe Kleine-König
2023-07-13 8:24 ` [PATCH 10/17] drm/framebuffer: Rename struct drm_framebuffer::dev " Uwe Kleine-König
2023-07-13 8:24 ` [PATCH 11/17] drm/gem_object: Rename struct drm_gem_object::dev " Uwe Kleine-König
2023-07-13 8:24 ` [PATCH 12/17] drm/master: Rename struct drm_master::dev " Uwe Kleine-König
2023-07-13 8:24 ` [PATCH 13/17] drm/minor: Rename struct drm_minor::dev " Uwe Kleine-König
2023-07-13 8:24 ` [PATCH 14/17] drm/plane: Rename struct drm_plane::dev " Uwe Kleine-König
2023-07-13 8:24 ` [PATCH 15/17] drm/property_blob: Rename struct drm_property_blob::dev " Uwe Kleine-König
2023-07-13 8:24 ` [PATCH 16/17] drm/property: Rename struct drm_property::dev " Uwe Kleine-König
2023-07-13 8:24 ` [PATCH 17/17] drm/vblank_crtc: Rename struct drm_vblank_crtc::dev " Uwe Kleine-König
2023-07-13 9:23 ` [PATCH 00/17] drm: rename various struct members "dev" -> "drm" Jani Nikula
2023-07-13 10:39 ` Uwe Kleine-König
2023-07-13 11:05 ` Jani Nikula
2023-07-13 13:40 ` Paul Kocialkowski
2023-07-13 11:17 ` Maxime Ripard
2023-07-13 14:10 ` Uwe Kleine-König
2023-07-13 14:24 ` Thomas Zimmermann
2023-07-13 14:38 ` Christian König
2023-07-13 15:47 ` Maxime Ripard
2023-07-13 15:59 ` Javier Martinez Canillas
2023-07-14 7:11 ` Uwe Kleine-König
2023-07-13 16:18 ` Jani Nikula
2023-07-14 10:51 ` Paul Kocialkowski
2023-08-02 9:49 ` Jani Nikula
2023-07-13 10:04 ` Thomas Zimmermann
2023-07-13 10:22 ` Uwe Kleine-König
2023-07-13 10:41 ` Thomas Zimmermann
2023-07-13 13:11 ` Uwe Kleine-König
2023-07-13 14:08 ` Thomas Zimmermann [this message]
2023-07-13 11:52 ` Thomas Zimmermann
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=4e985e56-ef32-5793-2f63-27804ff4bd65@suse.de \
--to=tzimmermann@suse.de \
--cc=andrzej.hajda@intel.com \
--cc=christian.koenig@amd.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=geert@linux-m68k.org \
--cc=jani.nikula@intel.com \
--cc=javierm@redhat.com \
--cc=julia.lawall@inria.fr \
--cc=kernel@pengutronix.de \
--cc=krzk@kernel.org \
--cc=linux@armlinux.org.uk \
--cc=luben.tuikov@amd.com \
--cc=mripard@kernel.org \
--cc=paul.kocialkowski@bootlin.com \
--cc=seanpaul@chromium.org \
--cc=suijingfeng@loongson.cn \
--cc=thierry.reding@gmail.com \
--cc=u.kleine-koenig@pengutronix.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox