From: Geordan Neukum <gneukum1@gmail.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Jeremy Sowden <jeremy@azazel.net>,
Mao Wenan <maowenan@huawei.com>,
YueHaibing <yuehaibing@huawei.com>,
Nathan Chancellor <natechancellor@gmail.com>,
Geordan Neukum <gneukum1@gmail.com>,
Dan Carpenter <dan.carpenter@oracle.com>,
devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org
Subject: [PATCH 0/5] staging: kpc2000: kpc_spi: Assorted small fixes
Date: Sun, 2 Jun 2019 15:58:32 +0000 [thread overview]
Message-ID: <cover.1559488571.git.gneukum1@gmail.com> (raw)
This patch set contains a few small fixups to the kpc_spi driver. There
is certainly nothing groundbreaking in this patch set. It is limited to
style fixups, removing unused things, and using the managed resource API
for mapping I/O space.
Geordan Neukum (5):
staging: kpc2000: kpc_spi: Remove unnecessary consecutive newlines
staging: kpc2000: kpc_spi: column-align switch and subordinate cases
staging: kpc2000: kpc_spi: remove fifo_depth from kp_spi struct
staging: kpc2000: kpc_spi: remove function kp_spi_bytes_per_word()
staging: kpc2000: kpc_spi: use devm_* API to manage mapped I/O space
drivers/staging/kpc2000/kpc2000_spi.c | 45 ++++++---------------------
1 file changed, 9 insertions(+), 36 deletions(-)
--
2.21.0
next reply other threads:[~2019-06-02 15:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-02 15:58 Geordan Neukum [this message]
2019-06-02 15:58 ` [PATCH 1/5] staging: kpc2000: kpc_spi: Remove unnecessary consecutive newlines Geordan Neukum
2019-06-02 15:58 ` [PATCH 2/5] staging: kpc2000: kpc_spi: column-align switch and subordinate cases Geordan Neukum
2019-06-02 15:58 ` [PATCH 3/5] staging: kpc2000: kpc_spi: remove fifo_depth from kp_spi struct Geordan Neukum
2019-06-02 15:58 ` [PATCH 4/5] staging: kpc2000: kpc_spi: remove function kp_spi_bytes_per_word() Geordan Neukum
2019-06-02 15:58 ` [PATCH 5/5] staging: kpc2000: kpc_spi: use devm_* API to manage mapped I/O space Geordan Neukum
2019-06-03 12:16 ` 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=cover.1559488571.git.gneukum1@gmail.com \
--to=gneukum1@gmail.com \
--cc=dan.carpenter@oracle.com \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=jeremy@azazel.net \
--cc=linux-kernel@vger.kernel.org \
--cc=maowenan@huawei.com \
--cc=natechancellor@gmail.com \
--cc=yuehaibing@huawei.com \
/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