From: liweihang <liweihang@huawei.com>
To: Bhaskar Chowdhury <unixbhaskar@gmail.com>,
oulijun <oulijun@huawei.com>,
"huwei87@hisilicon.com" <huwei87@hisilicon.com>,
"dledford@redhat.com" <dledford@redhat.com>,
"jgg@ziepe.ca" <jgg@ziepe.ca>, "dt@kernel.org" <dt@kernel.org>,
"linux-rdma@vger.kernel.org" <linux-rdma@vger.kernel.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Cc: "rdunlap@infradead.org" <rdunlap@infradead.org>
Subject: Re: [PATCH] IB/hns: Fix a spelling
Date: Mon, 22 Mar 2021 02:43:27 +0000 [thread overview]
Message-ID: <5d404e23725a4c62b06c4a00875c7312@huawei.com> (raw)
In-Reply-To: 20210322022751.4137205-1-unixbhaskar@gmail.com
On 2021/3/22 10:28, Bhaskar Chowdhury wrote:
>
> s/wubsytem/subsystem/
>
> Signed-off-by: Bhaskar Chowdhury <unixbhaskar@gmail.com>
> ---
> .../devicetree/bindings/infiniband/hisilicon-hns-roce.txt | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/Documentation/devicetree/bindings/infiniband/hisilicon-hns-roce.txt b/Documentation/devicetree/bindings/infiniband/hisilicon-hns-roce.txt
> index 84f1a1b505d2..c57e09099bcb 100644
> --- a/Documentation/devicetree/bindings/infiniband/hisilicon-hns-roce.txt
> +++ b/Documentation/devicetree/bindings/infiniband/hisilicon-hns-roce.txt
> @@ -1,7 +1,7 @@
> Hisilicon RoCE DT description
>
> Hisilicon RoCE engine is a part of network subsystem.
> -It works depending on other part of network wubsytem, such as, gmac and
> +It works depending on other part of network subsystem, such as, gmac and
> dsa fabric.
>
> Additional properties are described here:
> --
> 2.31.0
>
>
Thank you.
Acked-by: Weihang Li <liweihang@huawei.com>
next prev parent reply other threads:[~2021-03-22 2:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-22 2:27 [PATCH] IB/hns: Fix a spelling Bhaskar Chowdhury
2021-03-22 2:43 ` liweihang [this message]
2021-03-22 2:54 ` Randy Dunlap
2021-03-23 0:45 ` 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=5d404e23725a4c62b06c4a00875c7312@huawei.com \
--to=liweihang@huawei.com \
--cc=devicetree@vger.kernel.org \
--cc=dledford@redhat.com \
--cc=dt@kernel.org \
--cc=huwei87@hisilicon.com \
--cc=jgg@ziepe.ca \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=oulijun@huawei.com \
--cc=rdunlap@infradead.org \
--cc=unixbhaskar@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