From: Miklos Szeredi <miklos@szeredi.hu>
To: Zheng Yongjun <zhengyongjun3@huawei.com>
Cc: linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH -next] virtiofs: Fix spelling mistakes
Date: Mon, 21 Jun 2021 10:44:48 +0200 [thread overview]
Message-ID: <CAJfpegv3XMq_mBtcMaPP8c66nrtuQs4b1Por3btJDPVz4jH88w@mail.gmail.com> (raw)
In-Reply-To: <20210604014617.2086760-1-zhengyongjun3@huawei.com>
On Fri, 4 Jun 2021 at 03:32, Zheng Yongjun <zhengyongjun3@huawei.com> wrote:
>
> Fix some spelling mistakes in comments:
> refernce ==> reference
> happnes ==> happens
> threhold ==> threshold
> splitted ==> split
> mached ==> matched
>
> Signed-off-by: Zheng Yongjun <zhengyongjun3@huawei.com>
Thanks, applied.
Miklos
prev parent reply other threads:[~2021-06-21 8:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-04 1:46 [PATCH -next] virtiofs: Fix spelling mistakes Zheng Yongjun
2021-06-21 8:44 ` Miklos Szeredi [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=CAJfpegv3XMq_mBtcMaPP8c66nrtuQs4b1Por3btJDPVz4jH88w@mail.gmail.com \
--to=miklos@szeredi.hu \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=zhengyongjun3@huawei.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).