From: Peter Senna Tschudin <peter.senna@gmail.com>
To: Dominik Brodowski <linux@dominikbrodowski.net>
Cc: Peter Senna Tschudin <peter.senna@gmail.com>,
Thomas Renninger <trenn@suse.de>,
linux-kernel@vger.kernel.org,
"Rafael J. Wysocki" <rafael.j.wysocki@intel.com>,
Alan Cox <alan@linux.intel.com>,
kernel-janitors@vger.kernel.org
Subject: [PATCH 2/4] cpupower: Remove redundant error check
Date: Sat, 17 May 2014 20:22:58 +0200 [thread overview]
Message-ID: <1400350980-30455-2-git-send-email-peter.senna@gmail.com> (raw)
Remove double checks, and move the call to print_error to the
first check. The simplified version of the coccinelle semantic
patch that fixes this issue is as follows:
// <smpl>
@@
expression E; identifier pr; expression list es;
@@
for(...;...;...){
...
- if (E) break;
+ if (E){
+ pr(es);
+ break;
+ }
...
}
- if(E) pr(es);
// </smpl>
Untested.
Signed-off-by: Peter Senna Tschudin <peter.senna@gmail.com>
---
tools/power/cpupower/utils/cpufreq-set.c | 7 +++----
1 file changed, 3 insertions(+), 4 deletions(-)
diff --git a/tools/power/cpupower/utils/cpufreq-set.c b/tools/power/cpupower/utils/cpufreq-set.c
index a416de8..4e2f35a 100644
--- a/tools/power/cpupower/utils/cpufreq-set.c
+++ b/tools/power/cpupower/utils/cpufreq-set.c
@@ -320,12 +320,11 @@ int cmd_freq_set(int argc, char **argv)
printf(_("Setting cpu: %d\n"), cpu);
ret = do_one_cpu(cpu, &new_pol, freq, policychange);
- if (ret)
+ if (ret) {
+ print_error();
break;
+ }
}
- if (ret)
- print_error();
-
return ret;
}
next reply other threads:[~2014-05-17 18:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-17 18:22 Peter Senna Tschudin [this message]
2014-05-17 20:22 ` [PATCH 2/4] cpupower: Remove redundant error check Dan Carpenter
2014-05-17 21:34 ` Peter Senna Tschudin
2014-05-17 21:56 ` Dan Carpenter
2014-05-17 22:31 ` Peter Senna Tschudin
2014-05-17 22:42 ` Dan Carpenter
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=1400350980-30455-2-git-send-email-peter.senna@gmail.com \
--to=peter.senna@gmail.com \
--cc=alan@linux.intel.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@dominikbrodowski.net \
--cc=rafael.j.wysocki@intel.com \
--cc=trenn@suse.de \
/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