From: Jani Nikula <jani.nikula@linux.intel.com>
To: Shashank Sharma <shashank.sharma@intel.com>,
dri-devel@lists.freedesktop.org
Subject: Re: [PATCH] drm: Add description for scdc variable
Date: Mon, 27 Mar 2017 22:03:53 +0300 [thread overview]
Message-ID: <87d1d28rty.fsf@intel.com> (raw)
In-Reply-To: <87fuhy8rv8.fsf@intel.com>
On Mon, 27 Mar 2017, Jani Nikula <jani.nikula@linux.intel.com> wrote:
> On Sat, 25 Mar 2017, Shashank Sharma <shashank.sharma@intel.com> wrote:
>> This patch adds description about 'scdc' variable in drm_hdmi_info
>> structure, to fix this warning during doc-build.
>>
>> "drm_connector.h:140: warning: No description found for parameter 'scdc'"
>
> Did you actually run 'make htmldocs' with this? The opening marker for
> kernel-doc comments is "/**".
Nevermind, I'm just lagging in my email...
>
> BR,
> Jani.
>
>>
>> Cc: Daniel Vetter <daniel@ffwll.ch>
>> Signed-off-by: Shashank Sharma <shashank.sharma@intel.com>
>> ---
>> include/drm/drm_connector.h | 2 ++
>> 1 file changed, 2 insertions(+)
>>
>> diff --git a/include/drm/drm_connector.h b/include/drm/drm_connector.h
>> index 0fcea02..eafda3e 100644
>> --- a/include/drm/drm_connector.h
>> +++ b/include/drm/drm_connector.h
>> @@ -133,6 +133,8 @@ struct drm_scdc {
>> * This information is available in CEA-861-F extension blocks (like HF-VSDB).
>> */
>> struct drm_hdmi_info {
>> +
>> + /* @scdc: sink's scdc support and capabilities */
>> struct drm_scdc scdc;
>> u8 ycbcr420_dc_modes;
>> u64 ycbcr420_vcb_map;
--
Jani Nikula, Intel Open Source Technology Center
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
prev parent reply other threads:[~2017-03-27 19:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-25 9:10 [PATCH] drm: Add description for scdc variable Shashank Sharma
2017-03-27 19:03 ` Jani Nikula
2017-03-27 19:03 ` Jani Nikula [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=87d1d28rty.fsf@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=shashank.sharma@intel.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;
as well as URLs for NNTP newsgroup(s).