Hi,
Are you interested in patches fixing typos ? I've found a bunch more
under /crypto but as I haven't received any responses on this one, I'm
not sure I should send new patches in.
This was my first patch so if I'm doing anything wrong, please tell me !
Mickael
On Sat, Nov 9, 2013 at 6:30 PM, Mickael Maison <mickael.maison@xxxxxxxxx> wrote:
> Fixed 2 typos in async_xor.c
> ---
> crypto/async_tx/async_xor.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/crypto/async_tx/async_xor.c b/crypto/async_tx/async_xor.c
> index 8ade0a0..bcaa1e9 100644
> --- a/crypto/async_tx/async_xor.c
> +++ b/crypto/async_tx/async_xor.c
> @@ -48,7 +48,7 @@ do_async_xor(struct dma_chan *chan, struct page *dest, struct page **src_list,
> int xor_src_cnt = 0;
> dma_addr_t dma_dest;
>
> - /* map the dest bidrectional in case it is re-used as a source */
> + /* map the dest bidirectional in case it is re-used as a source */
> dma_dest = dma_map_page(dma->dev, dest, offset, len, DMA_BIDIRECTIONAL);
> for (i = 0; i < src_cnt; i++) {
> /* only map the dest once */
> @@ -175,7 +175,7 @@ do_sync_xor(struct page *dest, struct page **src_list, 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
> + * 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.
> --
> 1.7.10.4
>
--
To unsubscribe from this list: send the line "unsubscribe linux-crypto" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
