From: Jani Nikula <jani.nikula@intel.com>
To: Egbert Eich <eich@suse.com>
Cc: Egbert Eich <eich@suse.de>,
Danilo Cesar Lemes de Paula <danilo.cesar@collabora.co.uk>,
Jonathan Corbet <corbet@lwn.net>,
Daniel Vetter <daniel.vetter@ffwll.ch>,
intel-gfx@lists.freedesktop.org, kbuild-all@01.org,
kbuild test robot <fengguang.wu@intel.com>
Subject: Re: [drm-intel:for-linux-next-fixes 3/4] DockBook: drivers/gpu/drm/drm_probe_helper.c:107: warning: Excess function parameter 'dev' description in 'DRM_OUTPUT_POLL_PERIOD'
Date: Thu, 01 Oct 2015 11:35:27 +0300 [thread overview]
Message-ID: <87wpv7asvk.fsf@intel.com> (raw)
In-Reply-To: <22027.60259.312717.617536@linux-qknr.fritz.box>
On Wed, 30 Sep 2015, Egbert Eich <eich@suse.com> wrote:
> Jani Nikula writes:
> > On Wed, 30 Sep 2015, Daniel Vetter <daniel@ffwll.ch> wrote:
> > > On Wed, Sep 30, 2015 at 05:09:04PM +0800, kbuild test robot wrote:
> > >> tree: git://anongit.freedesktop.org/drm-intel for-linux-next-fixes
> > >> head: ad96c5f13442b17fafccc30f81efae2f08351f99
> > >> commit: 10d3a5618b3aba24d6388ccdff2d0182b72a6e8d [3/4] drm: Add a non-locking version of drm_kms_helper_poll_enable(), v2
> > >> reproduce: make htmldocs
> > >>
> > >> All warnings (new ones prefixed by >>):
> >
> > Cc: Jonathan and Danilo, and including the kernel-doc in question for
> > reference:
> >
> > /**
> > * drm_kms_helper_poll_enable_locked - re-enable output polling.
> > * @dev: drm_device
> > *
> > * This function re-enables the output polling work without
> > * locking the mode_config mutex.
> > *
> > * This is like drm_kms_helper_poll_enable() however it is to be
> > * called from a context where the mode_config mutex is locked
> > * already.
> > */
> > #define DRM_OUTPUT_POLL_PERIOD (10*HZ)
> > void drm_kms_helper_poll_enable_locked(struct drm_device *dev)
> > {
> > ...
> >
> > >> >> drivers/gpu/drm/drm_probe_helper.c:107: warning: Excess function parameter 'dev' description in 'DRM_OUTPUT_POLL_PERIOD'
> > >> >> drivers/gpu/drm/drm_probe_helper.c:107: warning: Excess function parameter 'dev' description in 'DRM_OUTPUT_POLL_PERIOD'
> > >
> > > I think this should be fixed by moving the DRM_OUTPUT_POLL_PERIOD #define
> > > before the kerneldoc for drm_kms_helper_poll_enable_locked. Jani, can you
> > > please do that fixup and check that make htmldocs is happy with it?
> >
> > Can do.
> >
> > However, having such #defines right above the only function that uses
> > them is not uncommon. Since there is no documentation for
> > DRM_OUTPUT_POLL_PERIOD, and the documentation for the function includes
> > the function name, I am wondering if kernel-doc could be made smarter
> > about this.
> >
>
> It is actually used twice in this file by two functions not immediately adjacent.
> Why not move it to the beginning of the file?
That would've been better, however I was too quick to fix it already
like Daniel suggested.
BR,
Jani.
>
> Cheers,
> Egbert.
--
Jani Nikula, Intel Open Source Technology Center
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
prev parent reply other threads:[~2015-10-01 8:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-30 9:09 [drm-intel:for-linux-next-fixes 3/4] DockBook: drivers/gpu/drm/drm_probe_helper.c:107: warning: Excess function parameter 'dev' description in 'DRM_OUTPUT_POLL_PERIOD' kbuild test robot
2015-09-30 12:34 ` Daniel Vetter
2015-09-30 13:00 ` Jani Nikula
2015-09-30 14:02 ` Egbert Eich
2015-10-01 8:35 ` 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=87wpv7asvk.fsf@intel.com \
--to=jani.nikula@intel.com \
--cc=corbet@lwn.net \
--cc=daniel.vetter@ffwll.ch \
--cc=danilo.cesar@collabora.co.uk \
--cc=eich@suse.com \
--cc=eich@suse.de \
--cc=fengguang.wu@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=kbuild-all@01.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