From: Rosen Penev <rosenp@gmail•com>
To: linux-pm@vger•kernel.org
Cc: Ulf Hansson <ulfh@kernel•org>,
Matthias Brugger <matthias.bgg@gmail•com>,
AngeloGioacchino Del Regno
<angelogioacchino.delregno@collabora•com>,
linux-kernel@vger•kernel.org (open list:ARM/Mediatek SoC support),
linux-arm-kernel@lists•infradead.org (moderated
list:ARM/Mediatek SoC support),
linux-mediatek@lists•infradead.org (moderated list:ARM/Mediatek
SoC support)
Subject: [PATCH] pmdomain: mediatek: mfg: move __packed after struct name to fix kernel-doc
Date: Thu, 28 May 2026 13:24:55 -0700 [thread overview]
Message-ID: <20260528202455.136618-1-rosenp@gmail.com> (raw)
The kernel-doc parser cannot parse 'struct __packed mtk_mfg_opp_entry {'.
Move __packed to the closing brace, which is the more common kernel style.
Assisted-by: Opencode:Big-pickle
Signed-off-by: Rosen Penev <rosenp@gmail•com>
---
drivers/pmdomain/mediatek/mtk-mfg-pmdomain.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/pmdomain/mediatek/mtk-mfg-pmdomain.c b/drivers/pmdomain/mediatek/mtk-mfg-pmdomain.c
index 3ce6fb74dd53..53bdab66cf15 100644
--- a/drivers/pmdomain/mediatek/mtk-mfg-pmdomain.c
+++ b/drivers/pmdomain/mediatek/mtk-mfg-pmdomain.c
@@ -236,14 +236,14 @@ struct __packed mtk_mfg_ipi_sleep_msg {
*
* This struct is part of the ABI with the EB firmware. Do not change it.
*/
-struct __packed mtk_mfg_opp_entry {
+struct mtk_mfg_opp_entry {
__le32 freq_khz;
__le32 voltage_core;
__le32 voltage_sram;
__le32 posdiv;
__le32 voltage_margin;
__le32 power_mw;
-};
+} __packed;
struct mtk_mfg_mbox {
struct mbox_client cl;
--
2.54.0
next reply other threads:[~2026-05-28 20:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-28 20:24 Rosen Penev [this message]
2026-06-03 10:15 ` [PATCH] pmdomain: mediatek: mfg: move __packed after struct name to fix kernel-doc Ulf Hansson
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=20260528202455.136618-1-rosenp@gmail.com \
--to=rosenp@gmail$(echo .)com \
--cc=angelogioacchino.delregno@collabora$(echo .)com \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-mediatek@lists$(echo .)infradead.org \
--cc=linux-pm@vger$(echo .)kernel.org \
--cc=matthias.bgg@gmail$(echo .)com \
--cc=ulfh@kernel$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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