From: Amirreza Zarrabi <amirreza.zarrabi@oss.qualcomm.com>
To: "Uwe Kleine-König (The Capable Hub)"
<u.kleine-koenig@baylibre.com>,
"Jens Wiklander" <jens.wiklander@linaro.org>
Cc: Sumit Garg <sumit.garg@kernel.org>,
linux-arm-msm@vger.kernel.org, op-tee@lists.trustedfirmware.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1] tee: qcomtee: Drop unused assignment of platform_device_id driver data
Date: Wed, 24 Jun 2026 13:39:20 +1000 [thread overview]
Message-ID: <6971c4b5-d091-4fe2-b843-60da8b32d48b@oss.qualcomm.com> (raw)
In-Reply-To: <c21803b3f2ea1522bb930dc1dcab79c2627f2234.1781620559.git.u.kleine-koenig@baylibre.com>
Hi,
On 6/17/2026 12:38 AM, Uwe Kleine-König (The Capable Hub) wrote:
> The driver explicitly sets the .driver_data member of struct
> platform_device_id to zero without relying on that value. Drop this
> unused assignment.
>
> While touching this array unify spacing and usage of commas and use
> a named initializer for .name for improved readability.
>
> Signed-off-by: Uwe Kleine-König (The Capable Hub) <u.kleine-koenig@baylibre.com>
> ---
> Hello,
>
> while this is a cleanup that can stand on its own, it is also a
> preparation for a change to struct platform_device_id that requires that
> .driver_data isn't assigned by a list initializer.
>
> Best regards
> Uwe
>
> drivers/tee/qcomtee/call.c | 7 ++++++-
> 1 file changed, 6 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/tee/qcomtee/call.c b/drivers/tee/qcomtee/call.c
> index 0efc5646242a..4a597eeaf174 100644
> --- a/drivers/tee/qcomtee/call.c
> +++ b/drivers/tee/qcomtee/call.c
> @@ -798,7 +798,12 @@ static void qcomtee_remove(struct platform_device *pdev)
> kfree(qcomtee);
> }
>
> -static const struct platform_device_id qcomtee_ids[] = { { "qcomtee", 0 }, {} };
> +static const struct platform_device_id qcomtee_ids[] = {
> + {
> + .name = "qcomtee",
> + },
> + { }
> +};
> MODULE_DEVICE_TABLE(platform, qcomtee_ids);
>
Looks good to me, thanks.
Reviewed-by: Amirreza Zarrabi <amirreza.zarrabi@oss.qualcomm.com>
> static struct platform_driver qcomtee_platform_driver = {
>
> base-commit: 8d6dbbbe3ba62de0a63e962ee004afb848c8e3ac
next prev parent reply other threads:[~2026-06-24 3:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-16 14:38 Uwe Kleine-König (The Capable Hub)
2026-06-24 3:39 ` Amirreza Zarrabi [this message]
2026-06-29 8:52 ` Jens Wiklander
2026-09-16 9:15 ` Jens Wiklander
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=6971c4b5-d091-4fe2-b843-60da8b32d48b@oss.qualcomm.com \
--to=amirreza.zarrabi@oss.qualcomm.com \
--cc=jens.wiklander@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=op-tee@lists.trustedfirmware.org \
--cc=sumit.garg@kernel.org \
--cc=u.kleine-koenig@baylibre.com \
/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®