All of lore.kernel.org
 help / color / mirror / Atom feed
From: Leon Romanovsky <leon@kernel.org>
To: Ruslan Vagner <rusya92266@gmail.com>
Cc: linux-rdma@vger.kernel.org, jgg@nvidia.com
Subject: Re: [PATCH] RDMA/qedr: fix comment typo in verbs.c
Date: Tue, 15 Sep 2026 21:35:48 +0300	[thread overview]
Message-ID: <20260915183548.GP13683@unreal> (raw)
In-Reply-To: <CAF9RqJ66ApKFeMwr59AYXHpDO2FOL=NCuvG=q3NaTxR4yEg1NQ@mail.gmail.com>

On Tue, Sep 15, 2026 at 07:55:56AM -0500, Ruslan Vagner wrote:
> Fix the spelling in comments. No functional change.
> 
> Signed-off-by: Ruslan Vagner <rusya92266@gmail.com>
> ---
>  drivers/infiniband/hw/qedr/verbs.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)

It was already fixed in commit ea42dc093681 ("RDMA: fix typos in comments")
https://lore.kernel.org/all/20260907065047.26773-2-hemanth.selam@gmail.com/

Thanks

> 
> diff --git a/drivers/infiniband/hw/qedr/verbs.c
> b/drivers/infiniband/hw/qedr/verbs.c
> index 012a0ab98d6b..973d0fa7cdce 100644
> --- a/drivers/infiniband/hw/qedr/verbs.c
> +++ b/drivers/infiniband/hw/qedr/verbs.c
> @@ -1075,7 +1075,7 @@ int qedr_destroy_cq(struct ib_cq *ibcq, struct
> ib_udata *udata)
>  	/* We don't want the IRQ handler to handle a non-existing CQ so we
>  	 * wait until all CNQ interrupts, if any, are received. This will always
>  	 * happen and will always happen very fast. If not, then a serious error
> -	 * has occured. That is why we can use a long delay.
> +	 * has occurred. That is why we can use a long delay.
>  	 * We spin for a short time so we don’t lose time on context switching
>  	 * in case all the completions are handled in that span. Otherwise
>  	 * we sleep for a while and check again. Since the CNQ may be
> -- 
> 2.54.0.windows.1
> 

      reply	other threads:[~2026-09-15 18:35 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-15 12:55 [PATCH] RDMA/qedr: fix comment typo in verbs.c Ruslan Vagner
2026-09-15 18:35 ` Leon Romanovsky [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=20260915183548.GP13683@unreal \
    --to=leon@kernel.org \
    --cc=jgg@nvidia.com \
    --cc=linux-rdma@vger.kernel.org \
    --cc=rusya92266@gmail.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 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.