* [PATCH] CRYPTO: async_tx: Fixed a couple of typos
@ 2013-11-09 17:30 Mickael Maison
2013-12-19 16:06 ` Mickael Maison
0 siblings, 1 reply; 2+ messages in thread
From: Mickael Maison @ 2013-11-09 17:30 UTC (permalink / raw)
To: dan.j.williams; +Cc: herbert, davem, linux-crypto, linux-kernel, Mickael Maison
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
^ permalink raw reply related [flat|nested] 2+ messages in thread
* Re: [PATCH] CRYPTO: async_tx: Fixed a couple of typos
2013-11-09 17:30 [PATCH] CRYPTO: async_tx: Fixed a couple of typos Mickael Maison
@ 2013-12-19 16:06 ` Mickael Maison
0 siblings, 0 replies; 2+ messages in thread
From: Mickael Maison @ 2013-12-19 16:06 UTC (permalink / raw)
To: dan.j.williams; +Cc: Herbert Xu, davem, linux-crypto, linux-kernel
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@gmail.com> 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
>
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2013-12-19 16:06 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2013-11-09 17:30 [PATCH] CRYPTO: async_tx: Fixed a couple of typos Mickael Maison
2013-12-19 16:06 ` Mickael Maison
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).