public inbox for linux-man@vger.kernel.org
 help / color / mirror / Atom feed
From: Alejandro Colomar <alx@kernel.org>
To: John Garry <john.g.garry@oracle.com>
Cc: linux-man@vger.kernel.org, linux-fsdevel@vger.kernel.org,
	dalias@libc.org, brauner@kernel.org
Subject: Re: [PATCH 2/2] io_submit.2: Document RWF_NOAPPEND flag
Date: Tue, 26 Nov 2024 12:55:11 +0100	[thread overview]
Message-ID: <20241126115511.aw4igyvlrd2ak7dz@devuan> (raw)
In-Reply-To: <20241126090847.297371-3-john.g.garry@oracle.com>

[-- Attachment #1: Type: text/plain, Size: 1096 bytes --]

Hi John,

On Tue, Nov 26, 2024 at 09:08:47AM +0000, John Garry wrote:
> Document flag introduced in Linux v6.9
> 
> Signed-off-by: John Garry <john.g.garry@oracle.com>

Please add the Cc:s also to the patch trailer section.  (That means less
work for me pasting them.:)

> ---
>  man/man2/io_submit.2 | 10 ++++++++++
>  1 file changed, 10 insertions(+)
> 
> diff --git a/man/man2/io_submit.2 b/man/man2/io_submit.2
> index c3d86b4c4..64292037d 100644
> --- a/man/man2/io_submit.2
> +++ b/man/man2/io_submit.2
> @@ -141,6 +141,16 @@ as well the description of
>  in
>  .BR open (2).
>  .TP
> +.BR RWF_NOAPPEND " (since Linux 6.9)"
> +Do not honor
> +.B O_APPEND
> +.BR open (2)
> +flag.
> +See the description of
> +.B RWF_NOAPPEND
> +in
> +.BR pwritev2 (2).

LGTM.  Thanks!  I'll wait to apply it once patch 1/2 is applied.

Have a lovely day!
Alex

> +.TP
>  .BR RWF_ATOMIC " (since Linux 6.11)"
>  Write a block of data such that
>  a write will never be torn from power fail or similar.
> -- 
> 2.31.1
> 

-- 
<https://www.alejandro-colomar.es/>

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2024-11-26 11:55 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-26  9:08 [PATCH 0/2] man2: Document RWF_NOAPPEND John Garry
2024-11-26  9:08 ` [PATCH 1/2] readv.2: Document RWF_NOAPPEND flag John Garry
2024-11-26 11:52   ` Alejandro Colomar
2024-11-26 11:57     ` John Garry
2025-01-04 20:34       ` Alejandro Colomar
2024-11-26  9:08 ` [PATCH 2/2] io_submit.2: " John Garry
2024-11-26 11:55   ` Alejandro Colomar [this message]
2025-01-04 20:36   ` Alejandro Colomar
2024-12-16 10:33 ` [PATCH 0/2] man2: Document RWF_NOAPPEND John Garry
2025-01-04 20:17   ` Alejandro Colomar

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=20241126115511.aw4igyvlrd2ak7dz@devuan \
    --to=alx@kernel.org \
    --cc=brauner@kernel.org \
    --cc=dalias@libc.org \
    --cc=john.g.garry@oracle.com \
    --cc=linux-fsdevel@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