[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20210828084528.gbkqcgqaaf3adyb7@xps.yggdrasil>
Date: Sat, 28 Aug 2021 14:15:28 +0530
From: Aakash Hemadri <aakashhemadri123@...il.com>
To: David Laight <David.Laight@...lab.com>
Cc: Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Larry Finger <Larry.Finger@...inger.net>,
Phillip Potter <phil@...lpotter.co.uk>,
"linux-staging@...ts.linux.dev" <linux-staging@...ts.linux.dev>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v4 3/5] staging: r8188eu: incorrect type in
csum_ipv6_magic
On 21/08/25 09:23AM, David Laight wrote:
> From: Aakash Hemadri
> > Sent: 23 August 2021 18:00
> >
> > Fix sparse warning:
> > > rtw_br_ext.c:771:84: got restricted __be16 [usertype] payload_len
> > > rtw_br_ext.c:773:110: warning: incorrect type in argument 2
> > (different base types)
> > > rtw_br_ext.c:773:110: expected int len
> > > rtw_br_ext.c:773:110: got restricted __be16 [usertype] payload_len
> >
> > csum_ipv6_magic and csum_partial expect int len not __be16, use
> > be16_to_cpu()
>
> This is a behaviour change on LE systems.
> Even if you are testing on BE the commit message should say
> that it fixes the length passed to the checksum code and
> was detected by sparse.
>
Thanks for the note david.
-Aakash
Powered by blists - more mailing lists