From: Michael Ellerman Subject: Re: [PATCH 1/5] crypto/nx: Rename nx842_powernv_function as icswx function Date: Tue, 04 Apr 2017 21:11:51 +1000 Message-ID: <87inmkv348.fsf@concordia.ellerman.id.au> References: <1491065941.29552.26.camel@hbabu-laptop> Mime-Version: 1.0 Content-Type: text/plain Cc: mikey@neuling.org, suka@us.ibm.com, linux-crypto@vger.kernel.org, linuxppc-dev@lists.ozlabs.org To: Haren Myneni , herbert@gondor.apana.org.au, ddstreet@ieee.org Return-path: In-Reply-To: <1491065941.29552.26.camel@hbabu-laptop> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: linuxppc-dev-bounces+glppe-linuxppc-embedded-2=m.gmane.org@lists.ozlabs.org Sender: "Linuxppc-dev" List-Id: linux-crypto.vger.kernel.org Haren Myneni writes: > [PATCH 1/5] crypto/nx: Rename nx842_powernv_function as icswx function > > nx842_powernv_function is points to nx842_icswx_function and > will be point to VAS function which will be added later for > P9 NX support. I know it's nit-picking but can you give it a better name while you're there. I was thinking it should be called "send" or something, but it actually synchronously sends and waits for a request. So perhaps just nx842_exec(), for "execute a request", and then you can have nx842_exec_icswx() and nx842_exec_vas(). cheers