From: Jani Nikula <jani.nikula@intel.com>
To: Mika Kahola <mika.kahola@intel.com>, dri-devel@lists.freedesktop.org
Cc: daniel.vetter@ffwll.ch, intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH] drm: Fix DisplayPort branch device ID
Date: Fri, 16 Sep 2016 14:19:42 +0300 [thread overview]
Message-ID: <87vaxwnlbl.fsf@intel.com> (raw)
In-Reply-To: <1474022355-29990-1-git-send-email-mika.kahola@intel.com>
On Fri, 16 Sep 2016, Mika Kahola <mika.kahola@intel.com> wrote:
> Fix missing parameter description for DisplayPort branch device ID.
> This fixes warning of "No description found for parameter 'id[6]'" when
> creating documentation by 'make htmldocs'.
>
> Signed-off-by: Mika Kahola <mika.kahola@intel.com>
Pushed to drm-intel-next-queued, with some tags added:
Reported-by: kbuild test robot <fengguang.wu@intel.com>
References: https://lists.freedesktop.org/archives/intel-gfx/2016-September/106645.html
Fixes: 266d783baaf5 ("drm: Read DP branch device id")
BR,
Jani.
> ---
> drivers/gpu/drm/drm_dp_helper.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/drivers/gpu/drm/drm_dp_helper.c b/drivers/gpu/drm/drm_dp_helper.c
> index a536514..0ad20f1 100644
> --- a/drivers/gpu/drm/drm_dp_helper.c
> +++ b/drivers/gpu/drm/drm_dp_helper.c
> @@ -517,6 +517,7 @@ EXPORT_SYMBOL(drm_dp_downstream_max_bpc);
> /**
> * drm_dp_downstream_id() - identify branch device
> * @aux: DisplayPort AUX channel
> + * @id: DisplayPort branch device id
> *
> * Returns branch device id on success or NULL on failure
> */
--
Jani Nikula, Intel Open Source Technology Center
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
prev parent reply other threads:[~2016-09-16 11:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-16 10:39 [PATCH] drm: Fix DisplayPort branch device ID Mika Kahola
2016-09-16 11:19 ` 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=87vaxwnlbl.fsf@intel.com \
--to=jani.nikula@intel.com \
--cc=daniel.vetter@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=mika.kahola@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).