LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Mao Wenan <maowenan@huawei.com>
To: <gregkh@linuxfoundation.org>, <jeremy@azazel.net>
Cc: <thesven73@gmail.com>, <devel@driverdev.osuosl.org>,
<linux-kernel@vger.kernel.org>, <kernel-janitors@vger.kernel.org>,
<matt.sickler@daktronics.com>, Mao Wenan <maowenan@huawei.com>
Subject: [PATCH -next v3 0/2] cleanup for kpc2000_spi.c
Date: Tue, 28 May 2019 16:02:12 +0800 [thread overview]
Message-ID: <20190528080214.18382-1-maowenan@huawei.com> (raw)
In-Reply-To: <20190525081321.121294-1-maowenan@huawei.com>
The error status should resotre to m->status in kp_spi_transfer_one_message(),
and many white spaces in kpc2000_spi.c. patch 1 is to fix the error path, and
patch 2 is to cleanup kpc2000_spi.c.
v1: remove set but not used variable 'status'.
v2: fix the subject tile.
v3: add another patch to fix the error condition path and do some clean work for kpc2000_spi.c.
Mao Wenan (2):
staging: kpc2000: report error status to spi core
staging: kpc2000: replace white spaces with tabs for kpc2000_spi.c
drivers/staging/kpc2000/kpc2000_spi.c | 718 +++++++++++++-------------
1 file changed, 361 insertions(+), 357 deletions(-)
--
2.20.1
next prev parent reply other threads:[~2019-05-28 7:54 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-25 4:26 [PATCH net] staging: Remove set but not used variable ‘status’ Mao Wenan
2019-05-25 5:01 ` Greg KH
2019-05-25 6:39 ` maowenan
2019-05-25 8:13 ` [PATCH -next v2] staging: kpc2000: " Mao Wenan
2019-05-28 2:09 ` maowenan
2019-05-28 8:02 ` Mao Wenan [this message]
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=20190528080214.18382-1-maowenan@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 \
--cc=matt.sickler@daktronics.com \
--cc=thesven73@gmail.com \
--subject='Re: [PATCH -next v3 0/2] cleanup for kpc2000_spi.c' \
/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
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).