From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Dan Carpenter <dan.carpenter@oracle.com>
Cc: Colin King <colin.king@canonical.com>,
Arnd Bergmann <arnd@arndb.de>,
kernel-janitors@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] drivers/misc: ti-st: remove redundant assignment to variable i
Date: Sat, 11 Jan 2020 20:01:36 +0000 [thread overview]
Message-ID: <20200111200136.GC438314@kroah.com> (raw)
In-Reply-To: <20191203072824.GA1765@kadam>
On Tue, Dec 03, 2019 at 10:28:24AM +0300, Dan Carpenter wrote:
> On Mon, Dec 02, 2019 at 03:13:52PM +0000, Colin King wrote:
> > From: Colin Ian King <colin.king@canonical.com>
> >
> > The variable i is being initialized with a value that is never
> > read and it is being updated later with a new value in a for-loop.
> > The initialization is redundant and can be removed.
> >
> > Addresses-Coverity: ("Unused value")
> > Signed-off-by: Colin Ian King <colin.king@canonical.com>
> > ---
> > drivers/misc/ti-st/st_core.c | 2 +-
> > 1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > diff --git a/drivers/misc/ti-st/st_core.c b/drivers/misc/ti-st/st_core.c
> > index 2ae9948a91e1..6255d9b88122 100644
> > --- a/drivers/misc/ti-st/st_core.c
> > +++ b/drivers/misc/ti-st/st_core.c
> > @@ -736,7 +736,7 @@ static int st_tty_open(struct tty_struct *tty)
> >
> > static void st_tty_close(struct tty_struct *tty)
> > {
> > - unsigned char i = ST_MAX_CHANNELS;
> > + unsigned char i;
> > unsigned long flags = 0;
>
> I'm surprised that flags doesn't generate a warning as well.
Yes, flags should be not initialized as well.
Colin, can you resend a v2 with that added?
thanks,
greg k-h
WARNING: multiple messages have this Message-ID (diff)
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Dan Carpenter <dan.carpenter@oracle.com>
Cc: Colin King <colin.king@canonical.com>,
Arnd Bergmann <arnd@arndb.de>,
kernel-janitors@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] drivers/misc: ti-st: remove redundant assignment to variable i
Date: Sat, 11 Jan 2020 21:01:36 +0100 [thread overview]
Message-ID: <20200111200136.GC438314@kroah.com> (raw)
In-Reply-To: <20191203072824.GA1765@kadam>
On Tue, Dec 03, 2019 at 10:28:24AM +0300, Dan Carpenter wrote:
> On Mon, Dec 02, 2019 at 03:13:52PM +0000, Colin King wrote:
> > From: Colin Ian King <colin.king@canonical.com>
> >
> > The variable i is being initialized with a value that is never
> > read and it is being updated later with a new value in a for-loop.
> > The initialization is redundant and can be removed.
> >
> > Addresses-Coverity: ("Unused value")
> > Signed-off-by: Colin Ian King <colin.king@canonical.com>
> > ---
> > drivers/misc/ti-st/st_core.c | 2 +-
> > 1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > diff --git a/drivers/misc/ti-st/st_core.c b/drivers/misc/ti-st/st_core.c
> > index 2ae9948a91e1..6255d9b88122 100644
> > --- a/drivers/misc/ti-st/st_core.c
> > +++ b/drivers/misc/ti-st/st_core.c
> > @@ -736,7 +736,7 @@ static int st_tty_open(struct tty_struct *tty)
> >
> > static void st_tty_close(struct tty_struct *tty)
> > {
> > - unsigned char i = ST_MAX_CHANNELS;
> > + unsigned char i;
> > unsigned long flags = 0;
>
> I'm surprised that flags doesn't generate a warning as well.
Yes, flags should be not initialized as well.
Colin, can you resend a v2 with that added?
thanks,
greg k-h
next prev parent reply other threads:[~2020-01-11 20:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-02 15:13 [PATCH] drivers/misc: ti-st: remove redundant assignment to variable i Colin King
2019-12-02 15:13 ` Colin King
2019-12-03 7:28 ` Dan Carpenter
2019-12-03 7:28 ` Dan Carpenter
2020-01-11 20:01 ` Greg Kroah-Hartman [this message]
2020-01-11 20:01 ` Greg Kroah-Hartman
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=20200111200136.GC438314@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=arnd@arndb.de \
--cc=colin.king@canonical.com \
--cc=dan.carpenter@oracle.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@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.