From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S933465AbdKBOOj (ORCPT ); Thu, 2 Nov 2017 10:14:39 -0400 Received: from mx02-sz.bfs.de ([194.94.69.103]:17437 "EHLO mx02-sz.bfs.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S933034AbdKBOOh (ORCPT ); Thu, 2 Nov 2017 10:14:37 -0400 Message-ID: <59FB2849.6020108@bfs.de> Date: Thu, 02 Nov 2017 15:14:33 +0100 From: walter harms Reply-To: wharms@bfs.de User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; de; rv:1.9.1.16) Gecko/20101125 SUSE/3.0.11 Thunderbird/3.0.11 MIME-Version: 1.0 To: Colin King CC: Greg Kroah-Hartman , Jiri Slaby , 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 References: <20171102140144.21514-1-colin.king@canonical.com> In-Reply-To: <20171102140144.21514-1-colin.king@canonical.com> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Am 02.11.2017 15:01, schrieb Colin King: > From: Colin Ian King > > 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 > --- > 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