From: Jani Nikula <jani.nikula@linux.intel.com>
To: Thierry Reding <thierry.reding@gmail.com>,
dri-devel@lists.freedesktop.org
Subject: Re: [PATCH] drm/dp: Add missing kernel-doc
Date: Wed, 23 Apr 2014 17:15:06 +0300 [thread overview]
Message-ID: <87fvl4i13p.fsf@intel.com> (raw)
In-Reply-To: <1398260944-29552-1-git-send-email-thierry.reding@gmail.com>
On Wed, 23 Apr 2014, Thierry Reding <thierry.reding@gmail.com> wrote:
> From: Thierry Reding <treding@nvidia.com>
>
> Commit 9dc4056026e0 (drm/dp: let drivers specify the name of the I2C-
> over-AUX adapter) introduced a new field but didn't add the proper
> kernel-doc for it.
Thanks for fixing this.
Reviewed-by: Jani Nikula <jani.nikula@intel.com>
> Signed-off-by: Thierry Reding <treding@nvidia.com>
> ---
> include/drm/drm_dp_helper.h | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/include/drm/drm_dp_helper.h b/include/drm/drm_dp_helper.h
> index cfcacec5b89d..f98cebf79738 100644
> --- a/include/drm/drm_dp_helper.h
> +++ b/include/drm/drm_dp_helper.h
> @@ -431,6 +431,7 @@ struct drm_dp_aux_msg {
>
> /**
> * struct drm_dp_aux - DisplayPort AUX channel
> + * @name: user-visible name of this AUX channel and the I2C-over-AUX adapter
> * @ddc: I2C adapter that can be used for I2C-over-AUX communication
> * @dev: pointer to struct device that is the parent for this AUX channel
> * @transfer: transfers a message representing a single AUX transaction
> --
> 1.9.2
>
> _______________________________________________
> dri-devel mailing list
> dri-devel@lists.freedesktop.org
> http://lists.freedesktop.org/mailman/listinfo/dri-devel
--
Jani Nikula, Intel Open Source Technology Center
prev parent reply other threads:[~2014-04-23 14:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-23 13:49 [PATCH] drm/dp: Add missing kernel-doc Thierry Reding
2014-04-23 14:15 ` 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=87fvl4i13p.fsf@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=thierry.reding@gmail.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