Re: [PATCH 0/2] fix sparse warnings

2021-02-24 Thread karthek
On Wed, Feb 24, 2021 at 06:06:48PM +0300, Dan Carpenter wrote: > On Wed, Feb 24, 2021 at 08:26:41PM +0530, karthek wrote: > > On Sun, Feb 21, 2021 at 09:00:48PM +0530, karthik alapati wrote: > > > the following patches fixes two byte-order issues > > > and fixes these sparse warnings > > > > > >

Re: [PATCH 0/2] fix sparse warnings

2021-02-24 Thread Dan Carpenter
On Wed, Feb 24, 2021 at 08:26:41PM +0530, karthek wrote: > On Sun, Feb 21, 2021 at 09:00:48PM +0530, karthik alapati wrote: > > the following patches fixes two byte-order issues > > and fixes these sparse warnings > > > > > > drivers/staging//wimax/i2400m/op-rfkill.c:89:25: warning: incorrect ty

Re: [PATCH 0/2] fix sparse warnings

2021-02-24 Thread karthek
On Sun, Feb 21, 2021 at 09:00:48PM +0530, karthik alapati wrote: > the following patches fixes two byte-order issues > and fixes these sparse warnings > > > drivers/staging//wimax/i2400m/op-rfkill.c:89:25: warning: incorrect type in > assignment (different base types) > drivers/staging//wimax/i

[PATCH 0/2] fix sparse warnings

2021-02-21 Thread karthik alapati
the following patches fixes two byte-order issues and fixes these sparse warnings drivers/staging//wimax/i2400m/op-rfkill.c:89:25: warning: incorrect type in assignment (different base types) drivers/staging//wimax/i2400m/op-rfkill.c:89:25:expected restricted __le16 [usertype] length drive