Re: [PATCH v2] input: misc: yealink: define packet offset __be16 instead of u16

2017-04-10 Thread Dmitry Torokhov
On Mon, Apr 10, 2017 at 05:00:22PM +0200, Martin Kepplinger wrote: > sparse says > > warning: incorrect type in assignment (different base types) > expected unsigned short [unsigned] [usertype] offset > got restricted __be16 [usertype] > > for every usage of cpu_to_be16 in yealink.c.

Re: [PATCH v2] input: misc: yealink: define packet offset __be16 instead of u16

2017-04-10 Thread Dmitry Torokhov
On Mon, Apr 10, 2017 at 05:00:22PM +0200, Martin Kepplinger wrote: > sparse says > > warning: incorrect type in assignment (different base types) > expected unsigned short [unsigned] [usertype] offset > got restricted __be16 [usertype] > > for every usage of cpu_to_be16 in yealink.c.

[PATCH v2] input: misc: yealink: define packet offset __be16 instead of u16

2017-04-10 Thread Martin Kepplinger
sparse says warning: incorrect type in assignment (different base types) expected unsigned short [unsigned] [usertype] offset got restricted __be16 [usertype] for every usage of cpu_to_be16 in yealink.c. Defining it __be16 in the first place shouldn't hurt. Signed-off-by: Martin

[PATCH v2] input: misc: yealink: define packet offset __be16 instead of u16

2017-04-10 Thread Martin Kepplinger
sparse says warning: incorrect type in assignment (different base types) expected unsigned short [unsigned] [usertype] offset got restricted __be16 [usertype] for every usage of cpu_to_be16 in yealink.c. Defining it __be16 in the first place shouldn't hurt. Signed-off-by: Martin