Hi,
* Dmitry Kasatkin dmitry.kasat...@nokia.com [101110 09:18]:
Suggested to use udelay() instead of nop as on the higher
core frequencies it might not be enough time.
Signed-off-by: Dmitry Kasatkin dmitry.kasat...@nokia.com
---
drivers/crypto/omap-aes.c | 10 ++
1 files
* Dmitry Kasatkin dmitry.kasat...@nokia.com [101110 09:20]:
- registration with multi OMAP kernels support
- clocks
Signed-off-by: Dmitry Kasatkin dmitry.kasat...@nokia.com
---
arch/arm/mach-omap2/clock2420_data.c |2 +-
arch/arm/mach-omap2/clock2430_data.c |2 +-
* Dmitry Kasatkin dmitry.kasat...@nokia.com [101110 09:20]:
Signed-off-by: Dmitry Kasatkin dmitry.kasat...@nokia.com
---
arch/arm/mach-omap2/devices.c |4 ++--
1 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/arch/arm/mach-omap2/devices.c b/arch/arm/mach-omap2/devices.c
Mimi Zohar zo...@linux.vnet.ibm.com wrote:
I actually like keyctl requiring 'trusted:' or 'user:'. Forcing the
user to indicate which type of key they want, is actually good - no
misunderstandings.
You still need to prefix the description of a user-defined key so that you
don't collide with
On Tue, 2010-11-16 at 17:50 +, David Howells wrote:
Mimi Zohar zo...@linux.vnet.ibm.com wrote:
I actually like keyctl requiring 'trusted:' or 'user:'. Forcing the
user to indicate which type of key they want, is actually good - no
misunderstandings.
You still need to prefix the
Mimi Zohar zo...@linux.vnet.ibm.com wrote:
No, this just updates the name of the key used to encrypt/decrypt the
encrypted key. For example, the encrypted key evm-key is initially
encrypted/decrypted using 'kmk-trusted'. After the update, it is
encrypted/decrypted with 'kmk'. Both now are
On Tue, 2010-11-16 at 17:50 +, David Howells wrote:
Mimi Zohar zo...@linux.vnet.ibm.com wrote:
I actually like keyctl requiring 'trusted:' or 'user:'. Forcing the
user to indicate which type of key they want, is actually good - no
misunderstandings.
You still need to prefix the
