Re: [RFC 3/5] clk: use struct clk only for external API

2014-06-30 Thread Rabin Vincent
On Fri, Jun 27, 2014 at 04:37:45PM -0600, Stephen Warren wrote: > On 06/27/2014 01:57 AM, Tomeu Vizoso wrote: > > +struct clk { > > + struct clk_core clk; > > +}; > > I'm confused why that field isn't a pointer instead. It becomes a pointer in the following patch. It's been a while since I

Re: [RFC 3/5] clk: use struct clk only for external API

2014-06-30 Thread Rabin Vincent
On Fri, Jun 27, 2014 at 04:37:45PM -0600, Stephen Warren wrote: On 06/27/2014 01:57 AM, Tomeu Vizoso wrote: +struct clk { + struct clk_core clk; +}; I'm confused why that field isn't a pointer instead. It becomes a pointer in the following patch. It's been a while since I created

Re: [RFC 3/5] clk: use struct clk only for external API

2014-06-27 Thread Stephen Warren
On 06/27/2014 01:57 AM, Tomeu Vizoso wrote: > From: Rabin Vincent > > In order to provide per-user accounting, this separates the struct clk > used in the common clock framework into two structures 'struct clk_core' > and 'struct clk'. struct clk_core will be used for internal > manipulation

Re: [RFC 3/5] clk: use struct clk only for external API

2014-06-27 Thread Stephen Warren
On 06/27/2014 01:57 AM, Tomeu Vizoso wrote: From: Rabin Vincent rabin.vinc...@stericsson.com In order to provide per-user accounting, this separates the struct clk used in the common clock framework into two structures 'struct clk_core' and 'struct clk'. struct clk_core will be used for