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 6/8] clk: Improve a size determination in two functions
Date: Thu, 20 Apr 2017 10:29:43 +0200 [thread overview]
Message-ID: <599640c0-d9a1-f1a4-47f3-edaf98f407c1@users.sourceforge.net> (raw)
In-Reply-To: <94b24eaa-c5fb-80ea-441a-883989d14ef5@users.sourceforge.net>
From: Markus Elfring <elfring@users.sourceforge.net>
Date: Thu, 20 Apr 2017 09:30:52 +0200
Replace the specification of two data structures by pointer dereferences
as the parameter for the operator "sizeof" to make the corresponding size
determination a bit safer according to the Linux coding style convention.
Signed-off-by: Markus Elfring <elfring@users.sourceforge.net>
---
drivers/clk/clk.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/clk/clk.c b/drivers/clk/clk.c
index 684642ab4212..3f2ee0469d3e 100644
--- a/drivers/clk/clk.c
+++ b/drivers/clk/clk.c
@@ -2939,7 +2939,7 @@ int clk_notifier_register(struct clk *clk, struct notifier_block *nb)
/* if clk wasn't in the notifier list, allocate new clk_notifier */
if (cn->clk != clk) {
- cn = kzalloc(sizeof(struct clk_notifier), GFP_KERNEL);
+ cn = kzalloc(sizeof(*cn), GFP_KERNEL);
if (!cn)
goto out;
@@ -3087,7 +3087,7 @@ int of_clk_add_provider(struct device_node *np,
struct of_clk_provider *cp;
int ret;
- cp = kzalloc(sizeof(struct of_clk_provider), GFP_KERNEL);
+ cp = kzalloc(sizeof(*cp), GFP_KERNEL);
if (!cp)
return -ENOMEM;
--
2.12.2
next prev parent reply other threads:[~2017-04-20 8:30 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-20 8:20 [PATCH 0/8] clk: Fine-tuning for ten function implementations SF Markus Elfring
2017-04-20 8:22 ` [PATCH 1/8] clk: si5351: Use devm_kcalloc() in si5351_i2c_probe() SF Markus Elfring
2017-04-22 2:44 ` Stephen Boyd
2017-04-20 8:23 ` [PATCH 2/8] clk: si5351: Delete an error message for a failed memory allocation " SF Markus Elfring
2017-04-22 2:45 ` Stephen Boyd
2017-04-20 8:26 ` [PATCH 3/8] clk: si5351: Adjust a null pointer check in si5351_dt_parse() SF Markus Elfring
2017-04-20 8:27 ` [PATCH 4/8] clk: Replace four seq_printf() calls by seq_putc() SF Markus Elfring
2017-04-22 2:46 ` Stephen Boyd
2017-04-20 8:28 ` [PATCH 5/8] clk: Combine two seq_puts() calls into one call in clk_summary_show() SF Markus Elfring
2017-04-20 8:29 ` SF Markus Elfring [this message]
2017-04-22 2:47 ` [PATCH 6/8] clk: Improve a size determination in two functions Stephen Boyd
2017-04-20 8:30 ` [PATCH 7/8] clk: nomadik: Use seq_puts() in nomadik_src_clk_show() SF Markus Elfring
2017-04-22 2:48 ` Stephen Boyd
2017-04-20 8:32 ` [PATCH 8/8] clk: nomadik: Delete error messages for a failed memory allocation in two functions SF Markus Elfring
2017-04-22 2:48 ` Stephen Boyd
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=599640c0-d9a1-f1a4-47f3-edaf98f407c1@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 \
/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;
as well as URLs for NNTP newsgroup(s).