Re: [PATCH 1/4] staging: lustre: fixed signedness of some socklnd params

2017-11-24 Thread Dan Carpenter
On Fri, Nov 24, 2017 at 12:47:21AM +0100, Stefano Manni wrote: > I've made the module param nsched signed because the > ksock_tunables.ksnd_nscheds (the real container) is signed too. Yeah. I know. And it's way more involved and controversial to change ksock_tunables. > > I definitely agree wi

Re: [PATCH 1/4] staging: lustre: fixed signedness of some socklnd params

2017-11-23 Thread Stefano Manni
On Thu, 2017-11-23 at 15:13 +0300, Dan Carpenter wrote: > I've looked through this series and I feel like none of these are > real > bugs.  It's just about type safety and being consistent.  Which are > good > things.  I'm not sure that I like the parts where we make the > variables > signed. > >

Re: [PATCH 1/4] staging: lustre: fixed signedness of some socklnd params

2017-11-23 Thread Dan Carpenter
On Wed, Nov 22, 2017 at 08:38:28PM +0100, Stefano Manni wrote: > diff --git a/drivers/staging/lustre/lnet/klnds/socklnd/socklnd_modparams.c > b/drivers/staging/lustre/lnet/klnds/socklnd/socklnd_modparams.c > index 5663a4c..2ad89ca 100644 > --- a/drivers/staging/lustre/lnet/klnds/socklnd/socklnd_mo

[PATCH 1/4] staging: lustre: fixed signedness of some socklnd params

2017-11-22 Thread Stefano Manni
sparse warnings: warning: incorrect type in assignment (different signedness) expected int *[addressable] [toplevel] [assigned] ksnd_nscheds got unsigned int static [toplevel] * warning: incorrect type in assignment (different signedness) expected int *[addressable] [toplevel] [assigned] ksnd_zc_re