From: Srinivas Kandagatla <srini@kernel.org>
To: Pengpeng Hou <pengpeng@iscas.ac.cn>,
Srinivas Kandagatla <srini@kernel.org>,
Amol Maheshwari <amahesh@qti.qualcomm.com>,
Arnd Bergmann <arnd@arndb.de>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: linux-arm-msm@vger.kernel.org, dri-devel@lists.freedesktop.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] misc: fastrpc: add missing MODULE_DEVICE_TABLE()
Date: Mon, 6 Jul 2026 10:50:30 +0100 [thread overview]
Message-ID: <6766c138-90cd-4be2-80c1-0f5c144252ef@kernel.org> (raw)
In-Reply-To: <20260705001820.72397-1-pengpeng@iscas.ac.cn>
On 7/5/26 1:18 AM, Pengpeng Hou wrote:
> The driver has a match table for the of bus wired into its driver
> structure, but the table is not exported with MODULE_DEVICE_TABLE().
>
> Add the missing MODULE_DEVICE_TABLE() entry so module alias information
> is generated for automatic module loading.
Are you fixing a real issue?
Is this patch tested?
>
> This is a source-level fix. It does not claim dynamic hardware
> reproduction; the evidence is the driver-owned match table, its use by
> the driver registration structure, and the missing module alias
> publication.
>
> Signed-off-by: Pengpeng Hou <pengpeng@iscas.ac.cn>
> ---
> drivers/misc/fastrpc.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/drivers/misc/fastrpc.c b/drivers/misc/fastrpc.c
> index 47356a5d5804..0d2196b3f632 100644
> --- a/drivers/misc/fastrpc.c
> +++ b/drivers/misc/fastrpc.c
> @@ -2265,6 +2265,7 @@ static const struct of_device_id fastrpc_match_table[] = {
> { .compatible = "qcom,fastrpc-compute-cb", },
> {}
> };
> +MODULE_DEVICE_TABLE(of, fastrpc_match_table);
This is adding dead code, these devices are created dynamically by
fastrpc driver and does not have a standalone driver.
There is already a MODULE_DEVICE_TABLE for this driver.
--srini
>
> static struct platform_driver fastrpc_cb_driver = {
> .probe = fastrpc_cb_probe,
prev parent reply other threads:[~2026-07-06 9:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-05 0:18 Pengpeng Hou
2026-07-06 9:50 ` Srinivas Kandagatla [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=6766c138-90cd-4be2-80c1-0f5c144252ef@kernel.org \
--to=srini@kernel.org \
--cc=amahesh@qti.qualcomm.com \
--cc=arnd@arndb.de \
--cc=dri-devel@lists.freedesktop.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pengpeng@iscas.ac.cn \
/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