From mboxrd@z Thu Jan 1 00:00:00 1970 From: Joe Perches Subject: Re: [PATCH 1/6] clk: make strings in parent name arrays const Date: Mon, 30 Mar 2015 11:20:31 -0700 Message-ID: <1427739631.14276.23.camel@perches.com> References: <1427737245-4064-1-git-send-email-s.hauer@pengutronix.de> <1427737245-4064-2-git-send-email-s.hauer@pengutronix.de> <1427738119.14276.19.camel@perches.com> <20150330181657.GF9742@pengutronix.de> Mime-Version: 1.0 Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <20150330181657.GF9742@pengutronix.de> Sender: linux-kernel-owner@vger.kernel.org To: Sascha Hauer Cc: Mike Turquette , Stephen Boyd , YH Chen , linux-kernel@vger.kernel.org, Henry Chen , linux-mediatek@lists.infradead.org, kernel@pengutronix.de, Matthias Brugger , Yingjoe Chen , Eddie Huang , linux-arm-kernel@lists.infradead.org List-Id: linux-mediatek@lists.infradead.org On Mon, 2015-03-30 at 20:16 +0200, Sascha Hauer wrote: > On Mon, Mar 30, 2015 at 10:55:19AM -0700, Joe Perches wrote: > > On Mon, 2015-03-30 at 19:40 +0200, Sascha Hauer wrote: > > > The clk functions and structs declare the parent_name arrays as > > > 'const char **parent_names' which means the parent name strings > > > are const, but the array itself is not. Use > > > 'const char * const * parent_names' instead which also makes > > > the array const. This allows us to put the parent_name arrays into > > > the __initconst section. > > > > If these are pointer entries are stored, care needs to be > > taken to make sure that the memory isn't discarded or needed > > post init. > > The clock framework makes deep copies of all initialization data > structures. Great. Is/Should that be documented somewhere?