[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <20150310060328.GA14997@gondor.apana.org.au>
Date: Tue, 10 Mar 2015 17:03:28 +1100
From: Herbert Xu <herbert@...dor.apana.org.au>
To: Stephen Rothwell <sfr@...b.auug.org.au>
Cc: linux-next@...r.kernel.org, linux-kernel@...r.kernel.org,
Stephan Mueller <smueller@...onox.de>,
"David S. Miller" <davem@...emloft.net>,
Linux Crypto Mailing List <linux-crypto@...r.kernel.org>,
netdev@...r.kernel.org
Subject: Re: linux-next: build warnings after merge of the crypto tree
On Tue, Mar 10, 2015 at 04:44:17PM +1100, Stephen Rothwell wrote:
> Hi Herbert,
>
> After merging the crypto tree, today's (and the past few days)
> linux-next build (powerpc allyesconfig) produced these warnings:
>
> crypto/algif_aead.c:561:2: warning: initialization from incompatible pointer type
> .sendmsg = aead_sendmsg,
> ^
> crypto/algif_aead.c:561:2: warning: (near initialization for 'algif_aead_ops.sendmsg')
> crypto/algif_aead.c:563:2: warning: initialization from incompatible pointer type
> .recvmsg = aead_recvmsg,
> ^
> crypto/algif_aead.c:563:2: warning: (near initialization for 'algif_aead_ops.recvmsg')
>
> Introduced by commit 400c40cf78da ("crypto: algif - add AEAD support").
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)?
Thanks!
--
Email: Herbert Xu <herbert@...dor.apana.org.au>
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists