From: Johan Hovold <johan@kernel.org>
To: YueHaibing <yuehaibing@huawei.com>
Cc: Johan Hovold <johan@kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-usb@vger.kernel.org, kernel-janitors@vger.kernel.org
Subject: [-next] USB: cypress_m8: remove set but not used variables 'actual_size, iflag'
Date: Sun, 30 Sep 2018 18:02:24 +0200 [thread overview]
Message-ID: <20180930160224.GG3332@localhost> (raw)
On Sat, Sep 29, 2018 at 09:54:03AM +0000, YueHaibing wrote:
> Fixes gcc '-Wunused-but-set-variable' warning:
>
> drivers/usb/serial/cypress_m8.c: In function 'cypress_send':
> drivers/usb/serial/cypress_m8.c:689:33: warning:
> variable 'actual_size' set but not used [-Wunused-but-set-variable]
>
> drivers/usb/serial/cypress_m8.c: In function 'cypress_set_termios':
> drivers/usb/serial/cypress_m8.c:866:18: warning:
> variable 'iflag' set but not used [-Wunused-but-set-variable]
>
> Signed-off-by: YueHaibing <yuehaibing@huawei.com>
> ---
> drivers/usb/serial/cypress_m8.c | 11 ++---------
> 1 file changed, 2 insertions(+), 9 deletions(-)
>
> diff --git a/drivers/usb/serial/cypress_m8.c b/drivers/usb/serial/cypress_m8.c
> index 31c6091..98dff12 100644
> --- a/drivers/usb/serial/cypress_m8.c
> +++ b/drivers/usb/serial/cypress_m8.c
> @@ -686,7 +686,7 @@ static int cypress_write(struct tty_struct *tty, struct usb_serial_port *port,
>
> static void cypress_send(struct usb_serial_port *port)
> {
> - int count = 0, result, offset, actual_size;
> + int count = 0, result, offset;
> struct cypress_private *priv = usb_get_serial_port_data(port);
> struct device *dev = &port->dev;
> unsigned long flags;
> @@ -758,12 +758,6 @@ static void cypress_send(struct usb_serial_port *port)
> priv->write_urb_in_use = 1;
> spin_unlock_irqrestore(&priv->lock, flags);
>
> - if (priv->cmd_ctrl)
> - actual_size = 1;
> - else
> - actual_size = count +
> - (priv->pkt_fmt == packet_format_1 ? 2 : 1);
> -
This looks like we have a bug in the driver, and sure enough we do.
Commit 9aa8dae7b1fa ("cypress_m8: use usb_fill_int_urb where
appropriate") incorrectly started setting the transfer length to the
size of the buffer.
I've prepared a fix to this.
> usb_serial_debug_data(dev, __func__, port->interrupt_out_size,
> port->interrupt_out_urb->transfer_buffer);
>
> @@ -863,7 +857,7 @@ static void cypress_set_termios(struct tty_struct *tty,
> struct cypress_private *priv = usb_get_serial_port_data(port);
> struct device *dev = &port->dev;
> int data_bits, stop_bits, parity_type, parity_enable;
> - unsigned cflag, iflag;
> + unsigned int cflag;
> unsigned long flags;
> __u8 oldlines;
> int linechange = 0;
> @@ -899,7 +893,6 @@ static void cypress_set_termios(struct tty_struct *tty,
> tty->termios.c_cflag &= ~(CMSPAR|CRTSCTS);
>
> cflag = tty->termios.c_cflag;
> - iflag = tty->termios.c_iflag;
>
> /* check if there are new settings */
> if (old_termios) {
Would you mind resending just this chunk as a v2?
Thanks,
Johan
next reply other threads:[~2018-09-30 16:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-30 16:02 Johan Hovold [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-10-04 1:35 [-next] USB: cypress_m8: remove set but not used variables 'actual_size, iflag' YueHaibing
2018-10-01 7:19 Dan Carpenter
2018-09-29 9:54 YueHaibing
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=20180930160224.GG3332@localhost \
--to=johan@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=yuehaibing@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;
as well as URLs for NNTP newsgroup(s).