mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Joshua Crofts via B4 Relay <devnull+joshua.crofts1.gmail.com@kernel.org>
To: "Jonathan Cameron" <jic23@kernel.org>,
	"David Lechner" <dlechner@baylibre.com>,
	"Nuno Sá" <nuno.sa@analog.com>,
	"Andy Shevchenko" <andy@kernel.org>,
	"Alexander Koch" <mail@alexanderkoch.net>,
	"Michael Hornung" <mhornung.linux@gmail.com>
Cc: linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org,
	 Joshua Crofts <joshua.crofts1@gmail.com>,
	 Maxwell Doose <m32285159@gmail.com>
Subject: [PATCH v3 7/7] iio: light: opt3001: add comment to mutex
Date: Thu, 21 May 2026 11:55:44 +0200	[thread overview]
Message-ID: <20260521-opt3001-cleanup-v3-7-820169dec8c3@gmail.com> (raw)
In-Reply-To: <20260521-opt3001-cleanup-v3-0-820169dec8c3@gmail.com>

From: Joshua Crofts <joshua.crofts1@gmail.com>

Add comment to mutex per checkpatch.pl report.

No functional change.

Reviewed-by: Maxwell Doose <m32285159@gmail.com>
Signed-off-by: Joshua Crofts <joshua.crofts1@gmail.com>
---
 drivers/iio/light/opt3001.c | 1 +
 1 file changed, 1 insertion(+)

diff --git a/drivers/iio/light/opt3001.c b/drivers/iio/light/opt3001.c
index ac1c7ba5679867f6b814894680e317615f2e373b..9d24d7a23ef00d160fdae737b6ea1943576a3fcf 100644
--- a/drivers/iio/light/opt3001.c
+++ b/drivers/iio/light/opt3001.c
@@ -103,6 +103,7 @@ struct opt3001_chip_info {
 struct opt3001 {
 	struct i2c_client	*client;
 
+	/* Mutex for ensuring one executed command at a time */
 	struct mutex		lock;
 	bool			ok_to_ignore_lock;
 	bool			result_ready;

-- 
2.47.3



  parent reply	other threads:[~2026-05-21  9:55 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-21  9:55 [PATCH v3 0/7] iio: light: opt3001: driver cleanup Joshua Crofts via B4 Relay
2026-05-21  9:55 ` [PATCH v3 1/7] iio: light: opt3001: move device registration to end of probe() Joshua Crofts via B4 Relay
2026-05-21 10:43   ` Joshua Crofts
2026-05-22 14:03   ` Jonathan Cameron
2026-05-21  9:55 ` [PATCH v3 2/7] iio: light: opt3001: use local struct device and i2c_client variables Joshua Crofts via B4 Relay
2026-05-21  9:55 ` [PATCH v3 3/7] iio: light: opt3001: ensure correct parenthesis alignment Joshua Crofts via B4 Relay
2026-05-22  6:52   ` Maxwell Doose
2026-05-21  9:55 ` [PATCH v3 4/7] iio: light: opt3001: localize for loop iterator Joshua Crofts via B4 Relay
2026-05-21  9:55 ` [PATCH v3 5/7] iio: light: opt3001: prefer dev_err_probe() Joshua Crofts via B4 Relay
2026-05-22  1:48   ` Maxwell Doose
2026-05-22  5:06     ` Joshua Crofts
2026-05-22  5:19       ` Maxwell Doose
2026-05-22 14:07         ` Jonathan Cameron
2026-05-21  9:55 ` [PATCH v3 6/7] iio: light: opt3001: move driver to guard(mutex)() use Joshua Crofts via B4 Relay
2026-05-21 11:35   ` Joshua Crofts
2026-05-21  9:55 ` Joshua Crofts via B4 Relay [this message]
2026-05-22 14:12   ` [PATCH v3 7/7] iio: light: opt3001: add comment to mutex Jonathan Cameron
2026-05-22 14:25     ` Joshua Crofts

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=20260521-opt3001-cleanup-v3-7-820169dec8c3@gmail.com \
    --to=devnull+joshua.crofts1.gmail.com@kernel.org \
    --cc=andy@kernel.org \
    --cc=dlechner@baylibre.com \
    --cc=jic23@kernel.org \
    --cc=joshua.crofts1@gmail.com \
    --cc=linux-iio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=m32285159@gmail.com \
    --cc=mail@alexanderkoch.net \
    --cc=mhornung.linux@gmail.com \
    --cc=nuno.sa@analog.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®