of the removed to that tells users which version to use.
Signed-off-by: Arnd Bergmann a...@arndb.de
Link: http://storage.kernelci.org/next/next-20150410/arm-allmodconfig/build.log
Fixes: 864cbeed4ab22d (crypto: arm - add support for SHA1 using ARMv8 Crypto
Instructions)
diff --git a/arch/arm
On Fri, Apr 10, 2015 at 04:33:17PM +0200, Stephan Mueller wrote:
Am Freitag, 10. April 2015, 14:22:08 schrieb mancha security:
Hi mancha,
__asm__ __volatile__(: :r(p) :memory)
gcc -O2/3: mov present
clang -O2/3: mov present
== approach would be good too.
Note, the assembly code
On Friday 10 April 2015 16:29:08 Ard Biesheuvel wrote:
+#if __ARM_MAX_ARCH__=7
+.arch armv7-a
+.fpu neon
+
This will cause a build failure on an ARMv7-M build, which is incompatible
with .arch armv7-a and .fpu neon.
Arnd
--
To unsubscribe from this list: send the line
On 10 apr. 2015, at 22:08, Arnd Bergmann a...@arndb.de wrote:
On Friday 10 April 2015 16:29:08 Ard Biesheuvel wrote:
+#if __ARM_MAX_ARCH__=7
+.arch armv7-a
+.fpu neon
+
This will cause a build failure on an ARMv7-M build, which is incompatible
with .arch armv7-a and .fpu neon.
Am Samstag, 11. April 2015, 00:30:30 schrieb sri sowj:
Hi sri,
Hi All,
I have seen multiple open source drivers for AES(CTR) mode for
different Crypto Hardware Engines, I was not really sure on
countersize,nonce etc.
Please can any one provide some info on the following
#1:How does AES
Hey Boris,
On Fri, Apr 10, 2015 at 05:11:48PM +0200, Boris Brezillon wrote:
On Fri, 10 Apr 2015 13:50:56 + Jason Cooper ja...@lakedaemon.net wrote:
On Thu, Apr 09, 2015 at 04:58:41PM +0200, Boris Brezillon wrote:
I know we usually try to adapt existing drivers instead of replacing them
