Re: [PATCH] cpufreq: make table sentinal macros unsigned to match use

2014-07-21 Thread Brian W Hart
On Fri, Jul 18, 2014 at 03:20:49AM +0200, Rafael J. Wysocki wrote: > On Friday, July 11, 2014 05:06:30 PM Brian W Hart wrote: > > On Mon, Jun 30, 2014 at 10:25:20AM +0530, Viresh Kumar wrote: > > > On 28 June 2014 02:39, Brian W Hart wrote: > > > > Commit 5eeaf1f18973 (cpufreq: Fix build error on

Re: [PATCH] cpufreq: make table sentinal macros unsigned to match use

2014-07-17 Thread Rafael J. Wysocki
On Friday, July 11, 2014 05:06:30 PM Brian W Hart wrote: > On Mon, Jun 30, 2014 at 10:25:20AM +0530, Viresh Kumar wrote: > > On 28 June 2014 02:39, Brian W Hart wrote: > > > Commit 5eeaf1f18973 (cpufreq: Fix build error on some platforms that > > > use cpufreq_for_each_*) moved function cpufreq_ne

Re: [PATCH] cpufreq: make table sentinal macros unsigned to match use

2014-07-11 Thread Brian W Hart
On Mon, Jun 30, 2014 at 10:25:20AM +0530, Viresh Kumar wrote: > On 28 June 2014 02:39, Brian W Hart wrote: > > Commit 5eeaf1f18973 (cpufreq: Fix build error on some platforms that > > use cpufreq_for_each_*) moved function cpufreq_next_valid() to a public > > header. Warnings are now generated wh

Re: [PATCH] cpufreq: make table sentinal macros unsigned to match use

2014-06-29 Thread Viresh Kumar
On 28 June 2014 02:39, Brian W Hart wrote: > Commit 5eeaf1f18973 (cpufreq: Fix build error on some platforms that > use cpufreq_for_each_*) moved function cpufreq_next_valid() to a public > header. Warnings are now generated when objects including that header > are built with -Wsign-compare (as a

Re: [PATCH] cpufreq: make table sentinal macros unsigned to match use

2014-06-27 Thread Simon Horman
On Fri, Jun 27, 2014 at 04:09:39PM -0500, Brian W Hart wrote: > Commit 5eeaf1f18973 (cpufreq: Fix build error on some platforms that > use cpufreq_for_each_*) moved function cpufreq_next_valid() to a public > header. Warnings are now generated when objects including that header > are built with -W

[PATCH] cpufreq: make table sentinal macros unsigned to match use

2014-06-27 Thread Brian W Hart
Commit 5eeaf1f18973 (cpufreq: Fix build error on some platforms that use cpufreq_for_each_*) moved function cpufreq_next_valid() to a public header. Warnings are now generated when objects including that header are built with -Wsign-compare (as an out-of-tree module might be): .../include/linux/c