From: Daniel Vetter <daniel@ffwll.ch>
To: Geliang Tang <geliangtang@163.com>
Cc: David Airlie <airlied@linux.ie>,
linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org
Subject: Re: [PATCH 2/3] drm: fix kernel-doc warnings in drm_crtc.h
Date: Tue, 22 Sep 2015 11:22:54 +0200 [thread overview]
Message-ID: <20150922092254.GC3383@phenom.ffwll.local> (raw)
In-Reply-To: <48d978610cbac46c00d06812c6bcee9350083d76.1442499384.git.geliangtang@163.com>
On Wed, Sep 16, 2015 at 11:25:22PM -0700, Geliang Tang wrote:
> Fix the following 'make htmldocs' warning:
>
> .//include/drm/drm_crtc.h:929: warning: Excess struct/union/enum/typedef member 'base' description in 'drm_bridge'
>
> Signed-off-by: Geliang Tang <geliangtang@163.com>
Applied to drm-misc, thanks.
-Daniel
> ---
> include/drm/drm_crtc.h | 1 -
> 1 file changed, 1 deletion(-)
>
> diff --git a/include/drm/drm_crtc.h b/include/drm/drm_crtc.h
> index c0366e9..6566f72 100644
> --- a/include/drm/drm_crtc.h
> +++ b/include/drm/drm_crtc.h
> @@ -911,7 +911,6 @@ struct drm_bridge_funcs {
> * @next: the next bridge in the encoder chain
> * @of_node: device node pointer to the bridge
> * @list: to keep track of all added bridges
> - * @base: base mode object
> * @funcs: control functions
> * @driver_private: pointer to the bridge driver's internal context
> */
> --
> 1.9.1
>
>
> _______________________________________________
> dri-devel mailing list
> dri-devel@lists.freedesktop.org
> http://lists.freedesktop.org/mailman/listinfo/dri-devel
--
Daniel Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch
prev parent reply other threads:[~2015-09-22 9:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-17 6:25 [PATCH 1/3] media: dvb-core: fix kernel-doc warnings in dvbdev.h Geliang Tang
2015-09-17 6:25 ` [PATCH 2/3] drm: fix kernel-doc warnings in drm_crtc.h Geliang Tang
2015-09-17 6:25 ` [PATCH 3/3] hsi: fix kernel-doc warnings in hsi.h Geliang Tang
2015-09-22 9:22 ` 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=20150922092254.GC3383@phenom.ffwll.local \
--to=daniel@ffwll.ch \
--cc=airlied@linux.ie \
--cc=dri-devel@lists.freedesktop.org \
--cc=geliangtang@163.com \
--cc=linux-kernel@vger.kernel.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
Powered by JetHome