From: <Claudiu.Beznea@microchip.com>
To: <rdunlap@infradead.org>, <linux-kernel@vger.kernel.org>
Cc: <andrei.stefanescu@microchip.com>, <broonie@kernel.org>,
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH] regulator: mcp16502: add enum MCP16502_REG_HPM description
Date: Tue, 17 Jan 2023 08:32:27 +0000 [thread overview]
Message-ID: <c8a2c56c-b372-6888-404b-7f548e52275e@microchip.com> (raw)
In-Reply-To: <20230117070139.28905-1-rdunlap@infradead.org>
On 17.01.2023 09:01, Randy Dunlap wrote:
> EXTERNAL EMAIL: Do not click links or open attachments unless you know the content is safe
>
> Add description for MCP16502_REG_HPM to prevent a kernel-doc warning:
>
> drivers/regulator/mcp16502.c:90: warning: Enum value 'MCP16502_REG_HPM' not described in enum 'mcp16502_reg'
>
> Fixes: 3e5532a011b0 ("regulator: mcp16502: adapt for get/set on other registers")
Fixes tag could be removed as this isn't a functional fix.
With that addressed:
Reviewed-by: Claudiu Beznea <claudiu.beznea@microchip.com>
> Signed-off-by: Randy Dunlap <rdunlap@infradead.org>
> Cc: Andrei Stefanescu <andrei.stefanescu@microchip.com>
> Cc: Claudiu Beznea <claudiu.beznea@microchip.com>
> Cc: Mark Brown <broonie@kernel.org>
> Cc: linux-arm-kernel@lists.infradead.org
> ---
> drivers/regulator/mcp16502.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff -- a/drivers/regulator/mcp16502.c b/drivers/regulator/mcp16502.c
> --- a/drivers/regulator/mcp16502.c
> +++ b/drivers/regulator/mcp16502.c
> @@ -77,6 +77,7 @@
> * @MCP16502_REG_A: active state register
> * @MCP16502_REG_LPM: low power mode state register
> * @MCP16502_REG_HIB: hibernate state register
> + * @MCP16502_REG_HPM: high-performance mode register
> * @MCP16502_REG_SEQ: startup sequence register
> * @MCP16502_REG_CFG: configuration register
> */
next prev parent reply other threads:[~2023-01-17 8:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-17 7:01 [PATCH] regulator: mcp16502: add enum MCP16502_REG_HPM description Randy Dunlap
2023-01-17 8:32 ` Claudiu.Beznea [this message]
2023-01-18 14:55 ` Mark Brown
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=c8a2c56c-b372-6888-404b-7f548e52275e@microchip.com \
--to=claudiu.beznea@microchip.com \
--cc=andrei.stefanescu@microchip.com \
--cc=broonie@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).