From: Jonathan Corbet <corbet@lwn.net>
To: jgq516@gmail.com
Cc: axboe@kernel.dk, linux-block@vger.kernel.org,
Guoqing Jiang <guoqing.jiang@cloud.ionos.com>
Subject: Re: [PATCH] docs: block/biovecs: update the location of bio.c
Date: Fri, 10 Jan 2020 10:23:59 -0700 [thread overview]
Message-ID: <20200110102359.6adf4a37@lwn.net> (raw)
In-Reply-To: <20200106103735.10327-1-guoqing.jiang@cloud.ionos.com>
On Mon, 6 Jan 2020 11:37:35 +0100
jgq516@gmail.com wrote:
> From: Guoqing Jiang <guoqing.jiang@cloud.ionos.com>
>
> Replace fs with block since bio.c had been moved to block folder.
>
> Signed-off-by: Guoqing Jiang <guoqing.jiang@cloud.ionos.com>
> ---
> Documentation/block/biovecs.rst | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/Documentation/block/biovecs.rst b/Documentation/block/biovecs.rst
> index 86fa66c87172..ad303a2569d3 100644
> --- a/Documentation/block/biovecs.rst
> +++ b/Documentation/block/biovecs.rst
> @@ -47,7 +47,7 @@ Having a real iterator, and making biovecs immutable, has a number of
> advantages:
>
> * Before, iterating over bios was very awkward when you weren't processing
> - exactly one bvec at a time - for example, bio_copy_data() in fs/bio.c,
> + exactly one bvec at a time - for example, bio_copy_data() in block/bio.c,
> which copies the contents of one bio into another. Because the biovecs
Applied, thanks.
jon
prev parent reply other threads:[~2020-01-10 17:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-06 10:37 [PATCH] docs: block/biovecs: update the location of bio.c jgq516
2020-01-08 3:05 ` Bart Van Assche
2020-01-10 17:23 ` Jonathan Corbet [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=20200110102359.6adf4a37@lwn.net \
--to=corbet@lwn.net \
--cc=axboe@kernel.dk \
--cc=guoqing.jiang@cloud.ionos.com \
--cc=jgq516@gmail.com \
--cc=linux-block@vger.kernel.org \
/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).