[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <c5208a76-e94b-0203-3591-81b14e7fd888@deltatee.com>
Date: Mon, 31 Jul 2017 12:04:56 -0600
From: Logan Gunthorpe <logang@...tatee.com>
To: Andy Shevchenko <andy.shevchenko@...il.com>
Cc: "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Linux-Arch <linux-arch@...r.kernel.org>,
linux-ntb@...glegroups.com,
linux-crypto <linux-crypto@...r.kernel.org>,
Arnd Bergmann <arnd@...db.de>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Horia Geantă <horia.geanta@....com>,
Stephen Bates <sbates@...thlin.com>,
Benjamin Herrenschmidt <benh@...nel.crashing.org>,
Paul Mackerras <paulus@...ba.org>,
Michael Ellerman <mpe@...erman.id.au>,
Suresh Warrier <warrier@...ux.vnet.ibm.com>,
Nicholas Piggin <npiggin@...il.com>
Subject: Re: [PATCH v5 3/6] iomap: introduce io{read|write}64_{lo_hi|hi_lo}
On 31/07/17 12:03 PM, Andy Shevchenko wrote:
>
> Per commit 3a044178cccf they are exactly created for this kind of cases.
>
Sure, ok, and my patchset provides the same set of functions to satisfy
such a use.
Logan
Powered by blists - more mailing lists