From: Randy Dunlap <rdunlap@infradead.org>
To: Paul Kocialkowski <paulk@sys-base.io>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Andy Shevchenko <andy.shevchenko@gmail.com>,
Arnd Bergmann <arnd@arndb.de>,
andrew.jones@linux.dev, linux-omap@vger.kernel.org,
openbmc@lists.ozlabs.org, linux-sound@vger.kernel.org,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
linux-mips@vger.kernel.org, asahi@lists.linux.dev,
"dri-devel@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>,
chrome-platform@lists.linux.dev,
Paul Cercueil <paul@crapouillou.net>,
linux-stm32@st-md-mailman.stormreply.com,
Linux ARM <linux-arm-kernel@lists.infradead.org>,
linux-gpio@vger.kernel.org,
Srinivas Kandagatla <srini@kernel.org>,
Philipp Zabel <p.zabel@pengutronix.de>,
Matti Vaittinen <mazziesaccount@gmail.com>,
Jonathan Cameron <jic23@kernel.org>,
Vaibhav Hiremath <hvaibhav.linux@gmail.com>,
linux-sh@vger.kernel.org, x86@kernel.org,
Max Filippov <jcmvbkbc@gmail.com>
Subject: Re: Kconfig dangling references (BZ 216748)
Date: Mon, 8 Dec 2025 10:39:58 -0800 [thread overview]
Message-ID: <873236c8-4dab-4f1e-a2bf-d233ec74bd49@infradead.org> (raw)
In-Reply-To: <aTcVXrUXVsyjaT22@shepard>
On 12/8/25 10:13 AM, Paul Kocialkowski wrote:
> Hi Randy,
>
> On Sun 07 Dec 25, 18:04, Randy Dunlap wrote:
>> from https://bugzilla.kernel.org/show_bug.cgi?id=216748
>>
>> The bugzilla entry includes a Perl script and a shell script.
>> This is the edited result of running them (I removed some entries that were noise).
>
> [...]
>
>> DRM_KMS_DMA_HELPER ---
>> drivers/gpu/drm/adp/Kconfig:9: select DRM_KMS_DMA_HELPER
>> drivers/gpu/drm/logicvc/Kconfig:7: select DRM_KMS_DMA_HELPER
>
> For these two, the symbol was removed in commit
> 09717af7d13d63df141ae6e71686289989d17efd but these two drivers either were
> missed by the batch rename or were introduced a bit later.
>
> Since the symbol selected DRM_GEM_CMA_HELPER (which is still needed by the
> drivers), it should be replaced with DRM_GEM_CMA_HELPER.
>
> Are you expecting to craft a patch for fixing this or should I do it myself?
Hi Paul,
Please take care of it yourself.
Thanks.
--
~Randy
next prev parent reply other threads:[~2025-12-08 18:40 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-08 2:04 Kconfig dangling references (BZ 216748) Randy Dunlap
2025-12-08 8:04 ` Matti Vaittinen
2025-12-08 8:55 ` Arnd Bergmann
2025-12-08 9:48 ` [Linux-stm32] " Antonio Borneo
2025-12-08 9:06 ` Takashi Iwai
2025-12-09 9:36 ` Richard Fitzgerald
2025-12-08 18:13 ` Paul Kocialkowski
2025-12-08 18:39 ` Randy Dunlap [this message]
2025-12-08 20:05 ` Janne Grunau
2025-12-10 22:09 ` Paul Kocialkowski
2025-12-10 13:06 ` Paul Cercueil
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=873236c8-4dab-4f1e-a2bf-d233ec74bd49@infradead.org \
--to=rdunlap@infradead.org \
--cc=alexander.shishkin@linux.intel.com \
--cc=andrew.jones@linux.dev \
--cc=andy.shevchenko@gmail.com \
--cc=arnd@arndb.de \
--cc=asahi@lists.linux.dev \
--cc=chrome-platform@lists.linux.dev \
--cc=dri-devel@lists.freedesktop.org \
--cc=hvaibhav.linux@gmail.com \
--cc=jcmvbkbc@gmail.com \
--cc=jic23@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux-sh@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=mazziesaccount@gmail.com \
--cc=openbmc@lists.ozlabs.org \
--cc=p.zabel@pengutronix.de \
--cc=paul@crapouillou.net \
--cc=paulk@sys-base.io \
--cc=srini@kernel.org \
--cc=x86@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;
as well as URLs for NNTP newsgroup(s).