From: Ravi Kumar kairi <kumarkairiravi@gmail.com>
To: parthiban.veerasooran@microchip.com,
christian.gromm@microchip.com, gregkh@linuxfoundation.org
Cc: linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org,
Ravi Kumar Kairi <kumarkairiravi@gmail.com>
Subject: [PATCH] staging: most: Remove unused mutex from most_video_dev
Date: Thu, 20 Feb 2025 00:01:51 +0530 [thread overview]
Message-ID: <20250219183152.176679-2-kumarkairiravi@gmail.com> (raw)
In-Reply-To: <20250219183152.176679-1-kumarkairiravi@gmail.com>
From: Ravi Kumar Kairi <kumarkairiravi@gmail.com>
The `lock` field in struct most_video_dev is never used anywhere in
the codebase. Since it serves no purpose, remove it to clean up the
structure.
Signed-off-by: Ravi Kumar Kairi <kumarkairiravi@gmail.com>
---
drivers/staging/most/video/video.c | 2 --
1 file changed, 2 deletions(-)
diff --git a/drivers/staging/most/video/video.c b/drivers/staging/most/video/video.c
index 2b3cdb1ce1..bd51125698 100644
--- a/drivers/staging/most/video/video.c
+++ b/drivers/staging/most/video/video.c
@@ -40,8 +40,6 @@ struct most_video_dev {
struct video_device *vdev;
unsigned int ctrl_input;
- struct mutex lock;
-
wait_queue_head_t wait_data;
};
--
2.48.1
next prev parent reply other threads:[~2025-02-19 18:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-19 18:31 [PATCH] Cleanup of most_video_dev structure Ravi Kumar kairi
2025-02-19 18:31 ` Ravi Kumar kairi [this message]
2025-02-19 18:31 ` [PATCH] staging: most: Remove unused spinlock from most_video_dev Ravi Kumar kairi
-- strict thread matches above, loose matches on Subject: below --
2025-02-21 16:34 [PATCH] Cleanup of most_video_dev structure Ravi Kumar kairi
2025-02-21 16:34 ` [PATCH] staging: most: Remove unused mutex from most_video_dev Ravi Kumar kairi
2025-03-03 7:12 ` kernel test robot
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=20250219183152.176679-2-kumarkairiravi@gmail.com \
--to=kumarkairiravi@gmail.com \
--cc=christian.gromm@microchip.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=parthiban.veerasooran@microchip.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