From: Guenter Roeck <linux@roeck-us.net>
To: vee.khee.wong@intel.com, Wim Van Sebroeck <wim@linux-watchdog.org>
Cc: linux-watchdog@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/1] watchdog: wdat_wdt: Fix missing kerneldoc reported by W=1
Date: Wed, 11 Nov 2020 09:49:23 -0800 [thread overview]
Message-ID: <32eae86b-2242-9feb-3db0-b3bab89506ec@roeck-us.net> (raw)
In-Reply-To: <20201111172205.17215-1-vee.khee.wong@intel.com>
On 11/11/20 9:22 AM, vee.khee.wong@intel.com wrote:
> From: Wong Vee Khee <vee.khee.wong@intel.com>
>
> Fix the following warning while compiling with W=1.
>
> drivers/watchdog/wdat_wdt.c:48: warning: Function parameter or member 'instructions' not described in 'wdat_wdt'
>
> Signed-off-by: Wong Vee Khee <vee.khee.wong@intel.com>
Reviewed-by: Guenter Roeck <linux@roeck-us.net>
> ---
> drivers/watchdog/wdat_wdt.c | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/drivers/watchdog/wdat_wdt.c b/drivers/watchdog/wdat_wdt.c
> index 3065dd670a18..cec7917790e5 100644
> --- a/drivers/watchdog/wdat_wdt.c
> +++ b/drivers/watchdog/wdat_wdt.c
> @@ -34,9 +34,9 @@ struct wdat_instruction {
> * @period: How long is one watchdog period in ms
> * @stopped_in_sleep: Is this watchdog stopped by the firmware in S1-S5
> * @stopped: Was the watchdog stopped by the driver in suspend
> - * @actions: An array of instruction lists indexed by an action number from
> - * the WDAT table. There can be %NULL entries for not implemented
> - * actions.
> + * @instructions: An array of instruction lists indexed by an action number from
> + * the WDAT table. There can be %NULL entries for not implemented
> + * actions.
> */
> struct wdat_wdt {
> struct platform_device *pdev;
>
prev parent reply other threads:[~2020-11-11 17:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-11 17:22 [PATCH 1/1] watchdog: wdat_wdt: Fix missing kerneldoc reported by W=1 vee.khee.wong
2020-11-11 17:49 ` Guenter Roeck [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=32eae86b-2242-9feb-3db0-b3bab89506ec@roeck-us.net \
--to=linux@roeck-us.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-watchdog@vger.kernel.org \
--cc=vee.khee.wong@intel.com \
--cc=wim@linux-watchdog.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;
as well as URLs for NNTP newsgroup(s).