On 3/22/2014 6:24 PM, Ben Hutchings wrote:
On Fri, 2014-03-21 at 00:35 +0545, Yashpal Dutta wrote:
Job ring is suspended gracefully and resume afresh.
Both Sleep (where device will remain powered-on) and Deep-sleep (where
device will be powered-down are handled gracefully. Persistance sessions
are not supported across deep-sleep.
Cc: sta...@vger.kernel.org
Signed-off-by: Yashpal Dutta <yashpal.du...@freescale.com>
---
drivers/crypto/caam/intern.h | 2 +
drivers/crypto/caam/jr.c | 257 +++++++++++++++++++++++++++++++------------
2 files changed, 190 insertions(+), 69 deletions(-)
[...]
This is too big for stable; is a simpler fix possible?
Besides size, I'd also question whether this is a bug fix or a feature.
From Documentation/stable_kernel_rules.txt:
- It must fix a problem that causes a build error (but not for things
marked CONFIG_BROKEN), an oops, a hang, data corruption, a real
security issue, or some "oh, that's not good" issue. In short,
something critical.
On top of that - does it apply cleanly && has it been tested with
-stable kernels?
Regards,
Horia
--
To unsubscribe from this list: send the line "unsubscribe linux-crypto" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
