From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: "Rafael J . Wysocki" <rafael.j.wysocki@intel.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1 3/3] device property: attach 'else if' to the proper 'if'
Date: Mon, 10 Aug 2015 20:05:22 +0300 [thread overview]
Message-ID: <1439226322.29746.227.camel@linux.intel.com> (raw)
In-Reply-To: <1439225808-132916-3-git-send-email-andriy.shevchenko@linux.intel.com>
On Mon, 2015-08-10 at 19:56 +0300, Andy Shevchenko wrote:
> Obviously in the current place the 'else' keyword is redundant,
> though it seems
> quite correct when we check if nval is in allowed range.
>
> Reattach the condition branch there.
Rafael, it would be nice to have these fixes in 4.3 as well if you have
no objections.
One comment below.
>
> Signed-off-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
> ---
> drivers/acpi/property.c | 8 ++++----
> 1 file changed, 4 insertions(+), 4 deletions(-)
>
> diff --git a/drivers/acpi/property.c b/drivers/acpi/property.c
> index 7836e2e..a28752c 100644
> --- a/drivers/acpi/property.c
> +++ b/drivers/acpi/property.c
> @@ -528,13 +528,14 @@ int acpi_dev_prop_read(struct acpi_device
> *adev, const char *propname,
>
> if (!val)
> return obj->package.count;
> - else if (nval <= 0)
> - return -EINVAL;
>
> if (nval > obj->package.count)
> return -EOVERFLOW;
> + else if (nval <= 0)
> + return -EINVAL;
>
> items = obj->package.elements;
> +
This…
> switch (proptype) {
> case DEV_PROP_U8:
> ret = acpi_copy_property_array_u8(items, (u8 *)val,
> nval);
> @@ -552,8 +553,7 @@ int acpi_dev_prop_read(struct acpi_device *adev,
> const char *propname,
> ret = acpi_copy_property_array_string(items, (char
> **)val, nval);
> break;
> default:
> - ret = -EINVAL;
> - break;
> + return -EINVAL;
…and this seem left overs. If you wish I can resend this patch without
them.
> }
> return ret;
> }
--
Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Intel Finland Oy
next prev parent reply other threads:[~2015-08-10 17:05 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-10 16:56 [PATCH v1 1/3] device property: check fwnode type in to_of_node() Andy Shevchenko
2015-08-10 16:56 ` [PATCH v1 2/3] device property: fallback to pset when gettng one string Andy Shevchenko
2015-08-12 11:48 ` Mika Westerberg
2015-08-10 16:56 ` [PATCH v1 3/3] device property: attach 'else if' to the proper 'if' Andy Shevchenko
2015-08-10 17:05 ` Andy Shevchenko [this message]
2015-08-12 11:52 ` Mika Westerberg
2015-08-12 11:47 ` [PATCH v1 1/3] device property: check fwnode type in to_of_node() Mika Westerberg
2015-08-26 0:17 ` Rafael J. Wysocki
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=1439226322.29746.227.camel@linux.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rafael.j.wysocki@intel.com \
/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
Powered by JetHome