From: Daniel Vetter <daniel@ffwll.ch>
To: Shashank Sharma <shashank.sharma@intel.com>
Cc: dri-devel@lists.freedesktop.org
Subject: Re: [PATCH v6] drm: Add description for scdc variable
Date: Tue, 28 Mar 2017 09:58:38 +0200 [thread overview]
Message-ID: <20170328075838.jwrddhjjptczskmk@phenom.ffwll.local> (raw)
In-Reply-To: <1490684779-21633-1-git-send-email-shashank.sharma@intel.com>
On Tue, Mar 28, 2017 at 10:06:19AM +0300, Shashank Sharma 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'"
>
> V2: Rebase
> V3: Added extra *
> V4: Removed merged conflict
> V5: Removed extra line at start of structure (Daniel)
> V6: Make description single line (Daniel)
>
> Cc: Daniel Vetter <daniel@ffwll.ch>
> Signed-off-by: Shashank Sharma <shashank.sharma@intel.com>
Applied, thx.
-Daniel
> ---
> include/drm/drm_connector.h | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/include/drm/drm_connector.h b/include/drm/drm_connector.h
> index f8b766d..6d3f7ba 100644
> --- a/include/drm/drm_connector.h
> +++ b/include/drm/drm_connector.h
> @@ -133,6 +133,7 @@ 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;
> };
>
> --
> 2.7.4
>
--
Daniel Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
prev parent reply other threads:[~2017-03-28 7:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-28 7:06 [PATCH v6] drm: Add description for scdc variable Shashank Sharma
2017-03-28 7:58 ` Daniel Vetter [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=20170328075838.jwrddhjjptczskmk@phenom.ffwll.local \
--to=daniel@ffwll.ch \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.