crypto: marvell/cesa - always ensure mid-fragments after first-fragment
authorRussell King <rmk+kernel@arm.linux.org.uk>
Sun, 18 Oct 2015 16:24:11 +0000 (17:24 +0100)
committerHerbert Xu <herbert@gondor.apana.org.au>
Tue, 20 Oct 2015 14:11:05 +0000 (22:11 +0800)
commit2f396a91d1d01a423fd87b7c6ff71600d06b9c05
treeee3915fee57f74aeaad52156cec6eeacd0246e82
parent9621288673cb2a1805eadf29b92e5bcec6a0e2e5
crypto: marvell/cesa - always ensure mid-fragments after first-fragment

If we add a template first-fragment operation, always update the
template to be a mid-fragment.  This ensures that mid-fragments
always follow on from a first fragment in every case.

This means we can move the first to mid-fragment update code out of
mv_cesa_ahash_dma_add_data().

Signed-off-by: Russell King <rmk+kernel@arm.linux.org.uk>
Signed-off-by: Herbert Xu <herbert@gondor.apana.org.au>
drivers/crypto/marvell/hash.c