From: maowenan <maowenan@huawei.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: <jeremy@azazel.net>, <devel@driverdev.osuosl.org>,
<kernel-janitors@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH net] staging: Remove set but not used variable ‘status’
Date: Sat, 25 May 2019 14:39:18 +0800 [thread overview]
Message-ID: <68a66947-928c-d2e6-be2b-aa412613f90c@huawei.com> (raw)
In-Reply-To: <20190525050113.GB18684@kroah.com>
On 2019/5/25 13:01, Greg KH wrote:
> On Sat, May 25, 2019 at 12:26:42PM +0800, Mao Wenan wrote:
>> Fixes gcc '-Wunused-but-set-variable' warning:
>>
>> drivers/staging/kpc2000/kpc_spi/spi_driver.c: In function
>> ‘kp_spi_transfer_one_message’:
>> drivers/staging/kpc2000/kpc_spi/spi_driver.c:282:9: warning: variable
>> ‘status’ set but not used [-Wunused-but-set-variable]
>> int status = 0;
>> ^~~~~~
>> The variable 'status' is not used any more, remve it.
>>
>> Signed-off-by: Mao Wenan <maowenan@huawei.com>
>> ---
>> drivers/staging/kpc2000/kpc_spi/spi_driver.c | 3 ---
>> 1 file changed, 3 deletions(-)
>
> What is [PATCH net] in the subject for? This is not a networking driver
> :(
Sorry, this is my mistake.
>
>
> .
>
next prev parent reply other threads:[~2019-05-25 6:39 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-25 4:26 Mao Wenan
2019-05-25 5:01 ` Greg KH
2019-05-25 6:39 ` maowenan [this message]
2019-05-25 8:13 ` [PATCH -next v2] staging: kpc2000: " Mao Wenan
2019-05-28 2:09 ` maowenan
2019-05-28 8:02 ` [PATCH -next v3 0/2] cleanup for kpc2000_spi.c Mao Wenan
2019-05-28 8:02 ` [PATCH -next v3 1/2] staging: kpc2000: report error status to spi core Mao Wenan
2019-05-28 8:02 ` [PATCH -next v3 2/2] staging: kpc2000: replace white spaces with tabs for kpc2000_spi.c Mao Wenan
2019-05-25 12:59 ` [PATCH net] staging: Remove set but not used variable ‘status’ Sven Van Asbroeck
2019-05-27 2:33 ` maowenan
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=68a66947-928c-d2e6-be2b-aa412613f90c@huawei.com \
--to=maowenan@huawei.com \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=jeremy@azazel.net \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®