[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20120502101132.GW4141@pengutronix.de>
Date: Wed, 2 May 2012 12:11:32 +0200
From: Sascha Hauer <s.hauer@...gutronix.de>
To: Russell King - ARM Linux <linux@....linux.org.uk>
Cc: Saravana Kannan <skannan@...eaurora.org>,
Mike Turquette <mturquette@...aro.org>,
Arnd Bergman <arnd.bergmann@...aro.org>,
linux-arm-kernel@...ts.infradead.org, Andrew Lunn <andrew@...n.ch>,
Paul Walmsley <paul@...an.com>,
Linus Walleij <linus.walleij@...ricsson.com>,
Stephen Boyd <sboyd@...eaurora.org>,
linux-arm-msm@...r.kernel.org,
Mark Brown <broonie@...nsource.wolfsonmicro.com>,
Magnus Damm <magnus.damm@...il.com>,
linux-kernel@...r.kernel.org,
Rob Herring <rob.herring@...xeda.com>,
Richard Zhao <richard.zhao@...aro.org>,
Grant Likely <grant.likely@...retlab.ca>,
Deepak Saxena <dsaxena@...aro.org>,
Amit Kucheria <amit.kucheria@...aro.org>,
Jamie Iles <jamie@...ieiles.com>,
Jeremy Kerr <jeremy.kerr@...onical.com>,
Thomas Gleixner <tglx@...utronix.de>,
Shawn Guo <shawn.guo@...escale.com>
Subject: Re: [PATCH] clk: Use a separate struct for holding init data.
On Wed, May 02, 2012 at 11:02:25AM +0100, Russell King - ARM Linux wrote:
> >
> > There is a mux->hw.init = &init missing here.
>
> What happens to mux->hw.init long term? Because once this function
> returns, that pointer will no longer be valid.
It's not used after clk_register, so everything should be fine.
> It would be a good
> idea to NULL it out in clk_register() once its done with, to ensure
> that no one comes up with the idea of using it later.
Enforcing this is a good idea.
Sascha
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
--
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