Re: [ 016/173] use clamp_t in UNAME26 fix

2012-12-29 Thread Jonathan Nieder
Ben Hutchings wrote: > On Sat, 2012-12-29 at 00:07 -0800, Jonathan Nieder wrote: >> Ben Hutchings wrote: >>> The min/max call needed to have explicit types on some architectures >>> (e.g. mn10300). Use clamp_t instead to avoid the warning: >>> >>> kernel/sys.c: In function 'override_release': >>

Re: [ 016/173] use clamp_t in UNAME26 fix

2012-12-29 Thread Ben Hutchings
On Sat, 2012-12-29 at 00:07 -0800, Jonathan Nieder wrote: > Ben Hutchings wrote: > > > The min/max call needed to have explicit types on some architectures > > (e.g. mn10300). Use clamp_t instead to avoid the warning: > > > > kernel/sys.c: In function 'override_release': > > kernel/sys.c:1287

Re: [ 016/173] use clamp_t in UNAME26 fix

2012-12-29 Thread Jonathan Nieder
Ben Hutchings wrote: > The min/max call needed to have explicit types on some architectures > (e.g. mn10300). Use clamp_t instead to avoid the warning: > > kernel/sys.c: In function 'override_release': > kernel/sys.c:1287:10: warning: comparison of distinct pointer types lacks a > cast [enab

[ 016/173] use clamp_t in UNAME26 fix

2012-12-28 Thread Ben Hutchings
3.2-stable review patch. If anyone has any objections, please let me know. -- From: Kees Cook commit 31fd84b95eb211d5db460a1dda85e004800a7b52 upstream. The min/max call needed to have explicit types on some architectures (e.g. mn10300). Use clamp_t instead to avoid the warning