Am Montag, 14. April 2014, 22:51:05 schrieb Joe Perches:
Hi Joe,
On Tue, 2014-04-15 at 07:35 +0200, Stephan Mueller wrote:
diff --git a/crypto/drbg.c b/crypto/drbg.c
[]
@@ -0,0 +1,1997 @@
[]
+/***
+ * Backend cipher
On Tue, Apr 15, 2014 at 11:06:34AM +0200, Paul Bolle wrote:
On Sun, 2014-02-09 at 21:18 +0100, Paul Bolle wrote:
On Sun, 2014-02-09 at 19:47 +0100, Richard Weinberger wrote:
The symbol is an orphan, get rid of it.
Signed-off-by: Richard Weinberger rich...@nod.at
Acked-by: Paul
On Sun, 2014-02-09 at 21:18 +0100, Paul Bolle wrote:
On Sun, 2014-02-09 at 19:47 +0100, Richard Weinberger wrote:
The symbol is an orphan, get rid of it.
Signed-off-by: Richard Weinberger rich...@nod.at
Acked-by: Paul Bolle pebo...@tiscali.nl
---
crypto/asymmetric_keys/Kconfig |
pm_runtime_get_sync may not always succeed depending on SoC involved. So
handle the error appropriately.
Reported-by: Joachim Eastwood manab...@gmail.com
Signed-off-by: Nishanth Menon n...@ti.com
---
based on v3.15-rc1
Report-thread: http://marc.info/?t=13975033042r=1w=2
Hi,
On Tue, Apr 15, 2014 at 10:33:02AM -0500, Nishanth Menon wrote:
pm_runtime_get_sync may not always succeed depending on SoC involved. So
handle the error appropriately.
Reported-by: Joachim Eastwood manab...@gmail.com
Signed-off-by: Nishanth Menon n...@ti.com
---
based on v3.15-rc1
On 04/15/2014 10:50 AM, Felipe Balbi wrote:
Hi,
On Tue, Apr 15, 2014 at 10:33:02AM -0500, Nishanth Menon wrote:
pm_runtime_get_sync may not always succeed depending on SoC involved. So
handle the error appropriately.
Reported-by: Joachim Eastwood manab...@gmail.com
Signed-off-by: Nishanth
pm_runtime_get_sync may not always succeed depending on SoC involved.
So handle the error appropriately ensuring usage_count is accurate in
case of failure.
Signed-off-by: Nishanth Menon n...@ti.com
---
V2:
- review fixes, print function names in error log as well.
V1:
On 15 April 2014 18:58, Nishanth Menon n...@ti.com wrote:
pm_runtime_get_sync may not always succeed depending on SoC involved.
So handle the error appropriately ensuring usage_count is accurate in
case of failure.
Signed-off-by: Nishanth Menon n...@ti.com
---
V2:
- review fixes,
On Tue, Apr 15, 2014 at 11:58:31AM -0500, Nishanth Menon wrote:
pm_runtime_get_sync may not always succeed depending on SoC involved.
So handle the error appropriately ensuring usage_count is accurate in
case of failure.
Signed-off-by: Nishanth Menon n...@ti.com
Reviewed-by: Felipe Balbi
On 04/15/2014 12:06 PM, Joachim Eastwood wrote:
On 15 April 2014 18:58, Nishanth Menon n...@ti.com wrote:
pm_runtime_get_sync may not always succeed depending on SoC involved.
So handle the error appropriately ensuring usage_count is accurate in
case of failure.
Signed-off-by: Nishanth Menon
On 04/15/2014 12:18 PM, Nishanth Menon wrote:
On 04/15/2014 12:06 PM, Joachim Eastwood wrote:
On 15 April 2014 18:58, Nishanth Menon n...@ti.com wrote:
pm_runtime_get_sync may not always succeed depending on SoC involved.
So handle the error appropriately ensuring usage_count is accurate in
11 matches
Mail list logo
