From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752094AbbCKCDA (ORCPT ); Tue, 10 Mar 2015 22:03:00 -0400 Received: from mga01.intel.com ([192.55.52.88]:20899 "EHLO mga01.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751097AbbCKCC6 (ORCPT ); Tue, 10 Mar 2015 22:02:58 -0400 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.11,378,1422950400"; d="scan'208";a="539014618" Message-ID: <54FFA1BA.30009@intel.com> Date: Tue, 10 Mar 2015 19:00:26 -0700 From: Tadeusz Struk User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.5.0 MIME-Version: 1.0 To: Herbert Xu , Stephen Rothwell CC: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org, Stephan Mueller , "David S. Miller" , Linux Crypto Mailing List , netdev@vger.kernel.org Subject: Re: linux-next: build warnings after merge of the crypto tree References: <20150310164417.540c18a4@canb.auug.org.au> <20150310060328.GA14997@gondor.apana.org.au> In-Reply-To: <20150310060328.GA14997@gondor.apana.org.au> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 03/09/2015 11:03 PM, Herbert Xu wrote: > This is a bit of a bummer. What happened is that net-next has > killed the kiocb argument to sendmsg/recvmsg. However, this > change is obviously not part of the crypto tree and algif_aead > only exists in the crypto tree. > > So Stephen could you fix this by hand until one of them is merged > upstream (just kill the first argument in aead_sendmsg/aead_recvmsg)? So does it mean that aio operations will not be supported on sockets?