From: Frank Rowand <frowand.list@gmail.com>
To: Matti Vaittinen <matti.vaittinen@fi.rohmeurope.com>,
mazziesaccount@gmail.com
Cc: Rob Herring <robh+dt@kernel.org>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] of: property: Fix documentation for out values
Date: Tue, 12 Nov 2019 18:32:18 -0600 [thread overview]
Message-ID: <b1e7e17e-bf58-70af-b3de-7e8138d578ad@gmail.com> (raw)
In-Reply-To: <20191112081726.GA8291@localhost.localdomain>
Hi Matti,
On 11/12/19 2:17 AM, Matti Vaittinen wrote:
> Property fetching functions which return number of successfully fetched
> properties should not state that out-values are only modified if 0 is
> returned. Fix this.
>
> Signed-off-by: Matti Vaittinen <matti.vaittinen@fi.rohmeurope.com>
> ---
> drivers/of/property.c | 12 ++++++++----
> 1 file changed, 8 insertions(+), 4 deletions(-)
>
> diff --git a/drivers/of/property.c b/drivers/of/property.c
> index d7fa75e31f22..4aae93cdc1ce 100644
> --- a/drivers/of/property.c
> +++ b/drivers/of/property.c
> @@ -164,7 +164,8 @@ EXPORT_SYMBOL_GPL(of_property_read_u64_index);
> *
> * @np: device node from which the property value is to be read.
> * @propname: name of the property to be searched.
> - * @out_values: pointer to return value, modified only if return value is 0.
> + * @out_values: pointer to return value, modified only if return value is
> + * greater than 0.
> * @sz_min: minimum number of array elements to read
> * @sz_max: maximum number of array elements to read, if zero there is no
> * upper limit on the number of elements in the dts entry but only
> @@ -212,7 +213,8 @@ EXPORT_SYMBOL_GPL(of_property_read_variable_u8_array);
> *
> * @np: device node from which the property value is to be read.
> * @propname: name of the property to be searched.
> - * @out_values: pointer to return value, modified only if return value is 0.
> + * @out_values: pointer to return value, modified only if return value is
> + * greater than 0.
> * @sz_min: minimum number of array elements to read
> * @sz_max: maximum number of array elements to read, if zero there is no
> * upper limit on the number of elements in the dts entry but only
> @@ -260,7 +262,8 @@ EXPORT_SYMBOL_GPL(of_property_read_variable_u16_array);
> *
> * @np: device node from which the property value is to be read.
> * @propname: name of the property to be searched.
> - * @out_values: pointer to return value, modified only if return value is 0.
> + * @out_values: pointer to return value, modified only if return value is
> + * greater than 0.
> * @sz_min: minimum number of array elements to read
> * @sz_max: maximum number of array elements to read, if zero there is no
> * upper limit on the number of elements in the dts entry but only
> @@ -334,7 +337,8 @@ EXPORT_SYMBOL_GPL(of_property_read_u64);
> *
> * @np: device node from which the property value is to be read.
> * @propname: name of the property to be searched.
> - * @out_values: pointer to return value, modified only if return value is 0.
> + * @out_values: pointer to return value, modified only if return value is
> + * greater than 0.
> * @sz_min: minimum number of array elements to read
> * @sz_max: maximum number of array elements to read, if zero there is no
> * upper limit on the number of elements in the dts entry but only
>
Thanks for catching each of these cases of incorrect documentation.
Instead of correcting each of the descriptions, please just remove the incorrect
portion. So for each case, remove ", modified only if return value is 0."
The reference to return value of 0 is a left over from another set of functions
which were modified to call the set of functions that you fix above.
Thanks,
Frank
prev parent reply other threads:[~2019-11-13 0:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-12 8:17 [PATCH] of: property: Fix documentation for out values Matti Vaittinen
2019-11-13 0:32 ` Frank Rowand [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=b1e7e17e-bf58-70af-b3de-7e8138d578ad@gmail.com \
--to=frowand.list@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=matti.vaittinen@fi.rohmeurope.com \
--cc=mazziesaccount@gmail.com \
--cc=robh+dt@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