[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAHp75Ve8LjhZHho15XZVnr8tSVLzJDxGBkAO7fJmYw1=mtfkTw@mail.gmail.com>
Date: Wed, 4 Jul 2018 20:25:08 +0300
From: Andy Shevchenko <andy.shevchenko@...il.com>
To: Logan Gunthorpe <logang@...tatee.com>
Cc: Fabio Estevam <festevam@...il.com>,
Horia Geanta <horia.geanta@....com>,
Aymen Sghaier <aymen.sghaier@....com>,
Andrew Morton <akpm@...ux-foundation.org>,
linux-kernel <linux-kernel@...r.kernel.org>,
Linux-Arch <linux-arch@...r.kernel.org>,
"linux-ntb@...glegroups.com" <linux-ntb@...glegroups.com>,
"open list:HARDWARE RANDOM NUMBER GENERATOR CORE"
<linux-crypto@...r.kernel.org>, Arnd Bergmann <arnd@...db.de>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Dan Douglass <dan.douglass@....com>,
Herbert Xu <herbert@...dor.apana.org.au>,
"David S. Miller" <davem@...emloft.net>
Subject: Re: [PATCH v18 6/7] crypto: caam: cleanup CONFIG_64BIT ifdefs when
using io{read|write}64
On Wed, Jul 4, 2018 at 8:23 PM, Logan Gunthorpe <logang@...tatee.com> wrote:
> On 7/4/2018 11:21 AM, Andy Shevchenko wrote:
>> I think it doesn't contradict with what you are saying rather supports it.
>>
>> I would expect to have lo-hi and hi-lo semantics done according to the
>> data flow, not to the address.
>
> Hmm, no, I expected the opposite...
Ah, sorry, misread you. Then it means I'm for the what I said and
opposing address flow.
--
With Best Regards,
Andy Shevchenko
Powered by blists - more mailing lists