From: Guenter Roeck <linux@roeck-us.net>
To: Luca Ceresoli <luca.ceresoli@bootlin.com>
Cc: Wim Van Sebroeck <wim@linux-watchdog.org>,
Thomas Petazzoni <thomas.petazzoni@bootlin.com>,
linux-watchdog@vger.kernel.org, linux-kernel@vger.kernel.org,
kernel test robot <lkp@intel.com>
Subject: Re: [PATCH] watchdog: max77620: fix excess field in kerneldoc
Date: Thu, 2 Jan 2025 07:43:27 -0800 [thread overview]
Message-ID: <984cdd73-8799-477f-bd7b-e53dc878f1ab@roeck-us.net> (raw)
In-Reply-To: <20241230-max77620_wdt-kerneldoc-fix-v1-1-8a3211818993@bootlin.com>
On Mon, Dec 30, 2024 at 06:35:58PM +0100, Luca Ceresoli wrote:
> The wdt_info does not exist in the struct being documented.
>
> Reported-by: kernel test robot <lkp@intel.com>
> Closes: https://lore.kernel.org/oe-kbuild-all/202412281555.YMBF9azh-lkp@intel.com/
> Signed-off-by: Luca Ceresoli <luca.ceresoli@bootlin.com>
Reviewed-by: Guenter Roeck <linux@roeck-us.net>
> ---
> drivers/watchdog/max77620_wdt.c | 1 -
> 1 file changed, 1 deletion(-)
>
> diff --git a/drivers/watchdog/max77620_wdt.c b/drivers/watchdog/max77620_wdt.c
> index 33835c0b06de573c93737309bd69c7aaab43127e..d3ced783a5f4d554db787a47185c8b7eb7ac85e4 100644
> --- a/drivers/watchdog/max77620_wdt.c
> +++ b/drivers/watchdog/max77620_wdt.c
> @@ -25,7 +25,6 @@ static bool nowayout = WATCHDOG_NOWAYOUT;
>
> /**
> * struct max77620_variant - Data specific to a chip variant
> - * @wdt_info: watchdog descriptor
> * @reg_onoff_cnfg2: ONOFF_CNFG2 register offset
> * @reg_cnfg_glbl2: CNFG_GLBL2 register offset
> * @reg_cnfg_glbl3: CNFG_GLBL3 register offset
>
> ---
> base-commit: fc033cf25e612e840e545f8d5ad2edd6ba613ed5
> change-id: 20241230-max77620_wdt-kerneldoc-fix-cc129bae0fb7
>
> Best regards,
> --
> Luca Ceresoli <luca.ceresoli@bootlin.com>
>
prev parent reply other threads:[~2025-01-02 15:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-30 17:35 [PATCH] watchdog: max77620: fix excess field in kerneldoc Luca Ceresoli
2025-01-02 15:43 ` 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=984cdd73-8799-477f-bd7b-e53dc878f1ab@roeck-us.net \
--to=linux@roeck-us.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-watchdog@vger.kernel.org \
--cc=lkp@intel.com \
--cc=luca.ceresoli@bootlin.com \
--cc=thomas.petazzoni@bootlin.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