From: Cristian Marussi <cristian.marussi@arm.com>
To: linux-kernel@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Cc: sudeep.holla@arm.com, cristian.marussi@arm.com
Subject: [PATCH 3/4] firmware: arm_scmi: Fix scmi_event_header fields typing
Date: Wed, 8 Jul 2020 13:22:47 +0100 [thread overview]
Message-ID: <20200708122248.52771-3-cristian.marussi@arm.com> (raw)
In-Reply-To: <20200708122248.52771-1-cristian.marussi@arm.com>
Drop size_t in favour of fixed size u32 for consistency and shuffle
around fields definitions to minimize implicit padding.
Signed-off-by: Cristian Marussi <cristian.marussi@arm.com>
---
drivers/firmware/arm_scmi/notify.c | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/drivers/firmware/arm_scmi/notify.c b/drivers/firmware/arm_scmi/notify.c
index 752415367305..f441da28d91f 100644
--- a/drivers/firmware/arm_scmi/notify.c
+++ b/drivers/firmware/arm_scmi/notify.c
@@ -254,10 +254,10 @@ struct events_queue {
* queueing it on the related &struct events_queue.
*/
struct scmi_event_header {
- u64 timestamp;
- u8 evt_id;
- size_t payld_sz;
- u8 payld[];
+ u64 timestamp;
+ u32 payld_sz;
+ u8 evt_id;
+ u8 payld[];
};
struct scmi_registered_event;
--
2.17.1
next prev parent reply other threads:[~2020-07-08 12:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-08 12:22 [PATCH 1/4] firmware: arm_scmi: Remove zero-length array in SCMI Notifications Cristian Marussi
2020-07-08 12:22 ` [PATCH 2/4] firmware: arm_scmi: Remove unneeded __packed attribute Cristian Marussi
2020-07-08 12:22 ` Cristian Marussi [this message]
2020-07-08 20:38 ` [PATCH 3/4] firmware: arm_scmi: Fix scmi_event_header fields typing Arnd Bergmann
2020-07-09 8:24 ` Cristian Marussi
2020-07-08 12:22 ` [PATCH 4/4] firmware: arm_scmi: Remove fixed size typing from event reports Cristian Marussi
2020-07-08 20:39 ` Arnd Bergmann
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=20200708122248.52771-3-cristian.marussi@arm.com \
--to=cristian.marussi@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sudeep.holla@arm.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;
as well as URLs for NNTP newsgroup(s).