[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAOMZO5BJXtpy+fmWxHqQWf_GwzoeQ=nTD8wWFAfw3vs6e0eV0g@mail.gmail.com>
Date: Wed, 4 Jul 2018 13:16:07 -0300
From: Fabio Estevam <festevam@...il.com>
To: Horia Geanta <horia.geanta@....com>
Cc: Logan Gunthorpe <logang@...tatee.com>,
Andy Shevchenko <andy.shevchenko@...il.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 12:59 PM, Horia Geanta <horia.geanta@....com> wrote:
> I guess it would be better this way.
Sounds good. I will submit the revert patch then.
Thanks
Powered by blists - more mailing lists