From: Riyan Dhiman <riyandhiman14@gmail.com>
To: gregkh@linuxfoundation.org
Cc: dri-devel@lists.freedesktop.org, linux-fbdev@vger.kernel.org,
linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org,
Riyan Dhiman <riyandhiman14@gmail.com>
Subject: [PATCH] staging: vme_user: vme_bridge.h: Fix mutex without comment warning
Date: Wed, 31 Jul 2024 13:06:05 +0530 [thread overview]
Message-ID: <20240731073605.9857-1-riyandhiman14@gmail.com> (raw)
Adhere to Linux kernel coding style
Reported by checkpatch:
CHECK: mutex definition without comment
Signed-off-by: Riyan Dhiman <riyandhiman14@gmail.com>
---
drivers/staging/vme_user/vme_bridge.h | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/drivers/staging/vme_user/vme_bridge.h b/drivers/staging/vme_user/vme_bridge.h
index 9bdc41bb6602..0b1f05944f0d 100644
--- a/drivers/staging/vme_user/vme_bridge.h
+++ b/drivers/staging/vme_user/vme_bridge.h
@@ -28,6 +28,7 @@ struct vme_master_resource {
struct vme_slave_resource {
struct list_head list;
struct vme_bridge *parent;
+ /* Locking for VME slave resources */
struct mutex mtx;
int locked;
int number;
@@ -55,12 +56,14 @@ struct vme_dma_list {
struct list_head list;
struct vme_dma_resource *parent;
struct list_head entries;
+ /* Mutex to protect access to DMA list's entries */
struct mutex mtx;
};
struct vme_dma_resource {
struct list_head list;
struct vme_bridge *parent;
+ /* Mutex to protect DMA controller resources and ensure thread-safe operations */
struct mutex mtx;
int locked;
int number;
@@ -72,6 +75,7 @@ struct vme_dma_resource {
struct vme_lm_resource {
struct list_head list;
struct vme_bridge *parent;
+ /* Mutex to protect LM Monitor resources and ensure thread-safe operations */
struct mutex mtx;
int locked;
int number;
--
2.39.2
next reply other threads:[~2024-07-31 7:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-31 7:36 Riyan Dhiman [this message]
2024-07-31 7:44 ` [PATCH] staging: vme_user: vme_bridge.h: Fix mutex without comment warning Greg KH
[not found] ` <CAAjz0Qahd96tQEpbWPXiGQ7Frku3sXpKQ6BfTWzqxcf4ApSYEA@mail.gmail.com>
2024-07-31 8:38 ` Greg KH
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=20240731073605.9857-1-riyandhiman14@gmail.com \
--to=riyandhiman14@gmail.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
/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