From: Tzung-Bi Shih <tzungbi@kernel.org>
To: "Gustavo A. R. Silva" <gustavoars@kernel.org>
Cc: Alexandre Belloni <alexandre.belloni@bootlin.com>,
Benson Leung <bleung@chromium.org>,
Guenter Roeck <groeck@chromium.org>,
linux-rtc@vger.kernel.org, chrome-platform@lists.linux.dev,
linux-kernel@vger.kernel.org, linux-hardening@vger.kernel.org
Subject: Re: [PATCH][next] rtc: Avoid a couple of -Wflex-array-member-not-at-end warnings
Date: Fri, 14 Mar 2025 08:17:15 +0000 [thread overview]
Message-ID: <Z9PmC4lExxDMusf3@google.com> (raw)
In-Reply-To: <Z9N8BsVJF-s6Hcvd@kspp>
On Fri, Mar 14, 2025 at 11:14:54AM +1030, Gustavo A. R. Silva wrote:
> static int cros_ec_rtc_get(struct cros_ec_device *cros_ec, u32 command,
> u32 *response)
> {
> + DEFINE_RAW_FLEX(struct cros_ec_command, msg, data,
> + sizeof(struct ec_response_rtc));
> int ret;
> - struct {
> - struct cros_ec_command msg;
> - struct ec_response_rtc data;
> - } __packed msg;
>
> - memset(&msg, 0, sizeof(msg));
> - msg.msg.command = command;
> - msg.msg.insize = sizeof(msg.data);
> + msg->command = command;
> + msg->insize = sizeof(struct ec_response_rtc);
>
> - ret = cros_ec_cmd_xfer_status(cros_ec, &msg.msg);
> + ret = cros_ec_cmd_xfer_status(cros_ec, msg);
> if (ret < 0)
> return ret;
>
> - *response = msg.data.time;
> + memcpy(response, msg->data, sizeof(*response));
Technically they are the same as `struct ec_response_rtc` only has an
u32 member. Any reason to not translate it something similar to:
*response = ((struct ec_response_rtc *)msg->data)->time;
>
> return 0;
> }
> @@ -57,18 +54,15 @@ static int cros_ec_rtc_get(struct cros_ec_device *cros_ec, u32 command,
> static int cros_ec_rtc_set(struct cros_ec_device *cros_ec, u32 command,
> u32 param)
> {
> + DEFINE_RAW_FLEX(struct cros_ec_command, msg, data,
> + sizeof(struct ec_response_rtc));
> int ret;
> - struct {
> - struct cros_ec_command msg;
> - struct ec_response_rtc data;
> - } __packed msg;
>
> - memset(&msg, 0, sizeof(msg));
> - msg.msg.command = command;
> - msg.msg.outsize = sizeof(msg.data);
> - msg.data.time = param;
> + msg->command = command;
> + msg->outsize = sizeof(struct ec_response_rtc);
> + memcpy(msg->data, ¶m, sizeof(param));
Same here, how about:
((struct ec_response_rtc *)msg->data)->time = param;
next prev parent reply other threads:[~2025-03-14 8:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-14 0:44 [PATCH][next] rtc: Avoid a couple of -Wflex-array-member-not-at-end warnings Gustavo A. R. Silva
2025-03-14 8:17 ` Tzung-Bi Shih [this message]
2025-03-14 8:33 ` Gustavo A. R. Silva
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=Z9PmC4lExxDMusf3@google.com \
--to=tzungbi@kernel.org \
--cc=alexandre.belloni@bootlin.com \
--cc=bleung@chromium.org \
--cc=chrome-platform@lists.linux.dev \
--cc=groeck@chromium.org \
--cc=gustavoars@kernel.org \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rtc@vger.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.