From: Shashank Sharma <shashank.sharma@intel.com>
To: dri-devel@lists.freedesktop.org
Subject: [PATCH v3] drm: Add description for scdc variable
Date: Sat, 25 Mar 2017 11:29:31 +0200 [thread overview]
Message-ID: <1490434171-9870-1-git-send-email-shashank.sharma@intel.com> (raw)
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 doc is specific format
Cc: Daniel Vetter <daniel@ffwll.ch>
Signed-off-by: Shashank Sharma <shashank.sharma@intel.com>
---
include/drm/drm_connector.h | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/include/drm/drm_connector.h b/include/drm/drm_connector.h
index 9fba967..b4fe812 100644
--- a/include/drm/drm_connector.h
+++ b/include/drm/drm_connector.h
@@ -134,7 +134,9 @@ struct drm_scdc {
*/
struct drm_hdmi_info {
- /* @scdc: sink's scdc support and capabilities */
+ /**
+ * @scdc: sink's scdc support and capabilities
+ */
struct drm_scdc scdc;
};
--
2.7.4
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
reply other threads:[~2017-03-25 9:29 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1490434171-9870-1-git-send-email-shashank.sharma@intel.com \
--to=shashank.sharma@intel.com \
--cc=dri-devel@lists.freedesktop.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).