From: Thomas Zimmermann <tzimmermann@suse.de>
To: Petr Pavlu <petr.pavlu@suse.com>, Sasha Levin <sashal@kernel.org>
Cc: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
Maxime Ripard <mripard@kernel.org>,
David Airlie <airlied@gmail.com>, Simona Vetter <simona@ffwll.ch>,
Luis Chamberlain <mcgrof@kernel.org>,
Daniel Gomez <da.gomez@kernel.org>,
Sami Tolvanen <samitolvanen@google.com>,
Aaron Tomlin <atomlin@atomlin.com>,
dri-devel@lists.freedesktop.org, linux-modules@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] drm/fbdev: Replace __MODULE_STRING() with __stringify()
Date: Tue, 27 Oct 2026 11:29:20 +0100 [thread overview]
Message-ID: <eaaa4b5a-9de9-41ed-a77b-aa2c6531eed6@suse.de> (raw)
In-Reply-To: <3e3b9652-7de5-4391-8b5d-122f00c4b585@suse.com>
Hi
Am 27.10.26 um 10:00 schrieb Petr Pavlu:
> On 10/23/26 10:51 AM, Thomas Zimmermann wrote:
>> Hi
>>
>> Am 22.10.26 um 19:55 schrieb Sasha Levin:
>>> Commit 08abfa5a161e ("drivers: Replace __MODULE_STRING() with
>>> __stringify()") converted the drm_fbdev_overalloc parameter description
>>> in drm_fb_helper.c ahead of the removal of __MODULE_STRING().
>>>
>>> Commit 6b5a66fd9f21 ("drm/fbdev: Move fbdev module parameters next to
>>> module init") moved that parameter into drm_kms_helper_common.c while it
>>> still used __MODULE_STRING(), so the conversion never reached the moved
>>> code. drm_kms_helper_common.c is now the last user of the macro, and
>>> removing the macro breaks the build with CONFIG_DRM_FBDEV_EMULATION=y:
>>>
>>> drivers/gpu/drm/drm_kms_helper_common.c:46:18: error: expected ')' before '__MODULE_STRING'
>>>
>>> Use __stringify() instead. The parameter description is unchanged.
>>>
>>> Signed-off-by: Sasha Levin <sashal@kernel.org>
>> Reviewed-by: Thomas Zimmermann <tzimmermann@suse.de>
>>
>>> ---
>>> This depends on 6b5a66fd9f21 in drm-next and 08abfa5a161e in
>>> modules-next, both queued for 7.4. Petr plans to remove
>>> __MODULE_STRING() once his conversions are in mainline, so this needs to
>>> land first, either through drm-misc after 7.4-rc1 or together with the
>>> removal patch.
>> Dave, could we put this patch directly into drm-next? It seems like this fixes a broken merge commit.
> It looks like Linus took care of this. Merge commit 5b0764a53235 ("Merge
> tag 'drm-next-2026-10-21' of https://gitlab.freedesktop.org/drm/kernel")
> updated drivers/gpu/drm/drm_kms_helper_common.c to use __stringify()
> instead of __MODULE_STRING(). The current mainline has no remaining uses of
> __MODULE_STRING().
Great, thanks for the info. I'll drop this patch then.
Best regards
Thomas
>
--
--
Thomas Zimmermann
Graphics Driver Developer
SUSE Software Solutions Germany GmbH
Frankenstr. 146, 90461 Nürnberg, Germany, www.suse.com
GF: Stefan Gaiser, Jochen Jaser, Abhinav Puri, (HRB 36809, AG Nürnberg)
prev parent reply other threads:[~2026-10-27 10:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-22 17:55 Sasha Levin
2026-10-23 8:51 ` Thomas Zimmermann
2026-10-27 9:00 ` Petr Pavlu
2026-10-27 10:29 ` Thomas Zimmermann [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=eaaa4b5a-9de9-41ed-a77b-aa2c6531eed6@suse.de \
--to=tzimmermann@suse.de \
--cc=airlied@gmail.com \
--cc=atomlin@atomlin.com \
--cc=da.gomez@kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-modules@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mcgrof@kernel.org \
--cc=mripard@kernel.org \
--cc=petr.pavlu@suse.com \
--cc=samitolvanen@google.com \
--cc=sashal@kernel.org \
--cc=simona@ffwll.ch \
/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®