lkml.org 
[lkml]   [2021]   [Feb]   [24]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: [PATCH 0/2] fix sparse warnings
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
> > >
> > >
> > > 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
> > > drivers/staging//wimax/i2400m/op-rfkill.c:89:25: got unsigned long
> > > .
> > > drivers/staging//wimax/i2400m/fw.c:514:27: warning: restricted __le32 degrades to integer
> > >
> > >
> > > karthik alapati (2):
> > > staging: wimax/i2400m: fix byte-order issue
> > > staging: wimax/i2400m: convert __le32 type to host byte-order
> > >
> > > drivers/staging/wimax/i2400m/fw.c | 2 +-
> > > drivers/staging/wimax/i2400m/op-rfkill.c | 2 +-
> > > 2 files changed, 2 insertions(+), 2 deletions(-)
> > >
> > > --
> > > 2.30.1
> > >
> > ping?
>
> The merge window is open so no one is merging these types of fixes now.
> Wait until -rc1 is out, and then give the maintainer two weeks to look
> at your patch and get back to you.
>
> regards,
> dan carpenter
>
thanks dan, Got it.

\
 
 \ /
  Last update: 2021-02-24 17:17    [W:0.160 / U:0.196 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site