From: Philipp Zabel <p.zabel@pengutronix.de>
To: Krzysztof Kozlowski <krzk@kernel.org>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] reset: Fix and extend kerneldoc
Date: Wed, 29 Jul 2020 08:41:21 +0200 [thread overview]
Message-ID: <dd98ed496cedfceec3d41064e95f05b8d3adcca1.camel@pengutronix.de> (raw)
In-Reply-To: <20200728171011.28412-1-krzk@kernel.org>
Hi Krzysztof,
On Tue, 2020-07-28 at 19:10 +0200, Krzysztof Kozlowski wrote:
> Fix W=1 compile warnings (invalid kerneldoc):
>
> drivers/reset/core.c:50: warning: Function parameter or member 'array' not described in 'reset_control'
> drivers/reset/core.c:50: warning: Function parameter or member 'deassert_count' not described in 'reset_control'
>
> Signed-off-by: Krzysztof Kozlowski <krzk@kernel.org>
> ---
> drivers/reset/core.c | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/reset/core.c b/drivers/reset/core.c
> index 01c0c7aa835c..a2df88e90011 100644
> --- a/drivers/reset/core.c
> +++ b/drivers/reset/core.c
> @@ -32,7 +32,8 @@ static LIST_HEAD(reset_lookup_list);
> * @refcnt: Number of gets of this reset_control
> * @acquired: Only one reset_control may be acquired for a given rcdev and id.
> * @shared: Is this a shared (1), or an exclusive (0) reset_control?
> - * @deassert_cnt: Number of times this reset line has been deasserted
> + * @array: Is this an array of reset controls (1)?
> + * @deassert_count: Number of times this reset line has been deasserted
> * @triggered_count: Number of times this reset line has been reset. Currently
> * only used for shared resets, which means that the value
> * will be either 0 or 1.
Thank you for the fix, applied to reset/next.
regards
Philipp
prev parent reply other threads:[~2020-07-29 6:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-28 17:10 Krzysztof Kozlowski
2020-07-29 6:41 ` Philipp Zabel [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=dd98ed496cedfceec3d41064e95f05b8d3adcca1.camel@pengutronix.de \
--to=p.zabel@pengutronix.de \
--cc=krzk@kernel.org \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®