From: Randy Dunlap <rdunlap@infradead.org>
To: Yang Yingliang <yangyingliang@huawei.com>,
linux-kernel@vger.kernel.org, linux-rtc@vger.kernel.org
Cc: a.zummo@towertech.it, alexandre.belloni@bootlin.com
Subject: Re: [PATCH -next] rtc: m41t80: correct function names in rtc-m41t80.c
Date: Sun, 16 May 2021 22:07:28 -0700 [thread overview]
Message-ID: <6dc0bf7e-50d3-e8bb-d068-a8a9bbed6fa1@infradead.org> (raw)
In-Reply-To: <20210517045831.3461507-1-yangyingliang@huawei.com>
On 5/16/21 9:58 PM, Yang Yingliang wrote:
> Fix the following make W=1 kernel build warnings:
>
> drivers/rtc/rtc-m41t80.c:811: warning: expecting prototype for wdt_close(). Prototype was for wdt_release() instead
> drivers/rtc/rtc-m41t80.c:830: warning: expecting prototype for notify_sys(). Prototype was for wdt_notify_sys() instead
>
> Signed-off-by: Yang Yingliang <yangyingliang@huawei.com>
Hi,
In kernel-doc notation, a function name should be followed by a '-',
not a ':'. Please fix & resend.
Thanks.
> ---
> drivers/rtc/rtc-m41t80.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/rtc/rtc-m41t80.c b/drivers/rtc/rtc-m41t80.c
> index 89128fc29ccc..79512d1c828e 100644
> --- a/drivers/rtc/rtc-m41t80.c
> +++ b/drivers/rtc/rtc-m41t80.c
> @@ -802,7 +802,7 @@ static int wdt_open(struct inode *inode, struct file *file)
> }
>
> /**
> - * wdt_close:
> + * wdt_release:
> * @inode: inode to board
> * @file: file handle to board
> *
> @@ -815,7 +815,7 @@ static int wdt_release(struct inode *inode, struct file *file)
> }
>
> /**
> - * notify_sys:
> + * wdt_notify_sys:
> * @this: our notifier block
> * @code: the event being reported
> * @unused: unused
>
--
~Randy
prev parent reply other threads:[~2021-05-17 5:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-17 4:58 Yang Yingliang
2021-05-17 5:07 ` Randy Dunlap [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=6dc0bf7e-50d3-e8bb-d068-a8a9bbed6fa1@infradead.org \
--to=rdunlap@infradead.org \
--cc=a.zummo@towertech.it \
--cc=alexandre.belloni@bootlin.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rtc@vger.kernel.org \
--cc=yangyingliang@huawei.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
all inboxes | Powered by JetHome®