On 3/25/21 7:34 PM, Bhaskar Chowdhury wrote: > > s/eninges/engines/ ...two different places. > s/explicity/explicitly/ ....two different places. > > Signed-off-by: Bhaskar Chowdhury <unixbhaskar@xxxxxxxxx> Acked-by: Randy Dunlap <rdunlap@xxxxxxxxxxxxx> > --- > crypto/async_tx/async_xor.c | 8 ++++---- > 1 file changed, 4 insertions(+), 4 deletions(-) > > diff --git a/crypto/async_tx/async_xor.c b/crypto/async_tx/async_xor.c > index a057ecb1288d..fee33f76cdd9 100644 > --- a/crypto/async_tx/async_xor.c > +++ b/crypto/async_tx/async_xor.c > @@ -170,8 +170,8 @@ dma_xor_aligned_offsets(struct dma_device *device, unsigned int offset, > * > * xor_blocks always uses the dest as a source so the > * ASYNC_TX_XOR_ZERO_DST flag must be set to not include dest data in > - * the calculation. The assumption with dma eninges is that they only > - * use the destination buffer as a source when it is explicity specified > + * the calculation. The assumption with dma engines is that they only > + * use the destination buffer as a source when it is explicitly specified > * in the source list. > * > * src_list note: if the dest is also a source it must be at index zero. > @@ -259,8 +259,8 @@ EXPORT_SYMBOL_GPL(async_xor_offs); > * > * xor_blocks always uses the dest as a source so the > * ASYNC_TX_XOR_ZERO_DST flag must be set to not include dest data in > - * the calculation. The assumption with dma eninges is that they only > - * use the destination buffer as a source when it is explicity specified > + * the calculation. The assumption with dma engines is that they only > + * use the destination buffer as a source when it is explicitly specified > * in the source list. > * > * src_list note: if the dest is also a source it must be at index zero. > -- -- ~Randy
