crypto: api - use list_first_entry_or_null and list_next_entry

Simplify crypto_more_spawns() with list_first_entry_or_null()
and list_next_entry().

Signed-off-by: Geliang Tang <geliangtang@163.com>
Signed-off-by: Herbert Xu <herbert@gondor.apana.org.au>

diff --git a/crypto/algapi.c b/crypto/algapi.c
index 59bf491fe3d8606acc4016c53182182615d32a21..7be76aa315796dfad085ad74be5da35204bda9e6 100644 (file)
--- a/crypto/algapi.c
+++ b/crypto/algapi.c
@@ -93,16 +93,15 @@ static struct list_head *crypto_more_spawns(struct crypto_alg *alg,
 {
        struct crypto_spawn *spawn, *n;
 
-       if (list_empty(stack))
+       spawn = list_first_entry_or_null(stack, struct crypto_spawn, list);
+       if (!spawn)
                return NULL;
 
-       spawn = list_first_entry(stack, struct crypto_spawn, list);
-       n = list_entry(spawn->list.next, struct crypto_spawn, list);
+       n = list_next_entry(spawn, list);
 
        if (spawn->alg && &n->list != stack && !n->alg)
                n->alg = (n->list.next == stack) ? alg :
-                        &list_entry(n->list.next, struct crypto_spawn,
-                                    list)->inst->alg;
+                        &list_next_entry(n, list)->inst->alg;
 
        list_move(&spawn->list, secondary_spawns);