* [PATCH] staging: vme_user: vme_bridge.h: Fix mutex without comment warning
@ 2024-07-31 7:36 Riyan Dhiman
2024-07-31 7:44 ` Greg KH
0 siblings, 1 reply; 3+ messages in thread
From: Riyan Dhiman @ 2024-07-31 7:36 UTC (permalink / raw)
To: gregkh; +Cc: dri-devel, linux-fbdev, linux-staging, linux-kernel, Riyan Dhiman
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
^ permalink raw reply related [flat|nested] 3+ messages in thread
* Re: [PATCH] staging: vme_user: vme_bridge.h: Fix mutex without comment warning
2024-07-31 7:36 [PATCH] staging: vme_user: vme_bridge.h: Fix mutex without comment warning Riyan Dhiman
@ 2024-07-31 7:44 ` Greg KH
[not found] ` <CAAjz0Qahd96tQEpbWPXiGQ7Frku3sXpKQ6BfTWzqxcf4ApSYEA@mail.gmail.com>
0 siblings, 1 reply; 3+ messages in thread
From: Greg KH @ 2024-07-31 7:44 UTC (permalink / raw)
To: Riyan Dhiman; +Cc: dri-devel, linux-fbdev, linux-staging, linux-kernel
On Wed, Jul 31, 2024 at 01:06:05PM +0530, Riyan Dhiman wrote:
> 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 */
Are you sure about all of these? Please document them individually and
put the proof of that in the changelog text.
thanks,
greg k-h
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [PATCH] staging: vme_user: vme_bridge.h: Fix mutex without comment warning
[not found] ` <CAAjz0Qahd96tQEpbWPXiGQ7Frku3sXpKQ6BfTWzqxcf4ApSYEA@mail.gmail.com>
@ 2024-07-31 8:38 ` Greg KH
0 siblings, 0 replies; 3+ messages in thread
From: Greg KH @ 2024-07-31 8:38 UTC (permalink / raw)
To: Riyan Dhiman; +Cc: dri-devel, linux-fbdev, linux-staging, linux-kernel
A: http://en.wikipedia.org/wiki/Top_post
Q: Were do I find info about this thing called top-posting?
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?
A: No.
Q: Should I include quotations after my reply?
http://daringfireball.net/2007/07/on_top
On Wed, Jul 31, 2024 at 01:34:56PM +0530, Riyan Dhiman wrote:
> Hello,
>
> Thank you for reviewing my patch. I received your feedback:
> > Are you sure about all of these? Please document them individually and
> > put the proof of that in the changelog text.
>
> I'd like to clarify a few points to ensure I address your concerns
> correctly:
>
> 1. By "document them individually", do you mean I should submit
> separate patches for each mutex documentation change?
Yes.
> 2. Regarding the "proof" for the changelog text, could you please elaborate
> on what kind of proof you 're looking for? Should I include:
> - References to the code where these mutexes are used?
> - Explanations of the race conditions these mutexes prevent?
> - Citations from the driver's design documentation (if available)?
Whatever you feel would be needed to convince everyone that the comment
is now correct.
> 3. Is there a preferred format or level of detail you'd like to see in the
> changelog for each documentation change?
What would you want to see if you had to review this type of change to
be comfortable accepting it?
thanks,
greg k-h
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2024-07-31 8:38 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2024-07-31 7:36 [PATCH] staging: vme_user: vme_bridge.h: Fix mutex without comment warning Riyan Dhiman
2024-07-31 7:44 ` Greg KH
[not found] ` <CAAjz0Qahd96tQEpbWPXiGQ7Frku3sXpKQ6BfTWzqxcf4ApSYEA@mail.gmail.com>
2024-07-31 8:38 ` Greg KH
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).