From: Artem Shimko <artyom.shimko@gmail.com>
To: Sudeep Holla <sudeep.holla@arm.com>,
Cristian Marussi <cristian.marussi@arm.com>
Cc: Artem Shimko <artyom.shimko@gmail.com>,
arm-scmi@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: [PATCH 0/2] firmware: arm_scmi: Minor cleanups and documentation fixes
Date: Mon, 1 Sep 2025 19:12:02 +0300 [thread overview]
Message-ID: <20250901161207.2501078-1-artyom.shimko@gmail.com> (raw)
In-Reply-To: <y>
Hello maintainers,
This small patch series addresses some minor issues found in the SCMI driver:
Patch 1 fixes alignment and indentation inconsistencies in two files:
Adjusts function parameter alignment in protocol_id_show()
Fixes debugfs call alignment in raw_mode.c for better readability
Patch 2 adds missing documentation for the xfer_lock spinlock that protects
access to xfer buffers and transfer allocation mechanism, making the code
more maintainable and easier to understand.
These are straightforward cleanups that don't change any functionality but
improve code quality and documentation.
Best regards,
Artem Shimko
Artem Shimko (2):
firmware: arm_scmi: fix alignment in protocol_id_show and debugfs calls
firmware: arm_scmi: add missing spinlock documentation
drivers/firmware/arm_scmi/bus.c | 2 +-
drivers/firmware/arm_scmi/driver.c | 1 +
drivers/firmware/arm_scmi/raw_mode.c | 4 ++--
3 files changed, 4 insertions(+), 3 deletions(-)
--
2.43.0
next reply other threads:[~2025-09-01 16:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-01 16:12 Artem Shimko [this message]
2025-09-01 16:12 ` [PATCH 1/2] firmware: arm_scmi: fix alignment in protocol_id_show and debugfs calls Artem Shimko
2025-09-01 16:12 ` [PATCH 2/2] firmware: arm_scmi: add missing spinlock documentation Artem Shimko
2025-09-02 9:27 ` Sudeep Holla
2025-09-05 23:44 ` Artem Shimko
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=20250901161207.2501078-1-artyom.shimko@gmail.com \
--to=artyom.shimko@gmail.com \
--cc=arm-scmi@vger.kernel.org \
--cc=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
all inboxes | Powered by JetHome®