From: Tony Lindgren <tony@atomide.com>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: linux-kernel@vger.kernel.org, kernel test robot <lkp@intel.com>,
Arnd Bergmann <arnd@arndb.de>, Vaibhav Hiremath <hvaibhav@ti.com>,
Felipe Balbi <balbi@ti.com>, Xunlei Pang <pang.xunlei@linaro.org>,
John Stultz <john.stultz@linaro.org>,
Ingo Molnar <mingo@kernel.org>,
Aaro Koskinen <aaro.koskinen@iki.fi>,
Janusz Krzysztofik <jmkrzyszt@gmail.com>,
linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] ARM: OMAP: timer32K: fix all kernel-doc warnings
Date: Sat, 7 Oct 2023 10:44:06 +0300 [thread overview]
Message-ID: <20231007074406.GZ34982@atomide.com> (raw)
In-Reply-To: <20231007001603.24972-1-rdunlap@infradead.org>
* Randy Dunlap <rdunlap@infradead.org> [231007 03:16]:
> Fix kernel-doc warnings reported by the kernel test robot:
>
> timer32k.c:186: warning: cannot understand function prototype: 'struct timespec64 persistent_ts; '
> timer32k.c:191: warning: Function parameter or member 'ts' not described in 'omap_read_persistent_clock64'
> timer32k.c:216: warning: Function parameter or member 'vbase' not described in 'omap_init_clocksource_32k'
> timer32k.c:216: warning: Excess function parameter 'pbase' description in 'omap_init_clocksource_32k'
> timer32k.c:216: warning: Excess function parameter 'size' description in 'omap_init_clocksource_32k'
> timer32k.c:216: warning: No description found for return value of 'omap_init_clocksource_32k'
Thanks applying into fixes.
Tony
prev parent reply other threads:[~2023-10-07 7:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-07 0:16 Randy Dunlap
2023-10-07 7:44 ` Tony Lindgren [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=20231007074406.GZ34982@atomide.com \
--to=tony@atomide.com \
--cc=aaro.koskinen@iki.fi \
--cc=arnd@arndb.de \
--cc=balbi@ti.com \
--cc=hvaibhav@ti.com \
--cc=jmkrzyszt@gmail.com \
--cc=john.stultz@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=lkp@intel.com \
--cc=mingo@kernel.org \
--cc=pang.xunlei@linaro.org \
--cc=rdunlap@infradead.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