From: Leon Romanovsky <leon@kernel.org>
To: Rohit Chavan <roheetchavan@gmail.com>
Cc: Jason Gunthorpe <jgg@ziepe.ca>,
linux-rdma@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] RDMA/core: Fix repeated words in comments
Date: Mon, 11 Sep 2023 12:55:00 +0300 [thread overview]
Message-ID: <20230911095500.GA19469@unreal> (raw)
In-Reply-To: <20230822174857.9003-1-roheetchavan@gmail.com>
On Tue, Aug 22, 2023 at 11:18:57PM +0530, Rohit Chavan wrote:
> Corrected the repeated words in the documentation for
> rdma_replace_ah_attr and ah_attribute.
>
> Signed-off-by: Rohit Chavan <roheetchavan@gmail.com>
> ---
> drivers/infiniband/core/verbs.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/infiniband/core/verbs.c b/drivers/infiniband/core/verbs.c
> index b99b3cc283b6..0c5b24ce3966 100644
> --- a/drivers/infiniband/core/verbs.c
> +++ b/drivers/infiniband/core/verbs.c
> @@ -366,7 +366,7 @@ void rdma_copy_ah_attr(struct rdma_ah_attr *dest,
> EXPORT_SYMBOL(rdma_copy_ah_attr);
>
> /**
> - * rdma_replace_ah_attr - Replace valid ah_attr with new one.
> + * rdma_replace_ah_attr - Replace valid ah_attr with new one.
<...>
> - * ah_attribute must have valid port_num, sgid_index.
> + * ah_attribute must have valid port_num, sgid_index.
What does this patch fix/change?
Thanks
> */
> static int ib_resolve_unicast_gid_dmac(struct ib_device *device,
> struct rdma_ah_attr *ah_attr)
> --
> 2.30.2
>
next prev parent reply other threads:[~2023-09-11 22:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-22 17:48 [PATCH] RDMA/core: Fix repeated words in comments Rohit Chavan
2023-09-11 9:55 ` Leon Romanovsky [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-08-24 8:13 Rohit Chavan
2023-09-11 11:15 ` Leon Romanovsky
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=20230911095500.GA19469@unreal \
--to=leon@kernel.org \
--cc=jgg@ziepe.ca \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=roheetchavan@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 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).