All of lore.kernel.org
 help / color / mirror / Atom feed
From: Max Gurtovoy <mgurtovoy@nvidia.com>
To: Julia Lawall <Julia.Lawall@inria.fr>, Sagi Grimberg <sagi@grimberg.me>
Cc: kernel-janitors@vger.kernel.org, Jason Gunthorpe <jgg@ziepe.ca>,
	Leon Romanovsky <leon@kernel.org>,
	linux-rdma@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] IB/iser: fix typo in comment
Date: Sun, 22 May 2022 11:32:18 +0300	[thread overview]
Message-ID: <3cbd35dc-2e63-26c4-7258-012009a97dd9@nvidia.com> (raw)
In-Reply-To: <20220521111145.81697-4-Julia.Lawall@inria.fr>


On 5/21/2022 2:10 PM, Julia Lawall wrote:
> Spelling mistake (triple letters) in comment.
> Detected with the help of Coccinelle.
>
> Signed-off-by: Julia Lawall <Julia.Lawall@inria.fr>
>
> ---
>   drivers/infiniband/ulp/iser/iscsi_iser.h |    2 +-
>   1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/infiniband/ulp/iser/iscsi_iser.h b/drivers/infiniband/ulp/iser/iscsi_iser.h
> index 7e4faf9c5e9e..dee8c97ff056 100644
> --- a/drivers/infiniband/ulp/iser/iscsi_iser.h
> +++ b/drivers/infiniband/ulp/iser/iscsi_iser.h
> @@ -363,7 +363,7 @@ struct iser_fr_pool {
>    * @cq:                  Connection completion queue
>    * @cq_size:             The number of max outstanding completions
>    * @device:              reference to iser device
> - * @fr_pool:             connection fast registration poool
> + * @fr_pool:             connection fast registration pool
>    * @pi_support:          Indicate device T10-PI support
>    * @reg_cqe:             completion handler
>    */

Looks good,

Acked-by: Max Gurtovoy <mgurtovoy@nvidia.com>



  parent reply	other threads:[~2022-05-22  8:32 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-21 11:10 [PATCH] IB/iser: fix typo in comment Julia Lawall
2022-05-21 20:03 ` Sagi Grimberg
2022-05-22  8:32 ` Max Gurtovoy [this message]
2022-05-24 14:30 ` Jason Gunthorpe

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=3cbd35dc-2e63-26c4-7258-012009a97dd9@nvidia.com \
    --to=mgurtovoy@nvidia.com \
    --cc=Julia.Lawall@inria.fr \
    --cc=jgg@ziepe.ca \
    --cc=kernel-janitors@vger.kernel.org \
    --cc=leon@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rdma@vger.kernel.org \
    --cc=sagi@grimberg.me \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.