From mboxrd@z Thu Jan 1 00:00:00 1970 Return-path: Received: from s3.sipsolutions.net ([5.9.151.49]:60990 "EHLO sipsolutions.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753060AbdIYFWd (ORCPT ); Mon, 25 Sep 2017 01:22:33 -0400 Message-ID: <1506316946.2909.8.camel@sipsolutions.net> (sfid-20170925_072508_951437_680DD0C5) Subject: Re: [PATCH] mac80211: aead api to reduce redundancy From: Johannes Berg To: Herbert Xu Cc: Xiang Gao , "David S. Miller" , linux-crypto@vger.kernel.org, linux-kernel , linux-wireless@vger.kernel.org, netdev@vger.kernel.org Date: Mon, 25 Sep 2017 07:22:26 +0200 In-Reply-To: <20170925045641.GB22947@gondor.apana.org.au> References: <20170924054015.8958-1-qasdfgtyuiop@gmail.com> <1506265531.2909.5.camel@sipsolutions.net> <1506274966.2909.7.camel@sipsolutions.net> <20170925045641.GB22947@gondor.apana.org.au> Content-Type: text/plain; charset="UTF-8" Mime-Version: 1.0 Sender: linux-wireless-owner@vger.kernel.org List-ID: On Mon, 2017-09-25 at 12:56 +0800, Herbert Xu wrote: > On Sun, Sep 24, 2017 at 07:42:46PM +0200, Johannes Berg wrote: > > > > Unrelated to this, I'm not sure whose tree this should go through - > > probably Herbert's (or DaveM's with his ACK? not sure if there's a > > crypto tree?) or so? > > Since you're just rearranging code invoking the crypto API, rather > than touching actual crypto API code, I think you should handle it > as you do with any other wireless patch. The code moves to crypto/ though, and I'm not even sure I can vouch for the Makefile choice there. johannes