Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
Date:   Fri, 12 Feb 2021 22:47:04 +0530
From:   Anirudh Rayabharam <mail@anirudhrb.com>
To:     Greg KH <gregkh@linuxfoundation.org>
Cc:     devel@driverdev.osuosl.org, arnd@arndb.de,
        linux-kernel@vger.kernel.org, colin.king@canonical.com,
        kuba@kernel.org, johannes@sipsolutions.net, lee.jones@linaro.org
Message-ID: <YCa4EBQHw02BeQ4B@anirudhrb.com>
Subject: Re: [PATCH] staging: wimax/i2400m: fix some byte order issues found
 by sparse
References: <20210211202908.4604-1-mail@anirudhrb.com>
 <YCWVD34rU5Lu71/S@kroah.com>
 <YCaRAYjiz0TJH+4L@anirudhrb.com>
 <YCaT/qLci4ap1grf@kroah.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
In-Reply-To: <YCaT/qLci4ap1grf@kroah.com>
Precedence: bulk

On Fri, Feb 12, 2021 at 03:43:10PM +0100, Greg KH wrote:
> On Fri, Feb 12, 2021 at 08:00:25PM +0530, Anirudh Rayabharam wrote:
> > On Thu, Feb 11, 2021 at 09:35:27PM +0100, Greg KH wrote:
> > > On Fri, Feb 12, 2021 at 01:59:08AM +0530, Anirudh Rayabharam wrote:
> > > > Fix sparse byte-order warnings in the i2400m_bm_cmd_prepare()
> > > > function:
> > > >=20
> > > > wimax/i2400m/fw.c:194:36: warning: restricted __le32 degrades to in=
teger
> > > > wimax/i2400m/fw.c:195:34: warning: invalid assignment: +=3D
> > > > wimax/i2400m/fw.c:195:34:    left side has type unsigned int
> > > > wimax/i2400m/fw.c:195:34:    right side has type restricted __le32
> > > > wimax/i2400m/fw.c:196:32: warning: restricted __le32 degrades to in=
teger
> > > > wimax/i2400m/fw.c:196:47: warning: restricted __le32 degrades to in=
teger
> > > > wimax/i2400m/fw.c:196:66: warning: restricted __le32 degrades to in=
teger
> > > >=20
> > > > Signed-off-by: Anirudh Rayabharam <mail@anirudhrb.com>
> > > > ---
> > > >  drivers/staging/wimax/i2400m/fw.c | 14 +++++++++-----
> > > >  1 file changed, 9 insertions(+), 5 deletions(-)
> > > >=20
> > > > diff --git a/drivers/staging/wimax/i2400m/fw.c b/drivers/staging/wi=
max/i2400m/fw.c
> > > > index b2fd4bd2c5f9..bce651a6b543 100644
> > > > --- a/drivers/staging/wimax/i2400m/fw.c
> > > > +++ b/drivers/staging/wimax/i2400m/fw.c
> > > > @@ -189,12 +189,16 @@ void i2400m_bm_cmd_prepare(struct i2400m_boot=
rom_header *cmd)
> > > >  {
> > > >  =09if (i2400m_brh_get_use_checksum(cmd)) {
> > > >  =09=09int i;
> > > > -=09=09u32 checksum =3D 0;
> > > > +=09=09__le32 checksum =3D 0;
> > >=20
> > > __le32 is only for when the data crosses the kernel/user boundry, jus=
t
> > > use le32 in the kernel for stuff like this.
> > >=20
> > But that throws a compile error.
>=20
> What error?

drivers/staging/wimax/i2400m/fw.c:192:3: error: unknown type name
=E2=80=98le32=E2=80=99; did you mean =E2=80=98__le32=E2=80=99?

=09- Anirudh