From: Sakari Ailus <sakari.ailus@linux.intel.com>
To: linux-media@vger.kernel.org
Cc: linux-leds@vger.kernel.org, jacek.anaszewski@gmail.com,
laurent.pinchart@ideasonboard.com,
Johan Hovold <johan@kernel.org>, Alex Elder <elder@kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
greybus-dev@lists.linaro.org, devel@driverdev.osuosl.org,
viresh.kumar@linaro.org, Rui Miguel Silva <rmfrfs@gmail.com>
Subject: [PATCH v2 3/3] v4l2-flash-led-class: Document v4l2_flash_init() references
Date: Wed, 9 Aug 2017 14:15:55 +0300 [thread overview]
Message-ID: <20170809111555.30147-4-sakari.ailus@linux.intel.com> (raw)
In-Reply-To: <20170809111555.30147-1-sakari.ailus@linux.intel.com>
The v4l2_flash_init() keeps a reference to the ops struct but not to the
config struct (nor anything it contains). Document this.
Signed-off-by: Sakari Ailus <sakari.ailus@linux.intel.com>
Acked-by: Pavel Machek <pavel@ucw.cz>
---
include/media/v4l2-flash-led-class.h | 6 ++++++
1 file changed, 6 insertions(+)
diff --git a/include/media/v4l2-flash-led-class.h b/include/media/v4l2-flash-led-class.h
index c3f39992f3fa..6f4825b6a352 100644
--- a/include/media/v4l2-flash-led-class.h
+++ b/include/media/v4l2-flash-led-class.h
@@ -112,6 +112,9 @@ static inline struct v4l2_flash *v4l2_ctrl_to_v4l2_flash(struct v4l2_ctrl *c)
* @config: initialization data for V4L2 Flash sub-device
*
* Create V4L2 Flash sub-device wrapping given LED subsystem device.
+ * The ops pointer is stored by the V4L2 flash framework. No
+ * references are held to config nor its contents once this function
+ * has returned.
*
* Returns: A valid pointer, or, when an error occurs, the return
* value is encoded using ERR_PTR(). Use IS_ERR() to check and
@@ -130,6 +133,9 @@ struct v4l2_flash *v4l2_flash_init(
* @config: initialization data for V4L2 Flash sub-device
*
* Create V4L2 Flash sub-device wrapping given LED subsystem device.
+ * The ops pointer is stored by the V4L2 flash framework. No
+ * references are held to config nor its contents once this function
+ * has returned.
*
* Returns: A valid pointer, or, when an error occurs, the return
* value is encoded using ERR_PTR(). Use IS_ERR() to check and
--
2.11.0
next prev parent reply other threads:[~2017-08-09 11:15 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-09 11:15 [PATCH v2 0/3] Create sub-device per LED Sakari Ailus
2017-08-09 11:15 ` [PATCH v2 1/3] staging: greybus: light: fix memory leak in v4l2 register Sakari Ailus
2017-08-09 13:20 ` Rui Miguel Silva
2017-08-09 15:36 ` Sakari Ailus
2017-08-09 16:06 ` Rui Miguel Silva
2017-08-10 13:02 ` Hans Verkuil
2017-08-10 13:09 ` Hans Verkuil
2017-08-10 13:56 ` Sakari Ailus
2017-08-10 14:43 ` Rui Miguel Silva
2017-08-09 11:15 ` [PATCH v2 2/3] v4l2-flash-led-class: Create separate sub-devices for indicators Sakari Ailus
2017-08-09 16:09 ` Rui Miguel Silva
2017-08-10 13:18 ` Hans Verkuil
2017-08-09 11:15 ` Sakari Ailus [this message]
2017-08-10 13:16 ` [PATCH v2 3/3] v4l2-flash-led-class: Document v4l2_flash_init() references Hans Verkuil
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=20170809111555.30147-4-sakari.ailus@linux.intel.com \
--to=sakari.ailus@linux.intel.com \
--cc=devel@driverdev.osuosl.org \
--cc=elder@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=greybus-dev@lists.linaro.org \
--cc=jacek.anaszewski@gmail.com \
--cc=johan@kernel.org \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-leds@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=rmfrfs@gmail.com \
--cc=viresh.kumar@linaro.org \
/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