From: Sakari Ailus <sakari.ailus@linux.intel.com>
To: linux-media@vger.kernel.org
Cc: laurent.pinchart@ideasonboard.com,
Tianshu Qiu <tian.shu.qiu@intel.com>,
Bingbu Cao <bingbu.cao@intel.com>,
Tomi Valkeinen <tomi.valkeinen@ideasonboard.com>,
Jacopo Mondi <jacopo+renesas@jmondi.org>
Subject: [PATCH 2/7] media: ccs: Fix driver quirk struct documentation
Date: Fri, 15 Sep 2023 10:28:04 +0300 [thread overview]
Message-ID: <20230915072809.37886-3-sakari.ailus@linux.intel.com> (raw)
In-Reply-To: <20230915072809.37886-1-sakari.ailus@linux.intel.com>
Fix documentation for struct ccs_quirk, a device specific struct for
managing deviations from the standard. The flags field was drifted away
from where it should have been.
Signed-off-by: Sakari Ailus <sakari.ailus@linux.intel.com>
---
drivers/media/i2c/ccs/ccs-quirk.h | 4 +---
1 file changed, 1 insertion(+), 3 deletions(-)
diff --git a/drivers/media/i2c/ccs/ccs-quirk.h b/drivers/media/i2c/ccs/ccs-quirk.h
index 5838fcda92fd..0b1a64958d71 100644
--- a/drivers/media/i2c/ccs/ccs-quirk.h
+++ b/drivers/media/i2c/ccs/ccs-quirk.h
@@ -32,12 +32,10 @@ struct ccs_sensor;
* @reg: Pointer to the register to access
* @value: Register value, set by the caller on write, or
* by the quirk on read
- *
- * @flags: Quirk flags
- *
* @return: 0 on success, -ENOIOCTLCMD if no register
* access may be done by the caller (default read
* value is zero), else negative error code on error
+ * @flags: Quirk flags
*/
struct ccs_quirk {
int (*limits)(struct ccs_sensor *sensor);
--
2.39.2
next prev parent reply other threads:[~2023-09-15 7:28 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-15 7:28 [PATCH 0/7] Small fixes and cleanups (ov2740 and ccs) Sakari Ailus
2023-09-15 7:28 ` [PATCH 1/7] media: Documentation: Align numbered list, make it a proper ReST Sakari Ailus
2023-09-15 9:17 ` Laurent Pinchart
2023-09-15 7:28 ` Sakari Ailus [this message]
2023-09-15 9:18 ` [PATCH 2/7] media: ccs: Fix driver quirk struct documentation Laurent Pinchart
2023-09-15 7:28 ` [PATCH 3/7] media: ccs: Correctly initialise try compose rectangle Sakari Ailus
2023-09-15 9:19 ` Laurent Pinchart
2023-09-15 9:48 ` Sakari Ailus
2023-09-15 7:28 ` [PATCH 4/7] media: ccs: Correct error handling in ccs_register_subdev Sakari Ailus
2023-09-15 9:33 ` Laurent Pinchart
2023-09-15 7:28 ` [PATCH 5/7] media: ov2740: Enable runtime PM before registering the async subdev Sakari Ailus
2023-09-15 9:42 ` Laurent Pinchart
2023-09-15 10:09 ` Sakari Ailus
2023-09-15 11:30 ` Laurent Pinchart
2023-09-15 11:48 ` Sakari Ailus
2023-09-15 12:16 ` Laurent Pinchart
2023-09-15 15:50 ` Sakari Ailus
2023-09-15 16:11 ` Laurent Pinchart
2023-09-15 20:31 ` Sakari Ailus
2023-09-15 20:39 ` Laurent Pinchart
2023-09-15 7:28 ` [PATCH 6/7] media: ov2740: Use sub-device active state Sakari Ailus
2023-09-15 9:48 ` Laurent Pinchart
2023-09-15 9:54 ` Sakari Ailus
2023-09-15 10:13 ` Laurent Pinchart
2023-09-15 10:27 ` Sakari Ailus
2023-09-15 11:31 ` Laurent Pinchart
2023-09-15 11:53 ` Sakari Ailus
2023-09-15 12:08 ` Laurent Pinchart
2023-09-15 7:28 ` [PATCH 7/7] media: ov2740: Return -EPROBE_DEFER if no endpoint is found Sakari Ailus
2023-09-15 9:50 ` Laurent Pinchart
2023-09-15 20:25 ` Sakari Ailus
2023-09-29 12:37 ` Sakari Ailus
2023-09-29 14:25 ` Hans de Goede
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=20230915072809.37886-3-sakari.ailus@linux.intel.com \
--to=sakari.ailus@linux.intel.com \
--cc=bingbu.cao@intel.com \
--cc=jacopo+renesas@jmondi.org \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-media@vger.kernel.org \
--cc=tian.shu.qiu@intel.com \
--cc=tomi.valkeinen@ideasonboard.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