From: Dalvin-Ehinoma Noah Aiguobas <pharcodra@gmail.com>
To: gregkh@linuxfoundation.org
Cc: linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: [PATCH] staging: wlan-ng: add comment to spinlock_t
Date: Sun, 2 Apr 2023 17:32:44 +0200 [thread overview]
Message-ID: <20230402153244.GA12609@koolguy> (raw)
Fix checkpatch.pl warning: spinlock_t definition without comment in
drivers/staging/wlan-ng/hfa384x.h
Signed-off-by: Dalvin-Ehinoma Noah Aiguobas <pharcodra@gmail.com>
---
drivers/staging/wlan-ng/hfa384x.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/staging/wlan-ng/hfa384x.h b/drivers/staging/wlan-ng/hfa384x.h
index e33dd1b9c40e..fc6d67cec5b1 100644
--- a/drivers/staging/wlan-ng/hfa384x.h
+++ b/drivers/staging/wlan-ng/hfa384x.h
@@ -1000,7 +1000,7 @@ struct hfa384x_usbctlx {
};
struct hfa384x_usbctlxq {
- spinlock_t lock;
+ spinlock_t lock; /* disable interrupts while working in hfa384 or hfa384x_usbctlx */
struct list_head pending;
struct list_head active;
struct list_head completing;
--
2.25.1
next reply other threads:[~2023-04-02 15:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-02 15:32 Dalvin-Ehinoma Noah Aiguobas [this message]
2023-04-02 15:36 ` [PATCH] staging: wlan-ng: add comment to spinlock_t 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=20230402153244.GA12609@koolguy \
--to=pharcodra@gmail.com \
--cc=gregkh@linuxfoundation.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