From: Uma Shankar <uma.shankar@intel.com>
To: intel-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org
Cc: jonas@kwiboo.se, seanpaul@chromium.org
Subject: [v2 0/3] Document fixes for DRM UAPI and HDR
Date: Mon, 3 Jun 2019 18:38:47 +0530 [thread overview]
Message-ID: <1559567330-25182-1-git-send-email-uma.shankar@intel.com> (raw)
This series adds DRM UAPI header structure documentation to kernel
docs. Fixes issues with existing structure documentation in drm
uapi header.
This also fixes warnings in HDR doc and addresses suggestions from
Daniel Vetter.
v2: 2 patches from v1 are merged. This series version adds remaining
on top of that. Addressed review comments from Daniel Vetter.
Uma Shankar (3):
drm: ADD UAPI structure definition section in kernel doc
drm: Fix docbook warnings in hdr metadata helper structures
video/hdmi: Dropped static functions from kernel doc
Documentation/gpu/drm-uapi.rst | 9 +++++
drivers/gpu/drm/drm_connector.c | 37 +++++++++++++++++++++
drivers/video/hdmi.c | 30 -----------------
include/drm/drm_connector.h | 1 +
include/drm/drm_mode_config.h | 4 +--
include/linux/hdmi.h | 12 +++++++
include/uapi/drm/drm_mode.h | 74 ++++++++++++++++++++++++++++++++++++++++-
7 files changed, 134 insertions(+), 33 deletions(-)
--
1.9.1
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next reply other threads:[~2019-06-03 13:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-03 13:08 Uma Shankar [this message]
2019-06-03 13:08 ` [v2 1/3] drm: ADD UAPI structure definition section in kernel doc Uma Shankar
2019-06-03 13:08 ` [v2 2/3] drm: Fix docbook warnings in hdr metadata helper structures Uma Shankar
2019-06-03 13:08 ` [v2 3/3] video/hdmi: Dropped static functions from kernel doc Uma Shankar
2019-06-03 13:46 ` ✗ Fi.CI.BAT: failure for Document fixes for DRM UAPI and HDR (rev2) Patchwork
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=1559567330-25182-1-git-send-email-uma.shankar@intel.com \
--to=uma.shankar@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jonas@kwiboo.se \
--cc=seanpaul@chromium.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