From: Randy Dunlap <rdunlap@bombadil.infradead.org>
To: Bhaskar Chowdhury <unixbhaskar@gmail.com>
Cc: dan.j.williams@intel.com, herbert@gondor.apana.org.au,
davem@davemloft.net, yuyufen@huawei.com, songliubraving@fb.com,
linux-crypto@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] md/raid6: Couple of typo fixes
Date: Fri, 19 Mar 2021 09:07:55 -0700 (PDT) [thread overview]
Message-ID: <2b59cdc-fdb7-be14-ebdc-a49b47594b32@bombadil.infradead.org> (raw)
In-Reply-To: <20210319083540.31016-1-unixbhaskar@gmail.com>
On Fri, 19 Mar 2021, Bhaskar Chowdhury wrote:
>
> s/boudary/boundary/
> s/compliled/compiled/
>
> Signed-off-by: Bhaskar Chowdhury <unixbhaskar@gmail.com>
Acked-by: Randy Dunlap <rdunlap@infradead.org>
> ---
> crypto/async_tx/raid6test.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/crypto/async_tx/raid6test.c b/crypto/async_tx/raid6test.c
> index 66db82e5a3b1..c9d218e53bcb 100644
> --- a/crypto/async_tx/raid6test.c
> +++ b/crypto/async_tx/raid6test.c
> @@ -217,7 +217,7 @@ static int raid6_test(void)
> err += test(12, &tests);
> }
>
> - /* the 24 disk case is special for ioatdma as it is the boudary point
> + /* the 24 disk case is special for ioatdma as it is the boundary point
> * at which it needs to switch from 8-source ops to 16-source
> * ops for continuation (assumes DMA_HAS_PQ_CONTINUE is not set)
> */
> @@ -241,7 +241,7 @@ static void raid6_test_exit(void)
> }
>
> /* when compiled-in wait for drivers to load first (assumes dma drivers
> - * are also compliled-in)
> + * are also compiled-in)
> */
> late_initcall(raid6_test);
> module_exit(raid6_test_exit);
> --
> 2.26.2
>
>
prev parent reply other threads:[~2021-03-19 17:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-19 8:35 [PATCH] md/raid6: Couple of typo fixes Bhaskar Chowdhury
2021-03-19 16:07 ` Randy Dunlap [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2b59cdc-fdb7-be14-ebdc-a49b47594b32@bombadil.infradead.org \
--to=rdunlap@bombadil.infradead.org \
--cc=dan.j.williams@intel.com \
--cc=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=songliubraving@fb.com \
--cc=unixbhaskar@gmail.com \
--cc=yuyufen@huawei.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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).