Hi Herbert,
On Thu, 8 Aug 2019 15:00:04 +1000 Herbert Xu
wrote:
>
> On Thu, Aug 08, 2019 at 01:17:10PM +1000, Stephen Rothwell wrote:
> >
> > Excellent, thanks. Should I add the crypto mailing list as a contact
> > for problems? Mostly the emails are just reporting conflicts and only
> > very
On Thu, Aug 08, 2019 at 01:17:10PM +1000, Stephen Rothwell wrote:
>
> Excellent, thanks. Should I add the crypto mailing list as a contact
> for problems? Mostly the emails are just reporting conflicts and only
> very occasionally do I actually send a useful patch. If so, what is
> its address?
Hi Herbert,
On Thu, 8 Aug 2019 13:01:57 +1000 Herbert Xu
wrote:
>
> Sorry, I forgot about your patch as it wasn't cced to the crypto
> mailing list. It should be out there now.
Excellent, thanks. Should I add the crypto mailing list as a contact
for problems? Mostly the emails are just
On Thu, Aug 08, 2019 at 11:52:45AM +1000, Stephen Rothwell wrote:
> Hi all,
>
> On Mon, 5 Aug 2019 14:57:36 +1000 Stephen Rothwell
> wrote:
> >
> > Hi all,
> >
> > After merging the crypto tree, today's linux-next build (sparc64
> > defconfig) failed like this:
> >
> >
Hi all,
On Mon, 5 Aug 2019 14:57:36 +1000 Stephen Rothwell
wrote:
>
> Hi all,
>
> After merging the crypto tree, today's linux-next build (sparc64
> defconfig) failed like this:
>
> drivers/char/hw_random/n2-drv.c: In function 'n2rng_probe':
> drivers/char/hw_random/n2-drv.c:771:29: error:
On Mon, Aug 5, 2019 at 12:57 PM Stephen Rothwell wrote:
>
> Hi all,
>
> After merging the crypto tree, today's linux-next build (sparc64
> defconfig) failed like this:
>
> drivers/char/hw_random/n2-drv.c: In function 'n2rng_probe':
> drivers/char/hw_random/n2-drv.c:771:29: error: 'pdev'
Hi all,
After merging the crypto tree, today's linux-next build (sparc64
defconfig) failed like this:
drivers/char/hw_random/n2-drv.c: In function 'n2rng_probe':
drivers/char/hw_random/n2-drv.c:771:29: error: 'pdev' undeclared (first use in
this function); did you mean 'cdev'?
err =
On Mon, Oct 08, 2018 at 12:03:30PM +1100, Stephen Rothwell wrote:
> Hi Herbert,
>
> After merging the crypto tree, today's linux-next build (x86_64
> allmodconfig) failed like this:
>
> ERROR: "crypto_fpu_exit" [arch/x86/crypto/aesni-intel.ko] undefined!
> ERROR: "crypto_fpu_init"
On Mon, Oct 08, 2018 at 12:03:30PM +1100, Stephen Rothwell wrote:
> Hi Herbert,
>
> After merging the crypto tree, today's linux-next build (x86_64
> allmodconfig) failed like this:
>
> ERROR: "crypto_fpu_exit" [arch/x86/crypto/aesni-intel.ko] undefined!
> ERROR: "crypto_fpu_init"
Hi Herbert,
After merging the crypto tree, today's linux-next build (x86_64
allmodconfig) failed like this:
ERROR: "crypto_fpu_exit" [arch/x86/crypto/aesni-intel.ko] undefined!
ERROR: "crypto_fpu_init" [arch/x86/crypto/aesni-intel.ko] undefined!
Caused by commit
944585a64f5e ("crypto:
Hi Herbert,
After merging the crypto tree, today's linux-next build (x86_64
allmodconfig) failed like this:
ERROR: "crypto_fpu_exit" [arch/x86/crypto/aesni-intel.ko] undefined!
ERROR: "crypto_fpu_init" [arch/x86/crypto/aesni-intel.ko] undefined!
Caused by commit
944585a64f5e ("crypto:
Hi Ondrej,
On Tue, 29 May 2018 12:16:59 +0200 Ondrej Mosnáček wrote:
>
> there is already a patch pending that fixes the issue:
>
> https://patchwork.kernel.org/patch/10416245/
Great, hopefully it will be merged soon.
--
Cheers,
Stephen Rothwell
pgpHUYW3gzGGl.pgp
Description: OpenPGP
Hi Ondrej,
On Tue, 29 May 2018 12:16:59 +0200 Ondrej Mosnáček wrote:
>
> there is already a patch pending that fixes the issue:
>
> https://patchwork.kernel.org/patch/10416245/
Great, hopefully it will be merged soon.
--
Cheers,
Stephen Rothwell
pgpHUYW3gzGGl.pgp
Description: OpenPGP
Hi Stephen,
there is already a patch pending that fixes the issue:
https://patchwork.kernel.org/patch/10416245/
Cheers,
Ondrej
2018-05-29 11:08 GMT+02:00 Stephen Rothwell :
> Hi Herbert,
>
> After merging the crypto tree, today's linux-next build (powerpc
> allyesconfig) failed like this:
>
>
Hi Stephen,
there is already a patch pending that fixes the issue:
https://patchwork.kernel.org/patch/10416245/
Cheers,
Ondrej
2018-05-29 11:08 GMT+02:00 Stephen Rothwell :
> Hi Herbert,
>
> After merging the crypto tree, today's linux-next build (powerpc
> allyesconfig) failed like this:
>
>
Hi Herbert,
After merging the crypto tree, today's linux-next build (powerpc
allyesconfig) failed like this:
/home/sfr/next/next/crypto/morus640_glue.c:24:10: fatal error: asm/fpu/api.h:
No such file or directory
#include
^~~
Hi Herbert,
After merging the crypto tree, today's linux-next build (powerpc
allyesconfig) failed like this:
/home/sfr/next/next/crypto/morus640_glue.c:24:10: fatal error: asm/fpu/api.h:
No such file or directory
#include
^~~
On Mon, Nov 06, 2017 at 11:25:21AM +1100, Stephen Rothwell wrote:
> Hi Herbert,
>
> After merging the crypto tree, today's linux-next build (arm
> multi_v7_defconfig) failed like this:
>
> drivers/crypto/marvell/marvell-cesa: struct platform_device_id is 24 bytes.
> The last of 1 is:
> 0x6d
On Mon, Nov 06, 2017 at 11:25:21AM +1100, Stephen Rothwell wrote:
> Hi Herbert,
>
> After merging the crypto tree, today's linux-next build (arm
> multi_v7_defconfig) failed like this:
>
> drivers/crypto/marvell/marvell-cesa: struct platform_device_id is 24 bytes.
> The last of 1 is:
> 0x6d
Hi Herbert,
After merging the crypto tree, today's linux-next build (arm
multi_v7_defconfig) failed like this:
drivers/crypto/marvell/marvell-cesa: struct platform_device_id is 24 bytes.
The last of 1 is:
0x6d 0x76 0x5f 0x63 0x72 0x79 0x70 0x74 0x6f 0x00 0x00 0x00 0x00 0x00 0x00 0x00
0x00
Hi Herbert,
After merging the crypto tree, today's linux-next build (arm
multi_v7_defconfig) failed like this:
drivers/crypto/marvell/marvell-cesa: struct platform_device_id is 24 bytes.
The last of 1 is:
0x6d 0x76 0x5f 0x63 0x72 0x79 0x70 0x74 0x6f 0x00 0x00 0x00 0x00 0x00 0x00 0x00
0x00
On 11/29/2016 10:09 AM, Herbert Xu wrote:
> On Tue, Nov 29, 2016 at 11:55:29AM +1100, Stephen Rothwell wrote:
>> Hi Herbert,
>>
>> After merging the crypto tree, today's linux-next build (arm
>> multi_v7_defconfig) failed like this:
>>
>> ERROR: "simd_skcipher_free" [arch/arm/crypto/aes-arm-ce.ko]
On 11/29/2016 10:09 AM, Herbert Xu wrote:
> On Tue, Nov 29, 2016 at 11:55:29AM +1100, Stephen Rothwell wrote:
>> Hi Herbert,
>>
>> After merging the crypto tree, today's linux-next build (arm
>> multi_v7_defconfig) failed like this:
>>
>> ERROR: "simd_skcipher_free" [arch/arm/crypto/aes-arm-ce.ko]
On Tue, Nov 29, 2016 at 08:34:08AM +, Horia Geantă wrote:
>
> > Fixes: da40e7a4ba4d ("crypto: aes-ce - Convert to skcipher")
> > Fixes: 211f41af534a ("crypto: aesbs - Convert to skcipher")
> The fix for this commit is missing.
> CRYPTO_AES_ARM_BS also needs to select CRYPTO_SIMD.
Thanks.
On Tue, Nov 29, 2016 at 08:34:08AM +, Horia Geantă wrote:
>
> > Fixes: da40e7a4ba4d ("crypto: aes-ce - Convert to skcipher")
> > Fixes: 211f41af534a ("crypto: aesbs - Convert to skcipher")
> The fix for this commit is missing.
> CRYPTO_AES_ARM_BS also needs to select CRYPTO_SIMD.
Thanks.
On Tue, Nov 29, 2016 at 11:55:29AM +1100, Stephen Rothwell wrote:
> Hi Herbert,
>
> After merging the crypto tree, today's linux-next build (arm
> multi_v7_defconfig) failed like this:
>
> ERROR: "simd_skcipher_free" [arch/arm/crypto/aes-arm-ce.ko] undefined!
> ERROR:
On Tue, Nov 29, 2016 at 11:55:29AM +1100, Stephen Rothwell wrote:
> Hi Herbert,
>
> After merging the crypto tree, today's linux-next build (arm
> multi_v7_defconfig) failed like this:
>
> ERROR: "simd_skcipher_free" [arch/arm/crypto/aes-arm-ce.ko] undefined!
> ERROR:
Hi Herbert,
After merging the crypto tree, today's linux-next build (arm
multi_v7_defconfig) failed like this:
ERROR: "simd_skcipher_free" [arch/arm/crypto/aes-arm-ce.ko] undefined!
ERROR: "simd_skcipher_create_compat" [arch/arm/crypto/aes-arm-ce.ko] undefined!
ERROR: "simd_skcipher_free"
Hi Herbert,
After merging the crypto tree, today's linux-next build (arm
multi_v7_defconfig) failed like this:
ERROR: "simd_skcipher_free" [arch/arm/crypto/aes-arm-ce.ko] undefined!
ERROR: "simd_skcipher_create_compat" [arch/arm/crypto/aes-arm-ce.ko] undefined!
ERROR: "simd_skcipher_free"
On Wed, Jul 20, 2016 at 05:46:34PM +1000, Stephen Rothwell wrote:
> Hi all,
>
> After merging the dax-misc tree, today's linux-next build (powerpc
> allyesconfig) failed like this:
>
> drivers/crypto/vmx/aesp8-ppc.S: Assembler messages:
> drivers/crypto/vmx/aesp8-ppc.S:2036: Error: symbol
On Wed, Jul 20, 2016 at 05:46:34PM +1000, Stephen Rothwell wrote:
> Hi all,
>
> After merging the dax-misc tree, today's linux-next build (powerpc
> allyesconfig) failed like this:
>
> drivers/crypto/vmx/aesp8-ppc.S: Assembler messages:
> drivers/crypto/vmx/aesp8-ppc.S:2036: Error: symbol
Hi all,
After merging the dax-misc tree, today's linux-next build (powerpc
allyesconfig) failed like this:
drivers/crypto/vmx/aesp8-ppc.S: Assembler messages:
drivers/crypto/vmx/aesp8-ppc.S:2036: Error: symbol `.aes_p8_xts_decrypt' is
already defined
Caused by commit
11c6e16ee13a ("crypto:
Hi all,
After merging the dax-misc tree, today's linux-next build (powerpc
allyesconfig) failed like this:
drivers/crypto/vmx/aesp8-ppc.S: Assembler messages:
drivers/crypto/vmx/aesp8-ppc.S:2036: Error: symbol `.aes_p8_xts_decrypt' is
already defined
Caused by commit
11c6e16ee13a ("crypto:
lvatore.benede...@intel.com>
> Subject: Re: linux-next: build failure after merge of the crypto tree
>
> On Fri, Jun 24, 2016 at 04:20:22PM +1000, Stephen Rothwell wrote:
> > Hi Herbert,
> >
> > After merging the crypto tree, today's linux-next build (powerpc
> > ally
> -Original Message-
> From: Herbert Xu [mailto:herb...@gondor.apana.org.au]
> Sent: Friday, June 24, 2016 2:33 PM
> To: Stephen Rothwell
> Cc: linux-n...@vger.kernel.org; linux-kernel@vger.kernel.org; Benedetto,
> Salvatore
> Subject: Re: linux-next: buil
On Fri, Jun 24, 2016 at 04:20:22PM +1000, Stephen Rothwell wrote:
> Hi Herbert,
>
> After merging the crypto tree, today's linux-next build (powerpc
> allyesconfig) failed like this:
>
> net/built-in.o: In function `.ecdh_shared_secret':
> (.text+0x4ad8d0): multiple definition of
On Fri, Jun 24, 2016 at 04:20:22PM +1000, Stephen Rothwell wrote:
> Hi Herbert,
>
> After merging the crypto tree, today's linux-next build (powerpc
> allyesconfig) failed like this:
>
> net/built-in.o: In function `.ecdh_shared_secret':
> (.text+0x4ad8d0): multiple definition of
Hi Herbert,
After merging the crypto tree, today's linux-next build (powerpc
allyesconfig) failed like this:
net/built-in.o: In function `.ecdh_shared_secret':
(.text+0x4ad8d0): multiple definition of `.ecdh_shared_secret'
crypto/built-in.o:(.text+0x113f0): first defined here
Hi Herbert,
After merging the crypto tree, today's linux-next build (powerpc
allyesconfig) failed like this:
net/built-in.o: In function `.ecdh_shared_secret':
(.text+0x4ad8d0): multiple definition of `.ecdh_shared_secret'
crypto/built-in.o:(.text+0x113f0): first defined here
Hi Herbert,
After merging the crypto tree, today's linux-next build (arm
multi_v7_defconfig) failed like this:
arch/arm/crypto/aesbs-glue.c: In function 'aesbs_xts_set_key':
arch/arm/crypto/aesbs-glue.c:94:8: error: implicit declaration of function
'xts_check_key'
Hi Herbert,
After merging the crypto tree, today's linux-next build (arm
multi_v7_defconfig) failed like this:
arch/arm/crypto/aesbs-glue.c: In function 'aesbs_xts_set_key':
arch/arm/crypto/aesbs-glue.c:94:8: error: implicit declaration of function
'xts_check_key'
On Thu, Oct 15, 2015 at 12:37:00PM +1100, Stephen Rothwell wrote:
> Hi Herbert,
>
> After merging the crypto tree, today's linux-next build (x86_64
> allmodconfig) failed like this:
>
> drivers/char/hw_random/stm32-rng.c: In function 'stm32_rng_runtime_suspend':
>
Hi Herbert,
After merging the crypto tree, today's linux-next build (x86_64
allmodconfig) failed like this:
drivers/char/hw_random/stm32-rng.c: In function 'stm32_rng_runtime_suspend':
drivers/char/hw_random/stm32-rng.c:163:51: error: 'pdev' undeclared (first use
in this function)
struct
Hi Herbert,
After merging the crypto tree, today's linux-next build (x86_64
allmodconfig) failed like this:
drivers/char/hw_random/stm32-rng.c: In function 'stm32_rng_runtime_suspend':
drivers/char/hw_random/stm32-rng.c:163:51: error: 'pdev' undeclared (first use
in this function)
struct
On Thu, Oct 15, 2015 at 12:37:00PM +1100, Stephen Rothwell wrote:
> Hi Herbert,
>
> After merging the crypto tree, today's linux-next build (x86_64
> allmodconfig) failed like this:
>
> drivers/char/hw_random/stm32-rng.c: In function 'stm32_rng_runtime_suspend':
>
On Wed, Aug 05, 2015 at 04:49:31PM +1000, Stephen Rothwell wrote:
> Hi Herbert,
>
> After merging the crypto tree, today's linux-next build (sparc64
> defconfig) failed like this:
>
> crypto/built-in.o: In function `crypto_authenc_exit_tfm':
> authenc.c:(.text+0x11d1c): undefined reference to
>
Hi Herbert,
After merging the crypto tree, today's linux-next build (sparc64
defconfig) failed like this:
crypto/built-in.o: In function `crypto_authenc_exit_tfm':
authenc.c:(.text+0x11d1c): undefined reference to
`crypto_put_default_null_skcipher'
crypto/built-in.o: In function
Hi Herbert,
After merging the crypto tree, today's linux-next build (sparc64
defconfig) failed like this:
crypto/built-in.o: In function `crypto_authenc_exit_tfm':
authenc.c:(.text+0x11d1c): undefined reference to
`crypto_put_default_null_skcipher'
crypto/built-in.o: In function
On Wed, Aug 05, 2015 at 04:49:31PM +1000, Stephen Rothwell wrote:
Hi Herbert,
After merging the crypto tree, today's linux-next build (sparc64
defconfig) failed like this:
crypto/built-in.o: In function `crypto_authenc_exit_tfm':
authenc.c:(.text+0x11d1c): undefined reference to
Hi Herbert,
After merging the crypto tree, today's linux-next build (x86_64
allmodconfig) failed like this:
net/mac802154/llsec.c: In function 'llsec_do_encrypt_auth':
/scratch/sfr/next/net/mac802154/llsec.c:675:15: error: 'dst' undeclared (first
use in this function)
sg_init_one(dst,
Hi Herbert,
After merging the crypto tree, today's linux-next build (x86_64
allmodconfig) failed like this:
net/mac802154/llsec.c: In function 'llsec_do_encrypt_auth':
/scratch/sfr/next/net/mac802154/llsec.c:675:15: error: 'dst' undeclared (first
use in this function)
sg_init_one(dst,
Am Donnerstag, 28. Mai 2015, 21:40:49 schrieb Stephen Rothwell:
Hi Stephen,
>Hi Herbert,
>
>After merging the crypto tree, today's linux-next build (powerpc
>allyesconfig) failed like this:
>
>crypto/jitterentropy.c: In function 'jent_get_nstime':
>crypto/jitterentropy.c:135:5: error: implicit
Hi Herbert,
After merging the crypto tree, today's linux-next build (powerpc allyesconfig)
failed like this:
crypto/jitterentropy.c: In function 'jent_get_nstime':
crypto/jitterentropy.c:135:5: error: implicit declaration of function
'timekeeping_valid_for_hres'
Hi Herbert,
After merging the crypto tree, today's linux-next build (powerpc allyesconfig)
failed like this:
crypto/jitterentropy.c: In function 'jent_get_nstime':
crypto/jitterentropy.c:135:5: error: implicit declaration of function
'timekeeping_valid_for_hres'
Am Donnerstag, 28. Mai 2015, 21:40:49 schrieb Stephen Rothwell:
Hi Stephen,
Hi Herbert,
After merging the crypto tree, today's linux-next build (powerpc
allyesconfig) failed like this:
crypto/jitterentropy.c: In function 'jent_get_nstime':
crypto/jitterentropy.c:135:5: error: implicit
On Tue, Mar 17, 2015 at 01:01:04PM +1100, Stephen Rothwell wrote:
>
> After merging the crypto tree, today's linux-next build (x86_64 allmodconfig)
> failed like this:
>
> drivers/crypto/img-hash.c: At top level:
> drivers/crypto/img-hash.c:878:1: error: expected ',' or ';' before 'static'
>
On Tue, Mar 17, 2015 at 01:01:04PM +1100, Stephen Rothwell wrote:
After merging the crypto tree, today's linux-next build (x86_64 allmodconfig)
failed like this:
drivers/crypto/img-hash.c: At top level:
drivers/crypto/img-hash.c:878:1: error: expected ',' or ';' before 'static'
static
Hi Herbert,
After merging the crypto tree, today's linux-next build (x86_64 allmodconfig)
failed like this:
drivers/crypto/img-hash.c: At top level:
drivers/crypto/img-hash.c:878:1: error: expected ',' or ';' before 'static'
static int img_hash_probe(struct platform_device *pdev)
^
Caused by
Hi Herbert,
After merging the crypto tree, today's linux-next build (x86_64 allmodconfig)
failed like this:
drivers/crypto/img-hash.c: At top level:
drivers/crypto/img-hash.c:878:1: error: expected ',' or ';' before 'static'
static int img_hash_probe(struct platform_device *pdev)
^
Caused by
On 07/24/2014 02:04 AM, Randy Dunlap wrote:
On 07/23/2014 08:08 PM, Stephen Rothwell wrote:
Hi Herbert,
After merging the crypto tree, today's linux-next build (powerpc
ppc64_defconfig) produced these messages:
fs/sysfs/Kconfig:1:error: recursive dependency detected!
fs/sysfs/Kconfig:1:
On 07/23/2014 08:08 PM, Stephen Rothwell wrote:
> Hi Herbert,
>
> After merging the crypto tree, today's linux-next build (powerpc
> ppc64_defconfig) produced these messages:
>
> fs/sysfs/Kconfig:1:error: recursive dependency detected!
> fs/sysfs/Kconfig:1: symbol SYSFS is selected by AT91_ADC
On 07/23/2014 08:08 PM, Stephen Rothwell wrote:
Hi Herbert,
After merging the crypto tree, today's linux-next build (powerpc
ppc64_defconfig) produced these messages:
fs/sysfs/Kconfig:1:error: recursive dependency detected!
fs/sysfs/Kconfig:1: symbol SYSFS is selected by AT91_ADC
On 07/24/2014 02:04 AM, Randy Dunlap wrote:
On 07/23/2014 08:08 PM, Stephen Rothwell wrote:
Hi Herbert,
After merging the crypto tree, today's linux-next build (powerpc
ppc64_defconfig) produced these messages:
fs/sysfs/Kconfig:1:error: recursive dependency detected!
fs/sysfs/Kconfig:1:
Hi Herbert,
After merging the crypto tree, today's linux-next build (powerpc
ppc64_defconfig) produced these messages:
fs/sysfs/Kconfig:1:error: recursive dependency detected!
fs/sysfs/Kconfig:1: symbol SYSFS is selected by AT91_ADC
drivers/iio/adc/Kconfig:110:symbol AT91_ADC depends on
Hi Herbert,
After merging the crypto tree, today's linux-next build (powerpc
ppc64_defconfig) produced these messages:
fs/sysfs/Kconfig:1:error: recursive dependency detected!
fs/sysfs/Kconfig:1: symbol SYSFS is selected by AT91_ADC
drivers/iio/adc/Kconfig:110:symbol AT91_ADC depends on
On Mon, Jun 23, 2014 at 11:15:31PM +1000, Stephen Rothwell wrote:
> Hi Herbert,
>
> On Mon, 23 Jun 2014 20:27:47 +0800 Herbert Xu
> wrote:
> >
> > That's weird as it built correctly here. This looks like a
> > make/gcc issue as the missing header file is meant to be found
> > with an
Hi Herbert,
On Mon, 23 Jun 2014 20:27:47 +0800 Herbert Xu
wrote:
>
> That's weird as it built correctly here. This looks like a
> make/gcc issue as the missing header file is meant to be found
> with an additional -I.
>
> Could you do a make V=1 for me and show me what the gcc command-line
>
Hi Stephen:
On Mon, Jun 23, 2014 at 11:49:42AM +1000, Stephen Rothwell wrote:
>
> After merging the crypto tree, today's linux-next build (x86_64
> allmodconfig) failed like this:
>
>
> drivers/crypto/qat/qat_dh895xcc/adf_dh895xcc_hw_data.c:47:31: fatal error:
> adf_accel_devices.h: No such
On Mon, Jun 23, 2014 at 11:15:31PM +1000, Stephen Rothwell wrote:
Hi Herbert,
On Mon, 23 Jun 2014 20:27:47 +0800 Herbert Xu herb...@gondor.apana.org.au
wrote:
That's weird as it built correctly here. This looks like a
make/gcc issue as the missing header file is meant to be found
Hi Stephen:
On Mon, Jun 23, 2014 at 11:49:42AM +1000, Stephen Rothwell wrote:
After merging the crypto tree, today's linux-next build (x86_64
allmodconfig) failed like this:
drivers/crypto/qat/qat_dh895xcc/adf_dh895xcc_hw_data.c:47:31: fatal error:
adf_accel_devices.h: No such file or
Hi Herbert,
On Mon, 23 Jun 2014 20:27:47 +0800 Herbert Xu herb...@gondor.apana.org.au
wrote:
That's weird as it built correctly here. This looks like a
make/gcc issue as the missing header file is meant to be found
with an additional -I.
Could you do a make V=1 for me and show me what
Hi Herbert,
After merging the crypto tree, today's linux-next build (x86_64
allmodconfig) failed like this:
drivers/crypto/qat/qat_dh895xcc/adf_dh895xcc_hw_data.c:47:31: fatal error:
adf_accel_devices.h: No such file or directory
#include
^
Hi Herbert,
After merging the crypto tree, today's linux-next build (x86_64
allmodconfig) failed like this:
drivers/crypto/qat/qat_dh895xcc/adf_dh895xcc_hw_data.c:47:31: fatal error:
adf_accel_devices.h: No such file or directory
#include adf_accel_devices.h
^
Hi Herbert,
After merging the crypto tree, today's linux-next build (arm
multi_v7_defconfig) failed like this:
crypto/memneq.c: In function '__crypto_memneq_16':
crypto/memneq.c:145:2: warning: no return statement in function returning
non-void [-Wreturn-type]
crypto/memneq.c: At top level:
Hi Herbert,
After merging the crypto tree, today's linux-next build (arm
multi_v7_defconfig) failed like this:
crypto/memneq.c: In function '__crypto_memneq_16':
crypto/memneq.c:145:2: warning: no return statement in function returning
non-void [-Wreturn-type]
crypto/memneq.c: At top level:
On Mon, May 27, 2013 at 01:43:01PM +1000, Stephen Rothwell wrote:
> Hi Herbert,
>
> On Mon, 27 May 2013 10:19:18 +0800 Herbert Xu
> wrote:
> >
> > Hi Stephen, did you get a chance to switch back to the current
> > cryptodev tree?
>
> Not quite sure what you mean? I fetch your tree every
Hi Herbert,
On Mon, 27 May 2013 10:19:18 +0800 Herbert Xu
wrote:
>
> Hi Stephen, did you get a chance to switch back to the current
> cryptodev tree?
Not quite sure what you mean? I fetch your tree every morning (that I
build linux-next) so I got an update from you this morning. I haven't
On Fri, May 24, 2013 at 05:57:15PM +0800, Herbert Xu wrote:
> On Tue, May 21, 2013 at 11:45:48AM +1000, Stephen Rothwell wrote:
> > Hi Herbert,
> >
> > After merging the crypto tree, today's linux-next build (x86_64
> > allmodconfig) failed like this:
> >
> >
On Fri, May 24, 2013 at 05:57:15PM +0800, Herbert Xu wrote:
On Tue, May 21, 2013 at 11:45:48AM +1000, Stephen Rothwell wrote:
Hi Herbert,
After merging the crypto tree, today's linux-next build (x86_64
allmodconfig) failed like this:
arch/x86/crypto/crct10dif-pclmul_glue.c: In
Hi Herbert,
On Mon, 27 May 2013 10:19:18 +0800 Herbert Xu herb...@gondor.apana.org.au
wrote:
Hi Stephen, did you get a chance to switch back to the current
cryptodev tree?
Not quite sure what you mean? I fetch your tree every morning (that I
build linux-next) so I got an update from you
On Mon, May 27, 2013 at 01:43:01PM +1000, Stephen Rothwell wrote:
Hi Herbert,
On Mon, 27 May 2013 10:19:18 +0800 Herbert Xu herb...@gondor.apana.org.au
wrote:
Hi Stephen, did you get a chance to switch back to the current
cryptodev tree?
Not quite sure what you mean? I fetch your
On Tue, May 21, 2013 at 11:45:48AM +1000, Stephen Rothwell wrote:
> Hi Herbert,
>
> After merging the crypto tree, today's linux-next build (x86_64
> allmodconfig) failed like this:
>
> arch/x86/crypto/crct10dif-pclmul_glue.c: In function
> 'crct10dif_intel_mod_init':
>
On Tue, May 21, 2013 at 11:45:48AM +1000, Stephen Rothwell wrote:
Hi Herbert,
After merging the crypto tree, today's linux-next build (x86_64
allmodconfig) failed like this:
arch/x86/crypto/crct10dif-pclmul_glue.c: In function
'crct10dif_intel_mod_init':
Hi Herbert,
After merging the crypto tree, today's linux-next build (x86_64
allmodconfig) failed like this:
arch/x86/crypto/crct10dif-pclmul_glue.c: In function 'crct10dif_intel_mod_init':
arch/x86/crypto/crct10dif-pclmul_glue.c:140:3: error: implicit declaration of
function
Hi Herbert,
After merging the crypto tree, today's linux-next build (x86_64
allmodconfig) failed like this:
arch/x86/crypto/crct10dif-pclmul_glue.c: In function 'crct10dif_intel_mod_init':
arch/x86/crypto/crct10dif-pclmul_glue.c:140:3: error: implicit declaration of
function
85 matches
Mail list logo
