From: walter harms <wharms@bfs.de>
To: Colin King <colin.king@canonical.com>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Jiri Slaby <jslaby@suse.com>,
linux-serial@vger.kernel.org, kernel-janitors@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] tty: max3100: remove unused variable rts and remove unused assignment
Date: Thu, 02 Nov 2017 14:14:33 +0000 [thread overview]
Message-ID: <59FB2849.6020108@bfs.de> (raw)
In-Reply-To: <20171102140144.21514-1-colin.king@canonical.com>
Am 02.11.2017 15:01, schrieb Colin King:
> From: Colin Ian King <colin.king@canonical.com>
>
> Variable rts is being assigned but it is never read, hence it can be
> removed. The assignment to param_new to zero is redundant as it is
> being updates a few statements later, so remove this redundant
> assignment. Cleans up two clang warnings:
>
> drivers/tty/serial/max3100.c:277:3: warning: Value stored to 'rts'
> is never read
> drivers/tty/serial/max3100.c:439:2: warning: Value stored to 'param_new'
> is never read
>
> Signed-off-by: Colin Ian King <colin.king@canonical.com>
> ---
> drivers/tty/serial/max3100.c | 4 +---
> 1 file changed, 1 insertion(+), 3 deletions(-)
>
> diff --git a/drivers/tty/serial/max3100.c b/drivers/tty/serial/max3100.c
> index b6b3453e8c1f..f691f3cdb5b1 100644
> --- a/drivers/tty/serial/max3100.c
> +++ b/drivers/tty/serial/max3100.c
> @@ -263,7 +263,7 @@ static void max3100_work(struct work_struct *w)
> struct max3100_port *s = container_of(w, struct max3100_port, work);
> int rxchars;
> u16 tx, rx;
> - int conf, cconf, rts, crts;
> + int conf, cconf, crts;
> struct circ_buf *xmit = &s->port.state->xmit;
>
> dev_dbg(&s->spi->dev, "%s\n", __func__);
> @@ -274,7 +274,6 @@ static void max3100_work(struct work_struct *w)
> conf = s->conf;
> cconf = s->conf_commit;
> s->conf_commit = 0;
> - rts = s->rts;
> crts = s->rts_commit;
> s->rts_commit = 0;
> spin_unlock(&s->conf_lock);
> @@ -436,7 +435,6 @@ max3100_set_termios(struct uart_port *port, struct ktermios *termios,
> dev_dbg(&s->spi->dev, "%s\n", __func__);
>
> cflag = termios->c_cflag;
> - param_new = 0;
> param_mask = 0;
>
> baud = tty_termios_baud_rate(termios);
are you sure ?
based on this code:
https://lxr.missinglinkelectronics.com/linux/drivers/tty/serial/max3100.c
the default case will not set param_new
re,
wh
WARNING: multiple messages have this Message-ID (diff)
From: walter harms <wharms@bfs.de>
To: Colin King <colin.king@canonical.com>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Jiri Slaby <jslaby@suse.com>,
linux-serial@vger.kernel.org, kernel-janitors@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] tty: max3100: remove unused variable rts and remove unused assignment
Date: Thu, 02 Nov 2017 15:14:33 +0100 [thread overview]
Message-ID: <59FB2849.6020108@bfs.de> (raw)
In-Reply-To: <20171102140144.21514-1-colin.king@canonical.com>
Am 02.11.2017 15:01, schrieb Colin King:
> From: Colin Ian King <colin.king@canonical.com>
>
> Variable rts is being assigned but it is never read, hence it can be
> removed. The assignment to param_new to zero is redundant as it is
> being updates a few statements later, so remove this redundant
> assignment. Cleans up two clang warnings:
>
> drivers/tty/serial/max3100.c:277:3: warning: Value stored to 'rts'
> is never read
> drivers/tty/serial/max3100.c:439:2: warning: Value stored to 'param_new'
> is never read
>
> Signed-off-by: Colin Ian King <colin.king@canonical.com>
> ---
> drivers/tty/serial/max3100.c | 4 +---
> 1 file changed, 1 insertion(+), 3 deletions(-)
>
> diff --git a/drivers/tty/serial/max3100.c b/drivers/tty/serial/max3100.c
> index b6b3453e8c1f..f691f3cdb5b1 100644
> --- a/drivers/tty/serial/max3100.c
> +++ b/drivers/tty/serial/max3100.c
> @@ -263,7 +263,7 @@ static void max3100_work(struct work_struct *w)
> struct max3100_port *s = container_of(w, struct max3100_port, work);
> int rxchars;
> u16 tx, rx;
> - int conf, cconf, rts, crts;
> + int conf, cconf, crts;
> struct circ_buf *xmit = &s->port.state->xmit;
>
> dev_dbg(&s->spi->dev, "%s\n", __func__);
> @@ -274,7 +274,6 @@ static void max3100_work(struct work_struct *w)
> conf = s->conf;
> cconf = s->conf_commit;
> s->conf_commit = 0;
> - rts = s->rts;
> crts = s->rts_commit;
> s->rts_commit = 0;
> spin_unlock(&s->conf_lock);
> @@ -436,7 +435,6 @@ max3100_set_termios(struct uart_port *port, struct ktermios *termios,
> dev_dbg(&s->spi->dev, "%s\n", __func__);
>
> cflag = termios->c_cflag;
> - param_new = 0;
> param_mask = 0;
>
> baud = tty_termios_baud_rate(termios);
are you sure ?
based on this code:
https://lxr.missinglinkelectronics.com/linux/drivers/tty/serial/max3100.c
the default case will not set param_new
re,
wh
next prev parent reply other threads:[~2017-11-02 14:14 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-02 14:01 [PATCH] tty: max3100: remove unused variable rts and remove unused assignment Colin King
2017-11-02 14:01 ` Colin King
2017-11-02 14:14 ` walter harms [this message]
2017-11-02 14:14 ` walter harms
2017-11-02 14:21 ` Colin Ian King
2017-11-02 14:21 ` Colin Ian King
2017-11-02 14:22 ` Colin Ian King
2017-11-02 14:22 ` Colin Ian King
2017-11-02 14:36 ` walter harms
2017-11-02 14:36 ` walter harms
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=59FB2849.6020108@bfs.de \
--to=wharms@bfs.de \
--cc=colin.king@canonical.com \
--cc=gregkh@linuxfoundation.org \
--cc=jslaby@suse.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.