From: Stephan Mueller <smueller@chronox.de>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Herbert Xu <herbert@gondor.apana.org.au>,
linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
"David S. Miller" <davem@davemloft.net>,
Linux Crypto Mailing List <linux-crypto@vger.kernel.org>,
netdev@vger.kernel.org
Subject: Re: linux-next: build warnings after merge of the crypto tree
Date: Tue, 10 Mar 2015 08:02:35 +0100 [thread overview]
Message-ID: <1658340.bSp4ddJdxm@tauon> (raw)
In-Reply-To: <20150310174454.7a92a3bd@canb.auug.org.au>
Am Dienstag, 10. März 2015, 17:44:54 schrieb Stephen Rothwell:
Hi Stephen,
>Hi Herbert,
>
>On Tue, 10 Mar 2015 17:03:28 +1100 Herbert Xu
<herbert@gondor.apana.org.au> wrote:
>> On Tue, Mar 10, 2015 at 04:44:17PM +1100, Stephen Rothwell wrote:
>> > 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)?
>
>No worries, I will put a merge fix patch in from tomorrow (and send you
>a copy just in case).
Thank you. Let me know if I should help.
Ciao
Stephan
next prev parent reply other threads:[~2015-03-10 7:02 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-10 5:44 linux-next: build warnings after merge of the crypto tree Stephen Rothwell
2015-03-10 6:03 ` Herbert Xu
2015-03-10 6:44 ` Stephen Rothwell
2015-03-10 7:02 ` Stephan Mueller [this message]
2015-03-11 0:56 ` Stephen Rothwell
2015-03-11 0:57 ` Herbert Xu
2015-03-11 2:00 ` Tadeusz Struk
2015-03-11 2:05 ` Herbert Xu
-- strict thread matches above, loose matches on Subject: below --
2023-03-14 3:19 Stephen Rothwell
2019-08-01 1:53 Stephen Rothwell
2017-02-06 1:28 Stephen Rothwell
2017-02-06 9:03 ` Herbert Xu
2017-02-10 3:12 ` Stephen Rothwell
2017-02-11 10:56 ` Herbert Xu
2017-02-12 23:42 ` Stephen Rothwell
2017-02-06 10:15 ` Cyrille Pitchen
2014-08-26 6:14 Stephen Rothwell
2014-08-26 6:38 ` Herbert Xu
2014-08-26 7:00 ` Stephan Mueller
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1658340.bSp4ddJdxm@tauon \
--to=smueller@chronox.de \
--cc=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).