linux-man.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Michael Kerrisk (man-pages)" <mtk.manpages@gmail.com>
To: Matti Moell <Matti.Moell@opensynergy.com>
Cc: mtk.manpages@gmail.com, linux-man@vger.kernel.org,
	linux-aio@vger.kernel.org,
	Damir Shaikhutdinov <Damir.Shaikhutdinov@opensynergy.com>
Subject: Re: [PATCH v2] io_submit.2: Fix kernel version numbers for 'aio_rw_flags' flags
Date: Fri, 13 Sep 2019 13:57:39 +0200	[thread overview]
Message-ID: <3410f0f4-9608-879a-a994-2479343ce186@gmail.com> (raw)
In-Reply-To: <852f4b43-b2ca-6823-7c42-2e8c766f79e9@opensynergy.com>

Hello Matti,

On 8/20/19 7:04 PM, Matti Moell wrote:
> Even though the RFW_* flags were first introduced in Linux 4.6, they
> could not be used with aio until 4.13 where the aio_rw_flags field was
> added to struct iocb (9830f4be159b "fs: Use RWF_* flags for AIO
> operations"). Correct the stated version for each flag.
> 
> Fixes: 2f72816f8680 ("io_submit.2: Add kernel version numbers for various 'aio_rw_flags' flags")
> Signed-off-by: Matti Möll <Matti.Moell@opensynergy.com>

Thanks. Patch applied.

Cheers,

Michael


> ---
> Changelog:
> v2:
>  - Fix kernel version from 4.12 to 4.13
> ---
>  man2/io_submit.2 | 6 +++---
>  1 file changed, 3 insertions(+), 3 deletions(-)
> 
> diff --git a/man2/io_submit.2 b/man2/io_submit.2
> index ed98da46c999..1b5fd405a00e 100644
> --- a/man2/io_submit.2
> +++ b/man2/io_submit.2
> @@ -91,7 +91,7 @@ The
>  field is ignored.
>  The file offset is not changed.
>  .TP
> -.BR RWF_DSYNC " (since Linux 4.7)"
> +.BR RWF_DSYNC " (since Linux 4.13)"
>  Write operation complete according to requirement of
>  synchronized I/O data integrity.
>  See the description of the flag of the same name in
> @@ -101,7 +101,7 @@ as well the description of
>  in
>  .BR open (2).
>  .TP
> -.BR RWF_HIPRI " (since Linux 4.6)"
> +.BR RWF_HIPRI " (since Linux 4.13)"
>  High priority request, poll if possible
>  .TP
>  .BR RWF_NOWAIT " (since Linux 4.14)"
> @@ -118,7 +118,7 @@ field of the
>  structure (see
>  .BR io_getevents (2)).
>  .TP
> -.BR RWF_SYNC " (since Linux 4.7)"
> +.BR RWF_SYNC " (since Linux 4.13)"
>  Write operation complete according to requirement of
>  synchronized I/O file integrity.
>  See the description of the flag of the same name in
> 


-- 
Michael Kerrisk
Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/
Linux/UNIX System Programming Training: http://man7.org/training/

      reply	other threads:[~2019-09-13 11:57 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-20 17:04 [PATCH v2] io_submit.2: Fix kernel version numbers for 'aio_rw_flags' flags Matti Moell
2019-09-13 11:57 ` 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=3410f0f4-9608-879a-a994-2479343ce186@gmail.com \
    --to=mtk.manpages@gmail.com \
    --cc=Damir.Shaikhutdinov@opensynergy.com \
    --cc=Matti.Moell@opensynergy.com \
    --cc=linux-aio@vger.kernel.org \
    --cc=linux-man@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).