From: SF Markus Elfring <elfring@users.sourceforge.net>
To: linux-clk@vger.kernel.org,
Michael Turquette <mturquette@baylibre.com>,
Stephen Boyd <sboyd@codeaurora.org>
Cc: LKML <linux-kernel@vger.kernel.org>, kernel-janitors@vger.kernel.org
Subject: [PATCH 0/5] clk-mvebu: Fine-tuning for four function implementations
Date: Wed, 19 Apr 2017 21:51:24 +0200 [thread overview]
Message-ID: <8af5ccb0-f7c1-297c-2661-8ced61302c37@users.sourceforge.net> (raw)
From: Markus Elfring <elfring@users.sourceforge.net>
Date: Wed, 19 Apr 2017 21:45:43 +0200
A few update suggestions were taken into account
from static source code analysis.
Markus Elfring (5):
Use kcalloc() in of_cpu_clk_setup()
Adjust two checks for null pointers in of_cpu_clk_setup()
Use kcalloc() in two functions
Adjust two checks for null pointers in kirkwood_fix_sscg_deviation()
Delete an unnecessary variable initialisation in kirkwood_fix_sscg_deviation()
drivers/clk/mvebu/clk-cpu.c | 8 ++++----
drivers/clk/mvebu/common.c | 10 +++++-----
2 files changed, 9 insertions(+), 9 deletions(-)
--
2.12.2
next reply other threads:[~2017-04-19 19:51 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-19 19:51 SF Markus Elfring [this message]
2017-04-19 19:52 ` [PATCH 1/5] clk: mvebu: Use kcalloc() in of_cpu_clk_setup() SF Markus Elfring
2017-04-22 2:49 ` Stephen Boyd
2017-04-19 19:54 ` [PATCH 2/5] clk: mvebu: Adjust two checks for null pointers " SF Markus Elfring
2017-04-19 19:55 ` [PATCH 3/5] clk: mvebu: Use kcalloc() in two functions SF Markus Elfring
2017-04-22 2:49 ` Stephen Boyd
2017-04-19 19:56 ` [PATCH 4/5] clk: mvebu: Adjust two checks for null pointers in kirkwood_fix_sscg_deviation() SF Markus Elfring
2017-04-19 19:57 ` [PATCH 5/5] clk: mvebu: Delete an unnecessary variable initialisation " SF Markus Elfring
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=8af5ccb0-f7c1-297c-2661-8ced61302c37@users.sourceforge.net \
--to=elfring@users.sourceforge.net \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=sboyd@codeaurora.org \
--subject='Re: [PATCH 0/5] clk-mvebu: Fine-tuning for four function implementations' \
/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
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).