From: Jose Abreu <Jose.Abreu@synopsys.com>
To: Hans Verkuil <hverkuil@xs4all.nl>,
Linux Media Mailing List <linux-media@vger.kernel.org>
Cc: Jose Abreu <Jose.Abreu@synopsys.com>
Subject: Re: [PATCH] cec-core.rst: document the new cec_get_drvdata() helper
Date: Mon, 27 Mar 2017 12:26:21 +0100 [thread overview]
Message-ID: <2e7b6c7b-c16a-a3f4-a805-a2df84b20c63@synopsys.com> (raw)
In-Reply-To: <119266d8-95c9-4bcf-114e-a5bfdb4144e3@xs4all.nl>
Hi Hans,
Thanks! I totally forgot about the documentation update.
On 27-03-2017 10:53, Hans Verkuil wrote:
> Document the new cec_get_drvdata() helper function.
>
> Signed-off-by: Hans Verkuil <hans.verkuil@cisco.com>
Reviewed-by: Jose Abreu <joabreu@synopsys.com>
Best regards,
Jose Miguel Abreu
> ---
> diff --git a/Documentation/media/kapi/cec-core.rst b/Documentation/media/kapi/cec-core.rst
> index 81c6d8e93774..8ea3a783f968 100644
> --- a/Documentation/media/kapi/cec-core.rst
> +++ b/Documentation/media/kapi/cec-core.rst
> @@ -51,6 +51,7 @@ ops:
>
> priv:
> will be stored in adap->priv and can be used by the adapter ops.
> + Use cec_get_drvdata(adap) to get the priv pointer.
>
> name:
> the name of the CEC adapter. Note: this name will be copied.
> @@ -65,6 +66,10 @@ available_las:
> the number of simultaneous logical addresses that this
> adapter can handle. Must be 1 <= available_las <= CEC_MAX_LOG_ADDRS.
>
> +To obtain the priv pointer use this helper function:
> +
> +.. c:function::
> + void *cec_get_drvdata(const struct cec_adapter *adap);
>
> To register the /dev/cecX device node and the remote control device (if
> CEC_CAP_RC is set) you call:
prev parent reply other threads:[~2017-03-27 11:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-27 9:53 [PATCH] cec-core.rst: document the new cec_get_drvdata() helper Hans Verkuil
2017-03-27 11:26 ` Jose Abreu [this message]
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=2e7b6c7b-c16a-a3f4-a805-a2df84b20c63@synopsys.com \
--to=jose.abreu@synopsys.com \
--cc=hverkuil@xs4all.nl \
--cc=linux-media@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).