From: Logan Gunthorpe <logang@deltatee.com>
To: linux-kernel@vger.kernel.org, linux-arch@vger.kernel.org,
linux-ntb@googlegroups.com, linux-crypto@vger.kernel.org
Cc: Arnd Bergmann <arnd@arndb.de>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Jyri Sarha <jsarha@ti.com>, Stephen Bates <sbates@raithlin.com>,
Logan Gunthorpe <logang@deltatee.com>
Subject: [PATCH v2 0/3] make io{read|write}64 more globally usable
Date: Tue, 27 Jun 2017 17:02:01 -0600 [thread overview]
Message-ID: <20170627230204.16410-1-logang@deltatee.com> (raw)
Hi,
This is my second attempt to cleanup the io{read|write}64 functions so
that I can use them in a new driver[1]. This time, per a suggestion from Arnd,
we simply add the io64 functions to the io-64-nonatomic headers and
cleanup the two obvious drivers. (Horia provided me with a corrected patch
for the crypto caam which I have included.)
I've droped the tilcdc patch as it does not appear to support
non-atomic accesses, so it's hack around iowrite64 will remain.
Thanks,
Logan
[1] https://marc.info/?l=linux-kernel&m=149774601910663&w=2
Horia Geantă (1):
crypto: caam: cleanup CONFIG_64BIT ifdefs when using io{read|write}64
Logan Gunthorpe (2):
io-64-nonatomic: add io{read|write}64[be] macros
ntb: ntb_hw_intel: use io-64-nonatomic instead of in-driver hacks
drivers/crypto/caam/regs.h | 35 +++++------------------------------
drivers/ntb/hw/intel/ntb_hw_intel.c | 31 +------------------------------
include/linux/io-64-nonatomic-hi-lo.h | 16 ++++++++++++++++
include/linux/io-64-nonatomic-lo-hi.h | 16 ++++++++++++++++
4 files changed, 38 insertions(+), 60 deletions(-)
--
2.11.0
next reply other threads:[~2017-06-27 23:02 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-27 23:02 Logan Gunthorpe [this message]
2017-06-27 23:02 ` [PATCH v2 1/3] io-64-nonatomic: add io{read|write}64[be] macros Logan Gunthorpe
2017-06-28 10:11 ` Arnd Bergmann
2017-06-28 16:02 ` Logan Gunthorpe
2017-06-27 23:02 ` [PATCH v2 2/3] ntb: ntb_hw_intel: use io-64-nonatomic instead of in-driver hacks Logan Gunthorpe
2017-06-27 23:02 ` [PATCH v2 3/3] crypto: caam: cleanup CONFIG_64BIT ifdefs when using io{read|write}64 Logan Gunthorpe
2017-06-28 10:20 ` Arnd Bergmann
2017-06-28 16:51 ` Logan Gunthorpe
2017-06-29 7:52 ` Horia Geantă
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=20170627230204.16410-1-logang@deltatee.com \
--to=logang@deltatee.com \
--cc=arnd@arndb.de \
--cc=gregkh@linuxfoundation.org \
--cc=jsarha@ti.com \
--cc=linux-arch@vger.kernel.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-ntb@googlegroups.com \
--cc=sbates@raithlin.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;
as well as URLs for NNTP newsgroup(s).