From: Leon Romanovsky <leon@kernel.org>
To: "Daisuke Matsuda (Fujitsu)" <matsuda-daisuke@fujitsu.com>
Cc: 'Deming Wang' <wangdeming@inspur.com>,
"jgg@ziepe.ca" <jgg@ziepe.ca>,
"linux-rdma@vger.kernel.org" <linux-rdma@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] RDMA/restrack: Correct spelling
Date: Tue, 7 Feb 2023 11:26:50 +0200 [thread overview]
Message-ID: <Y+IZWiRiNHtSKRdk@unreal> (raw)
In-Reply-To: <TYCPR01MB84550C2753CC434A4A3A48ADE5DA9@TYCPR01MB8455.jpnprd01.prod.outlook.com>
On Mon, Feb 06, 2023 at 09:08:06AM +0000, Daisuke Matsuda (Fujitsu) wrote:
> On Mon, Feb 6, 2023 5:57 PM Deming Wang wrote:
> >
> > We should use this replace thie.
> >
> > Signed-off-by: Deming Wang <wangdeming@inspur.com>
> > ---
> > include/rdma/restrack.h | 2 +-
> > 1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > diff --git a/include/rdma/restrack.h b/include/rdma/restrack.h
> > index 79d109c47242..d7ee54b7b9ae 100644
> > --- a/include/rdma/restrack.h
> > +++ b/include/rdma/restrack.h
> > @@ -162,7 +162,7 @@ struct rdma_restrack_entry *rdma_restrack_get_byid(struct ib_device *dev,
> > * rdma_restrack_no_track() - don't add resource to the DB
> > * @res: resource entry
> > *
> > - * Every user of thie API should be cross examined.
> > + * Every user of this API should be cross examined.
> > * Probaby you don't need to use this function.
>
> 'Probably' instead of 'Probaby', right?
I fixed it locally, thanks.
>
> Daisuke
>
> > */
> > static inline void rdma_restrack_no_track(struct rdma_restrack_entry *res)
> > --
> > 2.27.0
>
next prev parent reply other threads:[~2023-02-07 9:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-06 8:57 [PATCH] RDMA/restrack: Correct spelling Deming Wang
2023-02-06 9:08 ` Daisuke Matsuda (Fujitsu)
2023-02-07 9:26 ` Leon Romanovsky [this message]
2023-02-07 9:25 ` 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=Y+IZWiRiNHtSKRdk@unreal \
--to=leon@kernel.org \
--cc=jgg@ziepe.ca \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=matsuda-daisuke@fujitsu.com \
--cc=wangdeming@inspur.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