Hi all,
After merging the crypto tree, today's linux-next build (arm
multi_v7_defconfig) produced this warning:
scripts/Makefile.asm-generic:25: redundant generic-y found in
arch/arm/include/asm/Kbuild: simd.h
Introduced by commit
82cb54856874 ("asm-generic: make simd.h a mandatory
Hi Herbert,
On Sat, 11 Feb 2017 18:56:21 +0800 Herbert Xu
wrote:
>
> On Fri, Feb 10, 2017 at 02:12:51PM +1100, Stephen Rothwell wrote:
> >
> > I am still getting these warnings ... I have seen no updates to the
> > crypot tree since Feb 2.
>
> Sorry Stephen. I
Hi Herbert,
On Sat, 11 Feb 2017 18:56:21 +0800 Herbert Xu
wrote:
>
> On Fri, Feb 10, 2017 at 02:12:51PM +1100, Stephen Rothwell wrote:
> >
> > I am still getting these warnings ... I have seen no updates to the
> > crypot tree since Feb 2.
>
> Sorry Stephen. I have now applied Arnd's fixes
On Fri, Feb 10, 2017 at 02:12:51PM +1100, Stephen Rothwell wrote:
>
> I am still getting these warnings ... I have seen no updates to the
> crypot tree since Feb 2.
Sorry Stephen. I have now applied Arnd's fixes for this problem
and it should be pushed out.
Cheers,
--
Email: Herbert Xu
On Fri, Feb 10, 2017 at 02:12:51PM +1100, Stephen Rothwell wrote:
>
> I am still getting these warnings ... I have seen no updates to the
> crypot tree since Feb 2.
Sorry Stephen. I have now applied Arnd's fixes for this problem
and it should be pushed out.
Cheers,
--
Email: Herbert Xu
Home
Hi Herbert,
On Mon, 6 Feb 2017 17:03:40 +0800 Herbert Xu
wrote:
>
> On Mon, Feb 06, 2017 at 12:28:37PM +1100, Stephen Rothwell wrote:
> >
> > After merging the crypto tree, today's linux-next build (x86_64
> > allmodconfig) produced these warnings:
> >
> >
Hi Herbert,
On Mon, 6 Feb 2017 17:03:40 +0800 Herbert Xu
wrote:
>
> On Mon, Feb 06, 2017 at 12:28:37PM +1100, Stephen Rothwell wrote:
> >
> > After merging the crypto tree, today's linux-next build (x86_64
> > allmodconfig) produced these warnings:
> >
> > warning: (CRYPTO_DEV_ATMEL_AUTHENC)
Hi all,
Le 06/02/2017 à 02:28, Stephen Rothwell a écrit :
> Hi Herbert,
>
> After merging the crypto tree, today's linux-next build (x86_64
> allmodconfig) produced these warnings:
>
> warning: (CRYPTO_DEV_ATMEL_AUTHENC) selects CRYPTO_DEV_ATMEL_SHA which has
> unmet direct dependencies
Hi all,
Le 06/02/2017 à 02:28, Stephen Rothwell a écrit :
> Hi Herbert,
>
> After merging the crypto tree, today's linux-next build (x86_64
> allmodconfig) produced these warnings:
>
> warning: (CRYPTO_DEV_ATMEL_AUTHENC) selects CRYPTO_DEV_ATMEL_SHA which has
> unmet direct dependencies
Hi Stephen:
On Mon, Feb 06, 2017 at 12:28:37PM +1100, Stephen Rothwell wrote:
>
> After merging the crypto tree, today's linux-next build (x86_64
> allmodconfig) produced these warnings:
>
> warning: (CRYPTO_DEV_ATMEL_AUTHENC) selects CRYPTO_DEV_ATMEL_SHA which has
> unmet direct dependencies
Hi Stephen:
On Mon, Feb 06, 2017 at 12:28:37PM +1100, Stephen Rothwell wrote:
>
> After merging the crypto tree, today's linux-next build (x86_64
> allmodconfig) produced these warnings:
>
> warning: (CRYPTO_DEV_ATMEL_AUTHENC) selects CRYPTO_DEV_ATMEL_SHA which has
> unmet direct dependencies
Hi Herbert,
After merging the crypto tree, today's linux-next build (x86_64
allmodconfig) produced these warnings:
warning: (CRYPTO_DEV_ATMEL_AUTHENC) selects CRYPTO_DEV_ATMEL_SHA which has
unmet direct dependencies (CRYPTO && CRYPTO_HW && ARCH_AT91)
warning: (CRYPTO_DEV_ATMEL_AUTHENC) selects
Hi Herbert,
After merging the crypto tree, today's linux-next build (x86_64
allmodconfig) produced these warnings:
warning: (CRYPTO_DEV_ATMEL_AUTHENC) selects CRYPTO_DEV_ATMEL_SHA which has
unmet direct dependencies (CRYPTO && CRYPTO_HW && ARCH_AT91)
warning: (CRYPTO_DEV_ATMEL_AUTHENC) selects
On Tue, Mar 10, 2015 at 07:00:26PM -0700, Tadeusz Struk wrote:
> 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
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
On Wed, Mar 11, 2015 at 11:56:37AM +1100, Stephen Rothwell wrote:
>
> This is what I applied:
>
> From: Stephen Rothwell
> Date: Wed, 11 Mar 2015 11:51:30 +1100
> Subject: [PATCH] crypto: fix for sendmsg/recvmsg API change
>
> Signed-off-by: Stephen Rothwell
Looks good to me. Thanks
Hi all,
On Tue, 10 Mar 2015 17:44:54 +1100 Stephen Rothwell
wrote:
>
> On Tue, 10 Mar 2015 17:03:28 +1100 Herbert Xu
> 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
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
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)
>> >
Hi Herbert,
On Tue, 10 Mar 2015 17:03:28 +1100 Herbert Xu
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:
> >
> >
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
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
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
Hi all,
On Tue, 10 Mar 2015 17:44:54 +1100 Stephen Rothwell s...@canb.auug.org.au
wrote:
On Tue, 10 Mar 2015 17:03:28 +1100 Herbert Xu herb...@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
On Wed, Mar 11, 2015 at 11:56:37AM +1100, Stephen Rothwell wrote:
This is what I applied:
From: Stephen Rothwell s...@canb.auug.org.au
Date: Wed, 11 Mar 2015 11:51:30 +1100
Subject: [PATCH] crypto: fix for sendmsg/recvmsg API change
Signed-off-by: Stephen Rothwell s...@canb.auug.org.au
On Tue, Mar 10, 2015 at 07:00:26PM -0700, Tadeusz Struk wrote:
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
Hi Herbert,
On Tue, 10 Mar 2015 17:03:28 +1100 Herbert Xu herb...@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:
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
herb...@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
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
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
Am Dienstag, 26. August 2014, 14:38:12 schrieb Herbert Xu:
Hi Herbert,
>On Tue, Aug 26, 2014 at 04:14:56PM +1000, Stephen Rothwell wrote:
>> Hi Herbert,
>>
>> After merging the crypto tree, today's linux-next build (powerpc
>> ppc44x_defconfig, i386 defconfig and sparc defconfig) produced these
On Tue, Aug 26, 2014 at 04:14:56PM +1000, Stephen Rothwell wrote:
> Hi Herbert,
>
> After merging the crypto tree, today's linux-next build (powerpc
> ppc44x_defconfig, i386 defconfig and sparc defconfig) produced these
> warnings:
>
> In file included from crypto/testmgr.c:30:0:
>
Hi Herbert,
After merging the crypto tree, today's linux-next build (powerpc
ppc44x_defconfig, i386 defconfig and sparc defconfig) produced these
warnings:
In file included from crypto/testmgr.c:30:0:
include/crypto/drbg.h: In function 'drbg_max_addtl':
include/crypto/drbg.h:157:2: warning: left
Hi Herbert,
After merging the crypto tree, today's linux-next build (powerpc
ppc44x_defconfig, i386 defconfig and sparc defconfig) produced these
warnings:
In file included from crypto/testmgr.c:30:0:
include/crypto/drbg.h: In function 'drbg_max_addtl':
include/crypto/drbg.h:157:2: warning: left
On Tue, Aug 26, 2014 at 04:14:56PM +1000, Stephen Rothwell wrote:
Hi Herbert,
After merging the crypto tree, today's linux-next build (powerpc
ppc44x_defconfig, i386 defconfig and sparc defconfig) produced these
warnings:
In file included from crypto/testmgr.c:30:0:
Am Dienstag, 26. August 2014, 14:38:12 schrieb Herbert Xu:
Hi Herbert,
On Tue, Aug 26, 2014 at 04:14:56PM +1000, Stephen Rothwell wrote:
Hi Herbert,
After merging the crypto tree, today's linux-next build (powerpc
ppc44x_defconfig, i386 defconfig and sparc defconfig) produced these
35 matches
Mail list logo