linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dominique Martinet <asmadeus@codewreck.org>
To: piaojun <piaojun@huawei.com>
Cc: Eric Van Hensbergen <ericvh@gmail.com>,
	Ron Minnich <rminnich@sandia.gov>,
	Latchesar Ionkov <lucho@ionkov.net>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	v9fs-developer@lists.sourceforge.net,
	"akpm@linux-foundation.org" <akpm@linux-foundation.org>
Subject: Re: [PATCH] net/9p/trans_virtio.c: fix some spell mistakes in comments
Date: Wed, 18 Jul 2018 05:49:31 +0200	[thread overview]
Message-ID: <20180718034931.GA27247@nautica> (raw)
In-Reply-To: <5B4EB7D9.9010108@huawei.com>

piaojun wrote on Wed, Jul 18, 2018:
> Fix spelling mistake in comments of p9_virtio_zc_request().
> 
> Signed-off-by: Jun Piao <piaojun@huawei.com>

Thanks, queued it.

> ---
>  net/9p/trans_virtio.c | 4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)
> 
> diff --git a/net/9p/trans_virtio.c b/net/9p/trans_virtio.c
> index c9f2717..86077f7 100644
> --- a/net/9p/trans_virtio.c
> +++ b/net/9p/trans_virtio.c
> @@ -384,8 +384,8 @@ static int p9_get_mapped_pages(struct virtio_chan *chan,
>   * p9_virtio_zc_request - issue a zero copy request
>   * @client: client instance issuing the request
>   * @req: request to be issued
> - * @uidata: user bffer that should be ued for zero copy read
> - * @uodata: user buffer that shoud be user for zero copy write
> + * @uidata: user buffer that should be used for zero copy read
> + * @uodata: user buffer that should be used for zero copy write
>   * @inlen: read buffer size
>   * @outlen: write buffer size
>   * @in_hdr_len: reader header size, This is the size of response protocol data

-- 
Dominique Martinet

      reply	other threads:[~2018-07-18  3:49 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-18  3:45 [PATCH] net/9p/trans_virtio.c: fix some spell mistakes in comments piaojun
2018-07-18  3:49 ` Dominique Martinet [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=20180718034931.GA27247@nautica \
    --to=asmadeus@codewreck.org \
    --cc=akpm@linux-foundation.org \
    --cc=ericvh@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lucho@ionkov.net \
    --cc=piaojun@huawei.com \
    --cc=rminnich@sandia.gov \
    --cc=v9fs-developer@lists.sourceforge.net \
    /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).