From: "Michael Kerrisk (man-pages)" <mtk.manpages@gmail.com>
To: Yang Xu <xuyang2018.jy@cn.fujitsu.com>, linux-man@vger.kernel.org
Cc: mtk.manpages@gmail.com
Subject: Re: [PATCH v2 1/3] loop.4: Document LO_FLAGS_DIRECT_IO flag
Date: Wed, 9 Sep 2020 11:06:34 +0200 [thread overview]
Message-ID: <4ee43f80-cbcf-285a-d431-95824eb42dd6@gmail.com> (raw)
In-Reply-To: <1596707314-2361-1-git-send-email-xuyang2018.jy@cn.fujitsu.com>
On 8/6/20 11:48 AM, Yang Xu wrote:
> Signed-off-by: Yang Xu <xuyang2018.jy@cn.fujitsu.com>
> ---
> man4/loop.4 | 4 ++++
> 1 file changed, 4 insertions(+)
Thanks, Yang Xu. Patch applied.
Cheers,
Michael
>
> diff --git a/man4/loop.4 b/man4/loop.4
> index a3c59310d..1f8a31ac7 100644
> --- a/man4/loop.4
> +++ b/man4/loop.4
> @@ -130,6 +130,10 @@ The loopback device will autodestruct on last close.
> .BR LO_FLAGS_PARTSCAN " (since Linux 3.2)"
> .\" commit e03c8dd14915fabc101aa495828d58598dc5af98
> Allow automatic partition scanning.
> +.TP
> +.BR LO_FLAGS_DIRECT_IO " (since Linux 4.10)"
> +.\" commit 2e5ab5f379f96a6207c45be40c357ebb1beb8ef3
> +Use direct io mode to access backing file.
> .RE
> .TP
> .B LOOP_GET_STATUS
>
--
Michael Kerrisk
Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/
Linux/UNIX System Programming Training: http://man7.org/training/
prev parent reply other threads:[~2020-09-09 9:06 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-06 9:48 [PATCH v2 1/3] loop.4: Document LO_FLAGS_DIRECT_IO flag Yang Xu
2020-08-06 9:48 ` [PATCH v2 2/3] loop.4: add some details about lo_flag Yang Xu
2020-08-07 7:36 ` AW: " Walter Harms
2020-08-10 6:53 ` Yang Xu
2020-08-10 7:39 ` AW: " Walter Harms
2020-09-08 9:55 ` Yang Xu
2020-09-09 9:06 ` Michael Kerrisk (man-pages)
2020-09-09 11:17 ` Yang Xu
2020-08-06 9:48 ` [PATCH v2 3/3] loop.4: Document loop_configure ioctl Yang Xu
2020-09-09 9:17 ` Michael Kerrisk (man-pages)
2020-09-09 11:20 ` Yang Xu
2020-09-09 9:06 ` Michael Kerrisk (man-pages) [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=4ee43f80-cbcf-285a-d431-95824eb42dd6@gmail.com \
--to=mtk.manpages@gmail.com \
--cc=linux-man@vger.kernel.org \
--cc=xuyang2018.jy@cn.fujitsu.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.