On Mon, 1 Mar 2021 at 07:36, Herbert Xu wrote:
>
> On Sat, Feb 27, 2021 at 05:37:49PM +0100, Krzysztof Kozlowski wrote:
> >
> > I think this patch was lost, although you replied that the entire set
> > is applied.
> >
> > Can you pick it up?
>
> I think it was not applicable because the following
On Sat, Feb 27, 2021 at 05:37:49PM +0100, Krzysztof Kozlowski wrote:
>
> I think this patch was lost, although you replied that the entire set
> is applied.
>
> Can you pick it up?
I think it was not applicable because the following had already
been applied:
commit ea066b7a3ddf1e4e5ae749495f0adf
Remove including that don't need it.
Signed-off-by: Tian Tao
---
drivers/crypto/cavium/cpt/cptpf_main.c | 1 -
1 file changed, 1 deletion(-)
diff --git a/drivers/crypto/cavium/cpt/cptpf_main.c
b/drivers/crypto/cavium/cpt/cptpf_main.c
index 711b1ac..06ee42e 100644
--- a/drivers/crypto/cavium/c
DMA_TO_DEVICE synchronisation must be done after the last modification
of the memory region by the software and before it is handed off to
the device.
Signed-off-by: Hui Tang
---
drivers/crypto/qat/qat_common/qat_algs.c | 23 ---
1 file changed, 12 insertions(+), 11 deletions
Use devm_hwrng_register to get rid of manual unregistration.
Signed-off-by: Tian Tao
---
drivers/char/hw_random/pic32-rng.c | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/drivers/char/hw_random/pic32-rng.c
b/drivers/char/hw_random/pic32-rng.c
index e8210c1..99c8bd0 100644
Use devm_hwrng_register to get rid of manual unregistration.
Signed-off-by: Tian Tao
---
drivers/char/hw_random/cctrng.c | 4 +---
1 file changed, 1 insertion(+), 3 deletions(-)
diff --git a/drivers/char/hw_random/cctrng.c b/drivers/char/hw_random/cctrng.c
index 7a293f2..0efb37a 100644
--- a/dr
[ Bcc a lot of lists so that people understand what's this is all ]
[ about without creating uber-cc-thread. ]
[ Apologies if I missed your subsystem]
[ Please see [PATCH 11/11: pragma once: conversion script (in Pytho
Given that crypto_alloc_tfm() may return ERR pointers, and to avoid
crashes on obscure error paths where such pointers are presented to
crypto_destroy_tfm() (such as [0]), add an ERR_PTR check there
before dereferencing the second argument as a struct crypto_tfm
pointer.
[0]
https://lore.kernel.o