Re: linux-next: build warnings after merge of the crypto tree
From: Tadeusz Struk <hidden>
Date: 2015-03-11 02:03:00
Also in:
linux-next, lkml, netdev
Possibly related (same subject, not in this thread)
- 2023-03-14 · linux-next: build warnings after merge of the crypto tree · Stephen Rothwell <hidden>
- 2017-02-12 · Re: linux-next: build warnings after merge of the crypto tree · Stephen Rothwell <hidden>
- 2017-02-11 · Re: linux-next: build warnings after merge of the crypto tree · Herbert Xu <herbert@gondor.apana.org.au>
- 2017-02-10 · Re: linux-next: build warnings after merge of the crypto tree · Stephen Rothwell <hidden>
- 2017-02-06 · Re: linux-next: build warnings after merge of the crypto tree · Herbert Xu <herbert@gondor.apana.org.au>
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?