[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAJOA=zMPQK-W_nbRztXCNdLHoTJU73ZnrxAS8VvvmzgdaVS2mQ@mail.gmail.com>
Date: Mon, 16 Apr 2012 16:10:56 -0700
From: "Turquette, Mike" <mturquette@...com>
To: Shawn Guo <shawn.guo@...aro.org>
Cc: Andrew Lunn <andrew@...n.ch>,
Mark Brown <broonie@...nsource.wolfsonmicro.com>,
Russell King <linux@....linux.org.uk>, patches@...aro.org,
Sascha Hauer <s.hauer@...gutronix.de>,
Rajendra Nayak <rnayak@...com>, linux-kernel@...r.kernel.org,
Saravana Kannan <skannan@...eaurora.org>,
Olof Johansson <olof@...om.net>, linaro-dev@...ts.linaro.org,
arnd.bergmann@...aro.org, linux-arm-kernel@...ts.infradead.org
Subject: Re: [PATCH 13/13] clk: basic: improve parent_names & return errors
On Wed, Apr 11, 2012 at 11:49 PM, Shawn Guo <shawn.guo@...aro.org> wrote:
> On Wed, Apr 11, 2012 at 06:02:51PM -0700, Mike Turquette wrote:
> ...
>> @@ -175,23 +188,32 @@ struct clk *clk_register_divider(struct device *dev, const char *name,
>> div->flags = clk_divider_flags;
>> div->lock = lock;
>>
>> + /* allocate the temporary parent_names */
>> if (parent_name) {
>> - div->parent[0] = kstrdup(parent_name, GFP_KERNEL);
>> - if (!div->parent[0])
>> - goto out;
>> + parent_names[0] = kstrdup(parent_name, GFP_KERNEL);
>> + if (!parent_names[0]) {
>> + pr_err("%s: could not allocate parent_names\n",
>> + __func__);
>> + goto fail_parent_names;
>> + }
>> }
>
> Why do we need to copy the parent_names here at all? clk_register()
> has done that for each basic clk.
Yes, this was a braindead change on my part. I'll remove the kstrdup
in my next series (the rest of this patch will stay in).
Thanks,
Mike
> Regards,
> Shawn
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists