From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from ale.deltatee.com (ale.deltatee.com. [207.54.116.67]) by gmr-mx.google.com with ESMTPS id c67si79353itb.5.2017.06.22.10.30.56 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 22 Jun 2017 10:30:57 -0700 (PDT) References: <20170622164817.25515-1-logang@deltatee.com> <20170622164817.25515-5-logang@deltatee.com> From: Logan Gunthorpe Message-ID: <0d2f1f7c-d014-5ddf-ad5c-64f13cb5a64a@deltatee.com> Date: Thu, 22 Jun 2017 11:30:42 -0600 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [PATCH 4/7] alpha: provide ioread64 and iowrite64 implementations To: Stephen Bates , "linux-kernel@vger.kernel.org" , "linux-arch@vger.kernel.org" , "linux-ntb@googlegroups.com" , "linux-alpha@vger.kernel.org" , "linuxppc-dev@lists.ozlabs.org" , "linux-crypto@vger.kernel.org" , "dri-devel@lists.freedesktop.org" Cc: Arnd Bergmann , Greg Kroah-Hartman , Richard Henderson , Ivan Kokshaysky , Matt Turner List-ID: On 6/22/2017 11:29 AM, Stephen Bates wrote: >> +#define iowrite64be(v,p) iowrite32(cpu_to_be64(v), (p)) > > Logan, thanks for taking this cleanup on. I think this should be iowrite64 not iowrite32? Yup, good catch. Thanks. I'll fix it in a v2 of this series. Logan