From: "Uwe Kleine-König" <u.kleine-koenig@baylibre.com>
To: MANNURU VENKATESWARLU <v-mannuru@ti.com>
Cc: krzk@kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, n-francis@ti.com, s-k6@ti.com,
bb@ti.com
Subject: Re: [RFC PATCH 06/22] memory: ti-ddrss: Add MR4 temperature-driven refresh rate driver
Date: Tue, 14 Jul 2026 23:29:52 +0200 [thread overview]
Message-ID: <alaojVmBNqua82_t@monoceros> (raw)
In-Reply-To: <20260714125557.3304305-1-v-mannuru@ti.com>
[-- Attachment #1: Type: text/plain, Size: 1079 bytes --]
Hello,
On Tue, Jul 14, 2026 at 06:25:57PM +0530, MANNURU VENKATESWARLU wrote:
> +#include <linux/mfd/ti-ddrss.h>
> +#include <linux/mod_devicetable.h>
Please drop this header. platform_device_id is provided by
<linux/platform_device.h>, so the explicit include isn't needed.
The mod_devicetable.h header will go away soon.
> +#include <linux/module.h>
> +#include <linux/platform_device.h>
> [...]
> +static const struct platform_device_id k3_ddr_mr4_id[] = {
> + { "ti-ddrss-mr4", 0 },
> + {}
> +};
Please make this:
static const struct platform_device_id k3_ddr_mr4_id[] = {
{ .name = "ti-ddrss-mr4" },
{ }
};
> +MODULE_DEVICE_TABLE(platform, k3_ddr_mr4_id);
> +
> +static struct platform_driver k3_ddr_mr4_driver = {
> + .driver = {
> + .name = "ti-ddrss-mr4",
> + .dev_groups = k3_ddr_mr4_groups,
> + },
> + .probe = k3_ddr_mr4_probe,
> + .id_table = k3_ddr_mr4_id,
I'm not a fan of aligned `=`. These tend to diverge over time. And
sometimes they are not even aligned from the start ...
If you ask me, just use a single space before the `=`.
Best regards
Uwe
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
prev parent reply other threads:[~2026-07-14 21:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-14 12:55 [RFC PATCH 06/22] memory: ti-ddrss: Add MR4 temperature-driven refresh rate driver MANNURU VENKATESWARLU
2026-07-14 21:29 ` Uwe Kleine-König [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=alaojVmBNqua82_t@monoceros \
--to=u.kleine-koenig@baylibre.com \
--cc=bb@ti.com \
--cc=krzk@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=n-francis@ti.com \
--cc=s-k6@ti.com \
--cc=v-mannuru@ti.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