From: Hugo Lefeuvre <hle@owl.eu.com>
To: Arnd Bergmann <arnd@arndb.de>
Cc: Thomas Gleixner <tglx@linutronix.de>,
linux-arch@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH 0/4] iomap: fix multiple consistency issues, interface cleanup
Date: Mon, 18 Feb 2019 11:53:15 +0100 [thread overview]
Message-ID: <cover.1550485787.git.hle@owl.eu.com> (raw)
Hi,
This patch cleans up the iomap interface.
The first patch makes the include/asm-generic/iomap.h header compliant
with the kernel style guidelines by adding missing function args
identifier names.
The second and fourth patches address multiple compilation warnings due
to missing const qualifiers in mmio_ins* and ioread*/iowrite
definitions in include/asm-generic/iomap.h and lib/iomap.c.
The third patch modifies io*_rep definitions from asm-generic/io.h to
take unsigned long count parameter instead of unsigned int which is
inconsistent with other definitions in the kernel.
Hugo Lefeuvre (4):
iomap: add missing function args identifier names
iomap: add missing const to ioread*/iowrite addr arg
io: change io*_rep definitions to take ulong count
lib/iomap: add missing const to mmio_ins* addr arg
include/asm-generic/io.h | 16 ++++++++--------
include/asm-generic/iomap.h | 38 ++++++++++++++++++-------------------
lib/iomap.c | 22 ++++++++++-----------
3 files changed, 38 insertions(+), 38 deletions(-)
--
2.20.1
next reply other threads:[~2019-02-18 10:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-18 10:53 Hugo Lefeuvre [this message]
2019-02-18 10:53 ` [PATCH 1/4] iomap: add missing function args identifier names Hugo Lefeuvre
2019-02-18 10:54 ` [PATCH 2/4] iomap: add missing const to ioread*/iowrite addr arg Hugo Lefeuvre
2019-02-18 10:54 ` [PATCH 3/4] io: change io*_rep definitions to take ulong count Hugo Lefeuvre
2019-02-18 10:54 ` [PATCH 4/4] lib/iomap: add missing const to mmio_ins* addr arg Hugo Lefeuvre
2019-02-18 14:11 ` [PATCH 0/4] iomap: fix multiple consistency issues, interface cleanup Arnd Bergmann
2019-02-18 20:30 ` Hugo Lefeuvre
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.1550485787.git.hle@owl.eu.com \
--to=hle@owl.eu.com \
--cc=arnd@arndb.de \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tglx@linutronix.de \
/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