Re: [Outreachy kernel] Re: [PATCH v3 0/5] Fixed compilation error

2017-03-03 Thread SIMRAN SINGHAL
On Fri, Mar 3, 2017 at 9:45 PM, Julia Lawall wrote: > > > On Fri, 3 Mar 2017, SIMRAN SINGHAL wrote: > >> On Fri, Mar 3, 2017 at 9:20 PM, Joe Perches wrote: >> > On Fri, 2017-03-03 at 17:05 +0530, simran singhal wrote: >> >> Fixed compilation warning in

Re: [Outreachy kernel] Re: [PATCH v3 0/5] Fixed compilation error

2017-03-03 Thread SIMRAN SINGHAL
On Fri, Mar 3, 2017 at 9:45 PM, Julia Lawall wrote: > > > On Fri, 3 Mar 2017, SIMRAN SINGHAL wrote: > >> On Fri, Mar 3, 2017 at 9:20 PM, Joe Perches wrote: >> > On Fri, 2017-03-03 at 17:05 +0530, simran singhal wrote: >> >> Fixed compilation warning in lustre/lustre/llite/range_lock.c >> > >> >

Re: [Outreachy kernel] Re: [PATCH v3 0/5] Fixed compilation error

2017-03-03 Thread Julia Lawall
On Fri, 3 Mar 2017, SIMRAN SINGHAL wrote: > On Fri, Mar 3, 2017 at 9:20 PM, Joe Perches wrote: > > On Fri, 2017-03-03 at 17:05 +0530, simran singhal wrote: > >> Fixed compilation warning in lustre/lustre/llite/range_lock.c > > > > Really? What compilation warning was

Re: [Outreachy kernel] Re: [PATCH v3 0/5] Fixed compilation error

2017-03-03 Thread Julia Lawall
On Fri, 3 Mar 2017, SIMRAN SINGHAL wrote: > On Fri, Mar 3, 2017 at 9:20 PM, Joe Perches wrote: > > On Fri, 2017-03-03 at 17:05 +0530, simran singhal wrote: > >> Fixed compilation warning in lustre/lustre/llite/range_lock.c > > > > Really? What compilation warning was removed? > > CC [M]