From: Andy Shevchenko Subject: Re: [PATCH RFC 0/3] API for 128-bit IO access Date: Wed, 24 Jan 2018 17:48:03 +0200 Message-ID: References: <20180124090519.6680-1-ynorov@caviumnetworks.com> Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Cc: Yury Norov , Linux ARM , linux-arch , Linux Kernel Mailing List , "open list:HARDWARE RANDOM NUMBER GENERATOR CORE" , Al Viro , Andrew Morton , Andrew Pinski , Catalin Marinas , "David S . Miller" , Geethasowjanya Akula , Greg Kroah-Hartman , Ingo Molnar , Kees Cook , Laura Abbott , Nicholas Piggin , Sunil Goutham , To: Arnd Bergmann Return-path: In-Reply-To: Sender: linux-arch-owner@vger.kernel.org List-Id: linux-crypto.vger.kernel.org On Wed, Jan 24, 2018 at 12:28 PM, Arnd Bergmann wrote: > On Wed, Jan 24, 2018 at 10:05 AM, Yury Norov wrote: >> * For 128-bit read/write functions I take suffix 'o', which means read/write >> the octet of bytes. Is this name OK? > > Can't think of anything better. It's not an octet though, but 16 bytes > ('q' is for quadword, meaning four 16-bit words in Intel terminology). It's apparently follows Intel's terminology by implying "word", so, "octetword". -- With Best Regards, Andy Shevchenko