linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Fabio M. De Francesco" <fmdefrancesco@gmail.com>
To: Dan Carpenter <dan.carpenter@oracle.com>
Cc: Larry Finger <Larry.Finger@lwfinger.net>,
	Phillip Potter <phil@philpotter.co.uk>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Pavel Skripkin <paskripkin@gmail.com>,
	linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org,
	David Laight <david.Laight@aculab.com>
Subject: Re: [PATCH v6 16/19] staging: r8188eu: Clean up rtw_read*() and rtw_write*()
Date: Thu, 16 Sep 2021 14:14:14 +0200	[thread overview]
Message-ID: <1797501.xtDa3BoUpI@localhost.localdomain> (raw)
In-Reply-To: <20210916113606.GJ2116@kadam>

On Thursday, September 16, 2021 1:36:06 PM CEST Dan Carpenter wrote:
> On Wed, Sep 15, 2021 at 11:11:00PM +0200, Fabio M. De Francesco wrote:
> > Clean up rtw_read{8,16,32}() and rtw_write{8,16,32,N}() in 
usb_ops_linux.c.
> > 
> 
> It would be good to know what you did more specifically.
> 
> 1) Rename variables:
> 	pio_priv => io_priv
> 	pintfhdl => intfhdl
> 	wvalue => address.
> 2) Remove unnecessary casts.
> 3) Fix types.  Use __le16 instead of __le32.

Dear Dan,

I'm sorry for missing that. :( 

Now I remember that you asked for this specifications at least once (if not 
twice). I'll redo the commit message and add the list above in v7. I guess 
that I have to do the same in 15/19.

> The last one is a small KASan bug fix.  So good job on that.

