mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Muhammad Usama Anjum <musamaanjum@gmail.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: lee.jones@linaro.org, johannes@sipsolutions.net, arnd@arndb.de,
	kuba@kernel.org, gustavoars@kernel.org, wanghai38@huawei.com,
	devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org,
	musamaanjum@gmail.com
Subject: Re: [PATCH] staging: wimax/i2400m: don't change the endianness of one byte variable
Date: Thu, 18 Feb 2021 14:54:28 +0500	[thread overview]
Message-ID: <f44c413467df665de9bd1ecbee6d76222518c0c7.camel@gmail.com> (raw)
In-Reply-To: <YC42ECUUtX1Ah90v@kroah.com>

On Thu, 2021-02-18 at 10:40 +0100, Greg KH wrote:
> On Thu, Feb 18, 2021 at 02:21:54PM +0500, Muhammad Usama Anjum wrote:
> > It is wrong to change the endianness of a variable which has just one
> > byte size.
> > 
> > Sparse warnings fixed:
> > drivers/staging//wimax/i2400m/control.c:452:17: warning: cast to restricted __le32
> > drivers/staging//wimax/i2400m/control.c:452:17: warning: cast to restricted __le32
> > drivers/staging//wimax/i2400m/op-rfkill.c:159:14: warning: cast to restricted __le32
> > drivers/staging//wimax/i2400m/op-rfkill.c:160:14: warning: cast to restricted __le32
> > 
> > Signed-off-by: Muhammad Usama Anjum <musamaanjum@gmail.com>
> > ---
> >  drivers/staging/wimax/i2400m/control.c   | 4 ++--
> >  drivers/staging/wimax/i2400m/op-rfkill.c | 4 ++--
> >  2 files changed, 4 insertions(+), 4 deletions(-)
> > 
> > diff --git a/drivers/staging/wimax/i2400m/control.c b/drivers/staging/wimax/i2400m/control.c
> > index 1e270b2101e8..b6b2788af162 100644
> > --- a/drivers/staging/wimax/i2400m/control.c
> > +++ b/drivers/staging/wimax/i2400m/control.c
> > @@ -452,8 +452,8 @@ void i2400m_report_state_parse_tlv(struct i2400m *i2400m,
> >  		d_printf(2, dev, "%s: RF status TLV "
> >  			 "found (0x%04x), sw 0x%02x hw 0x%02x\n",
> >  			 tag, I2400M_TLV_RF_STATUS,
> > -			 le32_to_cpu(rfss->sw_rf_switch),
> > -			 le32_to_cpu(rfss->hw_rf_switch));
> > +			 rfss->sw_rf_switch,
> > +			 rfss->hw_rf_switch);
> 
> What do you mean by "one byte"?  This is a le32 sized variable, right?
> If not, why isn't the le32_to_cpu() call complaining?

These two variables are of type _u8, one byte. 
	__u8 sw_rf_switch;
	__u8 hw_rf_switch;
They aren't of type __le32. le32_to_cpu() macro should have
complained. But it isn't complaining. It seems like whatever we pass
to this macro, it casts it to __le32 forcefully (it seems like wrong).
So we'll never get any complain from this macro directly. But we are
getting complain from the sparse.

For big endian:
#define __le32_to_cpu(x) __swab32((__force __u32)(__le32)(x))
For little endian:
#define __le32_to_cpu(x) ((__force __u32)(__le32)(x))

> >  		i2400m_report_tlv_rf_switches_status(i2400m, rfss);
> >  	}
> >  	if (0 == i2400m_tlv_match(tlv, I2400M_TLV_MEDIA_STATUS, sizeof(*ms))) {
> > diff --git a/drivers/staging/wimax/i2400m/op-rfkill.c b/drivers/staging/wimax/i2400m/op-rfkill.c
> > index fbddf2e18c14..a159808f0ec2 100644
> > --- a/drivers/staging/wimax/i2400m/op-rfkill.c
> > +++ b/drivers/staging/wimax/i2400m/op-rfkill.c
> > @@ -156,8 +156,8 @@ void i2400m_report_tlv_rf_switches_status(
> >  	enum i2400m_rf_switch_status hw, sw;
> >  	enum wimax_st wimax_state;
> >  
> > -	sw = le32_to_cpu(rfss->sw_rf_switch);
> > -	hw = le32_to_cpu(rfss->hw_rf_switch);
> > +	sw = rfss->sw_rf_switch;
> > +	hw = rfss->hw_rf_switch;
> 
> Same here.

Same here.

> thanks,
> 
> greg k-h


  reply	other threads:[~2021-02-18 11:08 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-18  9:21 Muhammad Usama Anjum
2021-02-18  9:40 ` Greg KH
2021-02-18  9:54   ` Muhammad Usama Anjum [this message]
2021-02-18 18:32     ` Arnd Bergmann

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=f44c413467df665de9bd1ecbee6d76222518c0c7.camel@gmail.com \
    --to=musamaanjum@gmail.com \
    --cc=arnd@arndb.de \
    --cc=devel@driverdev.osuosl.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=gustavoars@kernel.org \
    --cc=johannes@sipsolutions.net \
    --cc=kuba@kernel.org \
    --cc=lee.jones@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=wanghai38@huawei.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®