From: John Garry <john.garry@huawei.com>
To: <xuwei5@huawei.com>
Cc: <linuxarm@huawei.com>, <linux-kernel@vger.kernel.org>,
<olof@lixom.net>, <bhelgaas@google.com>, <arnd@arndb.de>,
John Garry <john.garry@huawei.com>
Subject: [PATCH v2 0/5] hisi_lpc: Improve build test coverage
Date: Mon, 28 Oct 2019 20:10:00 +0800 [thread overview]
Message-ID: <1572264605-172363-1-git-send-email-john.garry@huawei.com> (raw)
This series aims to improve the build test cover of the driver by
supporting building under COMPILE_TEST.
I also included "lib: logic_pio: Enforce LOGIC_PIO_INDIRECT region ops
are set at registration" as it was never picked up for 5.4.
Two new patches are also included since v1:
- clean issues detected by sparse
- build logic_pio.o into /lib library
John Garry (5):
lib: logic_pio: Enforce LOGIC_PIO_INDIRECT region ops are set at
registration
logic_pio: Define PIO_INDIRECT_SIZE for !CONFIG_INDIRECT_PIO
bus: hisi_lpc: Clean some types
bus: hisi_lpc: Expand build test coverage
logic_pio: Build into a library
drivers/bus/Kconfig | 4 ++--
drivers/bus/hisi_lpc.c | 9 ++++-----
include/linux/logic_pio.h | 4 ++--
lib/Makefile | 2 +-
lib/logic_pio.c | 14 ++++++++------
5 files changed, 17 insertions(+), 16 deletions(-)
--
2.17.1
next reply other threads:[~2019-10-28 12:13 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-28 12:10 John Garry [this message]
2019-10-28 12:10 ` [PATCH v2 1/5] lib: logic_pio: Enforce LOGIC_PIO_INDIRECT region ops are set at registration John Garry
2019-10-28 12:10 ` [PATCH v2 2/5] logic_pio: Define PIO_INDIRECT_SIZE for !CONFIG_INDIRECT_PIO John Garry
2019-10-28 12:10 ` [PATCH v2 3/5] bus: hisi_lpc: Clean some types John Garry
2019-10-28 12:10 ` [PATCH v2 4/5] bus: hisi_lpc: Expand build test coverage John Garry
2019-10-28 12:10 ` [PATCH v2 5/5] logic_pio: Build into a library John Garry
2019-10-30 9:19 ` [PATCH v2 0/5] hisi_lpc: Improve build test coverage Wei Xu
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=1572264605-172363-1-git-send-email-john.garry@huawei.com \
--to=john.garry@huawei.com \
--cc=arnd@arndb.de \
--cc=bhelgaas@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxarm@huawei.com \
--cc=olof@lixom.net \
--cc=xuwei5@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
all inboxes | Powered by JetHome®