Thanks (even if I don't yet know anything about KASan).

> > Co-developed-by: Pavel Skripkin <paskripkin@gmail.com>
> > Signed-off-by: Pavel Skripkin <paskripkin@gmail.com>
> > Signed-off-by: Fabio M. De Francesco <fmdefrancesco@gmail.com>
> > ---
> >  drivers/staging/r8188eu/hal/usb_ops_linux.c | 68 ++++++++++-----------
> >  1 file changed, 34 insertions(+), 34 deletions(-)
> > 
> > diff --git a/drivers/staging/r8188eu/hal/usb_ops_linux.c b/drivers/
staging/r8188eu/hal/usb_ops_linux.c
> > index 2098ce935dc0..d87da84eca07 100644
> > --- a/drivers/staging/r8188eu/hal/usb_ops_linux.c
> > +++ b/drivers/staging/r8188eu/hal/usb_ops_linux.c
> > @@ -91,91 +91,91 @@ static int usbctrl_vendorreq(struct intf_hdl 
*intfhdl, u16 value, void *data, u1
> >  
> >  u8 rtw_read8(struct adapter *adapter, u32 addr)
> >  {
> > -	struct io_priv *pio_priv = &adapter->iopriv;
> > -	struct intf_hdl *pintfhdl = &pio_priv->intf;
> > -	u16 wvalue = (u16)(addr & 0x0000ffff);
> > +	struct io_priv *io_priv = &adapter->iopriv;
> > +	struct intf_hdl *intfhdl = &io_priv->intf;
> > +	u16 address = addr & 0xffff;
> >  	u8 data;
> > -
> 
> Deleting this line introduces a checkpatch warning.

I didn't notice the warning. This too will be fixed in v7.

> > -	usbctrl_vendorreq(pintfhdl, wvalue, &data, 1, 
REALTEK_USB_VENQT_READ);
> > +	usbctrl_vendorreq(intfhdl, address, &data, 1, 
REALTEK_USB_VENQT_READ);
> >  
> >  	return data;
> >  }
> >  
> >  u16 rtw_read16(struct adapter *adapter, u32 addr)
> >  {
> > -	struct io_priv *pio_priv = &adapter->iopriv;
> > -	struct intf_hdl *pintfhdl = &pio_priv->intf;
> > -	u16 wvalue = (u16)(addr & 0x0000ffff);
> > -	__le32 data;
> > +	struct io_priv *io_priv = &adapter->iopriv;
> > +	struct intf_hdl *intfhdl = &io_priv->intf;
> > +	u16 address = addr & 0xffff;
> > +	__le16 data;
> >  
> > -	usbctrl_vendorreq(pintfhdl, wvalue, &data, 2, 
REALTEK_USB_VENQT_READ);
> > +	usbctrl_vendorreq(intfhdl, address, &data, 2, 
REALTEK_USB_VENQT_READ);
> >  
> > -	return (u16)(le32_to_cpu(data) & 0xffff);
> > +	return le16_to_cpu(data);
> 
> The last two bytes of "data" are not initialized.  I do not think that
> will cause a bug on either endian type of system during runtime but I
> this that KASan will catch it and complain.

I don't want to add mistakes on mistakes. I guess that you are talking of the 
same fix you wrote above and that "return le16_to_cpu(data);" is correct.
Am I interpreting your words in the correct way?
 
> >  }
> >  
> >  u32 rtw_read32(struct adapter *adapter, u32 addr)
> >  {
> > -	struct io_priv *pio_priv = &adapter->iopriv;
> > -	struct intf_hdl *pintfhdl = &pio_priv->intf;
> > -	u16 wvalue = (u16)(addr & 0x0000ffff);
> > +	struct io_priv *io_priv = &adapter->iopriv;
> > +	struct intf_hdl *intfhdl = &io_priv->intf;
> > +	u16 address = addr & 0xffff;
> >  	__le32 data;
> >  
> > -	usbctrl_vendorreq(pintfhdl, wvalue, &data, 4, 
REALTEK_USB_VENQT_READ);
> > +	usbctrl_vendorreq(intfhdl, address, &data, 4, 
REALTEK_USB_VENQT_READ);
> >  
> >  	return le32_to_cpu(data);
> >  }
> >  
> >  int rtw_write8(struct adapter *adapter, u32 addr, u8 val)
> >  {
> > -	struct io_priv *pio_priv = &adapter->iopriv;
> > -	struct intf_hdl *pintfhdl = &pio_priv->intf;
> > -	u16 wvalue = (u16)(addr & 0x0000ffff);
> > +	struct io_priv *io_priv = &adapter->iopriv;
> > +	struct intf_hdl *intfhdl = &io_priv->intf;
> > +	u16 address = addr & 0xffff;
> >  	int ret;
> >  
> > -	ret = usbctrl_vendorreq(pintfhdl, wvalue, &val, 1, 
REALTEK_USB_VENQT_WRITE);
> > +	ret = usbctrl_vendorreq(intfhdl, address, &val, 1, 
REALTEK_USB_VENQT_WRITE);
> >  
> >  	return RTW_STATUS_CODE(ret);
> >  }
> >  
> >  int rtw_write16(struct adapter *adapter, u32 addr, u16 val)
> >  {
> > -	struct io_priv *pio_priv = &adapter->iopriv;
> > -	struct intf_hdl *pintfhdl = &pio_priv->intf;
> > -	u16 wvalue = (u16)(addr & 0x0000ffff);
> > -	__le32 data = cpu_to_le32(val & 0x0000ffff);
> > +	struct io_priv *io_priv = &adapter->iopriv;
> > +	struct intf_hdl *intfhdl = &io_priv->intf;
> > +	__le16 data = cpu_to_le16(val);
> 
> This is the other interesting change.  I think the original code works
> though.

Here too, I'm a bit confused... Do yo prefer the original code or you're 
saying that, although the original code works fine, I made the correct choice 
in changing it? Can you please confirm?

> 
> > +	u16 address = addr & 0xffff;
> >  	int ret;
> >  
> > -	ret = usbctrl_vendorreq(pintfhdl, wvalue, &data, 2, 
REALTEK_USB_VENQT_WRITE);
> > +	ret = usbctrl_vendorreq(intfhdl, address, &data, 2, 
REALTEK_USB_VENQT_WRITE);
> >  
> >  	return RTW_STATUS_CODE(ret);
> >  }
> 
> regards,
> dan carpenter
> 
> 

Regards,

Fabio



  reply	other threads:[~2021-09-16 12:14 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-15 21:10 [PATCH v6 00/19] staging: r8188eu: Shorten and simplify calls chains Fabio M. De Francesco
2021-09-15 21:10 ` [PATCH v6 01/19] staging: r8188eu: remove usb_{read,write}_mem() Fabio M. De Francesco
2021-09-15 21:10 ` [PATCH v6 02/19] staging: r8188eu: remove the helpers of rtw_read8() Fabio M. De Francesco
2021-09-15 21:10 ` [PATCH v6 03/19] staging: r8188eu: remove the helpers of rtw_read16() Fabio M. De Francesco
2021-09-15 21:10 ` [PATCH v6 04/19] staging: r8188eu: remove the helpers of rtw_read32() Fabio M. De Francesco
2021-09-15 21:10 ` [PATCH v6 05/19] staging: r8188eu: remove the helpers of usb_write8() Fabio M. De Francesco
2021-09-15 21:10 ` [PATCH v6 06/19] staging: r8188eu: remove the helpers of usb_write16() Fabio M. De Francesco
2021-09-15 21:10 ` [PATCH v6 07/19] staging: r8188eu: remove the helpers of usb_write32() Fabio M. De Francesco
2021-09-15 21:10 ` [PATCH v6 08/19] staging: r8188eu: remove the helpers of usb_writeN() Fabio M. De Francesco
2021-09-15 21:10 ` [PATCH v6 09/19] staging: r8188eu: remove the helpers of usb_read_port() Fabio M. De Francesco
2021-09-15 21:10 ` [PATCH v6 10/19] staging: r8188eu: remove the helpers of usb_write_port() Fabio M. De Francesco
2021-09-15 21:10 ` [PATCH v6 11/19] staging: r8188eu: remove the helpers of usb_read_port_cancel() Fabio M. De Francesco
2021-09-15 21:10 ` [PATCH v6 12/19] staging: r8188eu: remove the helpers of usb_write_port_cancel() Fabio M. De Francesco
2021-09-15 21:10 ` [PATCH v6 13/19] staging: r8188eu: remove core/rtw_io.c Fabio M. De Francesco
2021-09-15 21:10 ` [PATCH v6 14/19] staging: remove struct _io_ops Fabio M. De Francesco
2021-09-16 12:52   ` Dan Carpenter
2021-09-16 13:28     ` Fabio M. De Francesco
2021-09-16 13:52   ` Greg Kroah-Hartman
2021-09-15 21:10 ` [PATCH v6 15/19] staging: r8188eu: Clean up usbctrl_vendorreq() Fabio M. De Francesco
2021-09-15 21:11 ` [PATCH v6 16/19] staging: r8188eu: Clean up rtw_read*() and rtw_write*() Fabio M. De Francesco
2021-09-16 11:36   ` Dan Carpenter
2021-09-16 12:14     ` Fabio M. De Francesco [this message]
2021-09-16 12:50       ` Dan Carpenter
2021-09-15 21:11 ` [PATCH v6 17/19] staging: r8188eu: Shorten calls chains of rtw_read*() Fabio M. De Francesco
2021-09-15 21:11 ` [PATCH v6 18/19] staging: r8188eu: Shorten calls chains of rtw_write*() Fabio M. De Francesco
2021-09-15 21:11 ` [PATCH v6 19/19] staging: r8188eu: remove shared buffer for USB requests Fabio M. De Francesco
2021-09-16 11:49   ` Dan Carpenter
2021-09-16 11:51     ` Pavel Skripkin

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=1797501.xtDa3BoUpI@localhost.localdomain \
    --to=fmdefrancesco@gmail.com \
    --cc=Larry.Finger@lwfinger.net \
    --cc=dan.carpenter@oracle.com \
    --cc=david.Laight@aculab.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-staging@lists.linux.dev \
    --cc=paskripkin@gmail.com \
    --cc=phil@philpotter.co.uk \
    /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;
as well as URLs for NNTP newsgroup(s).