[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20160923214730.GF21232@codeaurora.org>
Date: Fri, 23 Sep 2016 14:47:30 -0700
From: Stephen Boyd <sboyd@...eaurora.org>
To: Marcin Wojtas <mw@...ihalf.com>
Cc: linux-kernel@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
linux-clk@...r.kernel.org, mturquette@...libre.com,
sebastian.hesselbarth@...il.com, andrew@...n.ch,
jason@...edaemon.net, thomas.petazzoni@...e-electrons.com,
gregory.clement@...e-electrons.com, nadavh@...vell.com,
alior@...vell.com, tn@...ihalf.com, jaz@...ihalf.com
Subject: Re: [PATCH v3 3/3] clk: mvebu: migrate CP110 system controller to
clk_hw API and registration
On 09/21, Marcin Wojtas wrote:
> @@ -203,80 +202,75 @@ static int cp110_syscon_clk_probe(struct platform_device *pdev)
> if (ret)
> return ret;
>
> - cp110_clks = devm_kcalloc(&pdev->dev, sizeof(struct clk *),
> - CP110_CLK_NUM, GFP_KERNEL);
> - if (!cp110_clks)
> - return -ENOMEM;
> -
> - cp110_clk_data = devm_kzalloc(&pdev->dev,
> - sizeof(*cp110_clk_data),
> + cp110_clk_data = devm_kcalloc(&pdev->dev, sizeof(*cp110_clk_data),
> + sizeof(struct clk_hw *) * CP110_CLK_NUM,
> GFP_KERNEL);
This doesn't look right. Why are calloc()ing clk_hw_onecell_data this
way?
--
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
a Linux Foundation Collaborative Project
Powered by blists - more mailing lists