Re: [PATCH v5 0/7] Per-user clock constraints

On 31 October 2014 12:33, Peter De Schrijver wrote: > On Thu, Oct 30, 2014 at 11:48:26AM +0100, Tomeu Vizoso wrote: >> Hello, >> >> this fifth version of the series has just one change, suggested by Stephen: Hi Mike, how is this looking for 3.19? Regards, Tomeu >> * Initialize

Re: [PATCH v5 0/7] Per-user clock constraints

On 31 October 2014 12:33, Peter De Schrijver pdeschrij...@nvidia.com wrote: On Thu, Oct 30, 2014 at 11:48:26AM +0100, Tomeu Vizoso wrote: Hello, this fifth version of the series has just one change, suggested by Stephen: Hi Mike, how is this looking for 3.19? Regards, Tomeu * Initialize

Re: [PATCH v5 0/7] Per-user clock constraints

On Thu, Oct 30, 2014 at 11:48:26AM +0100, Tomeu Vizoso wrote: > Hello, > > this fifth version of the series has just one change, suggested by Stephen: > > * Initialize clk.ceiling_constraint to ULONG_MAX and warn about new floor > constraints being higher than the existing ceiling. > > The

Re: [PATCH v5 0/7] Per-user clock constraints

On Thu, Oct 30, 2014 at 11:48:26AM +0100, Tomeu Vizoso wrote: Hello, this fifth version of the series has just one change, suggested by Stephen: * Initialize clk.ceiling_constraint to ULONG_MAX and warn about new floor constraints being higher than the existing ceiling. The first five

[PATCH v5 0/7] Per-user clock constraints

Hello, this fifth version of the series has just one change, suggested by Stephen: * Initialize clk.ceiling_constraint to ULONG_MAX and warn about new floor constraints being higher than the existing ceiling. The first five patches are just cleanups that should be desirable on their own, and

[PATCH v5 0/7] Per-user clock constraints

Hello, this fifth version of the series has just one change, suggested by Stephen: * Initialize clk.ceiling_constraint to ULONG_MAX and warn about new floor constraints being higher than the existing ceiling. The first five patches are just cleanups that should be desirable on their own, and