From: Vincent Mailhol <mailhol.vincent@wanadoo.fr>
To: Ming Yu <a0282524688@gmail.com>
Cc: linux-kernel@vger.kernel.org, linux-gpio@vger.kernel.org,
linux-i2c@vger.kernel.org, linux-can@vger.kernel.org,
netdev@vger.kernel.org, linux-watchdog@vger.kernel.org,
linux-hwmon@vger.kernel.org, linux-rtc@vger.kernel.org,
linux-usb@vger.kernel.org, tmyu0@nuvoton.com, lee@kernel.org,
linus.walleij@linaro.org, brgl@bgdev.pl, andi.shyti@kernel.org,
mkl@pengutronix.de, andrew+netdev@lunn.ch, davem@davemloft.net,
edumazet@google.com, kuba@kernel.org, pabeni@redhat.com,
wim@linux-watchdog.org, linux@roeck-us.net, jdelvare@suse.com,
alexandre.belloni@bootlin.com
Subject: Re: [PATCH v6 4/7] can: Add Nuvoton NCT6694 CANFD support
Date: Thu, 6 Feb 2025 20:05:26 +0900 [thread overview]
Message-ID: <c255fe16-da67-42ff-86f3-89c1ac683c60@wanadoo.fr> (raw)
In-Reply-To: <CAOoeyxWivAZmZPe92+_LrL-HvMn7Lqs7M4B__JULKqHeJMTioA@mail.gmail.com>
On 04/02/2025 at 12:24, Ming Yu wrote:
> Dear Vincent,
>
> Thank you for reviewing,
> I will address the issues you mentioned in the next patch.
>
> Vincent Mailhol <mailhol.vincent@wanadoo.fr> 於 2025年1月26日 週日 下午4:47寫道:
>>
> ...
>>> +static int nct6694_can_get_clock(struct nct6694_can_priv *priv)
>>> +{
>>> + struct nct6694_can_information *info;
>>> + struct nct6694_cmd_header cmd_hd = {
>>
>> If the variable only has constant initializer, make it static const:
>>
>> static const struct nct6694_cmd_header cmd_hd = {
>>
>> Apply this at other locations in your different modules.
>>
>>> + .mod = NCT6694_CAN_MOD,
>>> + .cmd = NCT6694_CAN_INFORMATION,
>>> + .sel = NCT6694_CAN_INFORMATION_SEL,
>>> + .len = cpu_to_le16(sizeof(*info))
>>> + };
>>> + int ret, can_clk;
>>> +
>>> + info = kzalloc(sizeof(*info), GFP_KERNEL);
>>> + if (!info)
>>> + return -ENOMEM;
>>> +
>
> Excuse me, I would like to confirm, if the variable is constant
> initializer, should the declaration be written as:
> static const struct nct6694_cmd_header cmd_hd = {
> .mod = NCT6694_CAN_MOD,
> .cmd = NCT6694_CAN_INFORMATION,
> .sel = NCT6694_CAN_INFORMATION_SEL,
> .len = cpu_to_le16(sizeof(struct nct6694_can_information))
> };
> instead of:
> static const struct nct6694_cmd_header cmd_hd = {
> .mod = NCT6694_CAN_MOD,
> .cmd = NCT6694_CAN_INFORMATION,
> .sel = NCT6694_CAN_INFORMATION_SEL,
> .len = cpu_to_le16(sizeof(*info))
> };
> , correct?
The sizeof() keyword returns a integer constant expression even if
applied on to a variable (unless that variable is a variable length
array, but these are banned in the kernel anyway). This is because only
the type of the variable matters, and that is known at compile time.
So, cpu_to_le16(sizeof(*info)) should work fine. Or are you getting any
error?
> In addition, does this mean that the parameter in nct6694_read_msg()
> and nct6694_write_msg() should be changed to const struct
> nct6694_cmd_header *cmd_hd?
Yes!
Yours sincerely,
Vincent Mailhol
next prev parent reply other threads:[~2025-02-06 11:05 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-23 9:11 [PATCH v6 0/7] Add Nuvoton NCT6694 MFD drivers Ming Yu
2025-01-23 9:11 ` [PATCH v6 1/7] mfd: Add core driver for Nuvoton NCT6694 Ming Yu
2025-01-23 9:11 ` [PATCH v6 2/7] gpio: Add Nuvoton NCT6694 GPIO support Ming Yu
2025-01-23 9:11 ` [PATCH v6 3/7] i2c: Add Nuvoton NCT6694 I2C support Ming Yu
2025-01-23 9:11 ` [PATCH v6 4/7] can: Add Nuvoton NCT6694 CANFD support Ming Yu
2025-01-23 11:09 ` Simon Horman
2025-02-04 2:55 ` Ming Yu
2025-01-26 8:47 ` Vincent Mailhol
2025-02-04 3:24 ` Ming Yu
2025-02-06 11:05 ` Vincent Mailhol [this message]
2025-01-23 9:11 ` [PATCH v6 5/7] watchdog: Add Nuvoton NCT6694 WDT support Ming Yu
2025-01-26 10:13 ` Vincent Mailhol
2025-02-04 2:44 ` Ming Yu
2025-01-23 9:11 ` [PATCH v6 6/7] hwmon: Add Nuvoton NCT6694 HWMON support Ming Yu
2025-01-26 7:42 ` Vincent Mailhol
2025-01-26 13:18 ` Guenter Roeck
2025-02-04 2:52 ` Ming Yu
2025-01-23 9:11 ` [PATCH v6 7/7] rtc: Add Nuvoton NCT6694 RTC support Ming Yu
2025-02-05 10:23 ` Alexandre Belloni
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=c255fe16-da67-42ff-86f3-89c1ac683c60@wanadoo.fr \
--to=mailhol.vincent@wanadoo.fr \
--cc=a0282524688@gmail.com \
--cc=alexandre.belloni@bootlin.com \
--cc=andi.shyti@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=brgl@bgdev.pl \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=jdelvare@suse.com \
--cc=kuba@kernel.org \
--cc=lee@kernel.org \
--cc=linus.walleij@linaro.org \
--cc=linux-can@vger.kernel.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-hwmon@vger.kernel.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rtc@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=linux-watchdog@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=mkl@pengutronix.de \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=tmyu0@nuvoton.com \
--cc=wim@linux-watchdog.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).