From: "Rafael J. Wysocki" <rjw@rjwysocki.net>
To: David Archuleta <darchuletajr@gmail.com>
Cc: lenb@kernel.org, linux-acpi@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] acpi: processor_throttling: fixed a few brace coding style issues.
Date: Sun, 12 Aug 2018 13:19:02 +0200 [thread overview]
Message-ID: <2258817.rCk9hs2z3C@aspire.rjw.lan> (raw)
In-Reply-To: <20180726202341.9816-1-darchuletajr@gmail.com>
On Thursday, July 26, 2018 10:23:41 PM CEST David Archuleta wrote:
> From: darchuletajr <darchuletajr@gmail.com>
>
> Fixed a few brace coding style issues found by running
> ./scripts/checkpatch
>
> Signed-off-by: David Archuleta Jr. <darchuletajr@gmail.com>
IMO this doesn't add any value to the code, so I'm not going to apply it.
> ---
> drivers/acpi/processor_throttling.c | 12 ++++--------
> 1 file changed, 4 insertions(+), 8 deletions(-)
>
> diff --git a/drivers/acpi/processor_throttling.c b/drivers/acpi/processor_throttling.c
> index fbc936cf2025..75cc179b352b 100644
> --- a/drivers/acpi/processor_throttling.c
> +++ b/drivers/acpi/processor_throttling.c
> @@ -298,9 +298,8 @@ static int acpi_processor_get_platform_limit(struct acpi_processor *pr)
>
> status = acpi_evaluate_integer(pr->handle, "_TPC", NULL, &tpc);
> if (ACPI_FAILURE(status)) {
> - if (status != AE_NOT_FOUND) {
> + if (status != AE_NOT_FOUND)
> ACPI_EXCEPTION((AE_INFO, status, "Evaluating _TPC"));
> - }
> return -ENODEV;
> }
>
> @@ -431,9 +430,8 @@ static int acpi_processor_get_throttling_control(struct acpi_processor *pr)
>
> status = acpi_evaluate_object(pr->handle, "_PTC", NULL, &buffer);
> if (ACPI_FAILURE(status)) {
> - if (status != AE_NOT_FOUND) {
> + if (status != AE_NOT_FOUND)
> ACPI_EXCEPTION((AE_INFO, status, "Evaluating _PTC"));
> - }
> return -ENODEV;
> }
>
> @@ -516,9 +514,8 @@ static int acpi_processor_get_throttling_states(struct acpi_processor *pr)
>
> status = acpi_evaluate_object(pr->handle, "_TSS", NULL, &buffer);
> if (ACPI_FAILURE(status)) {
> - if (status != AE_NOT_FOUND) {
> + if (status != AE_NOT_FOUND)
> ACPI_EXCEPTION((AE_INFO, status, "Evaluating _TSS"));
> - }
> return -ENODEV;
> }
>
> @@ -596,9 +593,8 @@ static int acpi_processor_get_tsd(struct acpi_processor *pr)
>
> status = acpi_evaluate_object(pr->handle, "_TSD", NULL, &buffer);
> if (ACPI_FAILURE(status)) {
> - if (status != AE_NOT_FOUND) {
> + if (status != AE_NOT_FOUND)
> ACPI_EXCEPTION((AE_INFO, status, "Evaluating _TSD"));
> - }
> return -ENODEV;
> }
>
>
prev parent reply other threads:[~2018-08-12 11:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-26 20:23 David Archuleta
2018-08-12 11:19 ` Rafael J. Wysocki [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=2258817.rCk9hs2z3C@aspire.rjw.lan \
--to=rjw@rjwysocki.net \
--cc=darchuletajr@gmail.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.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®