From: John Garry <john.g.garry@oracle.com>
To: Alejandro Colomar <alx@kernel.org>
Cc: linux-man@vger.kernel.org, linux-fsdevel@vger.kernel.org,
axboe@kernel.dk, hch@lst.de, djwong@kernel.org,
dchinner@redhat.com, martin.petersen@oracle.com
Subject: Re: [PATCH v3 3/3] io_submit.2: Document RWF_ATOMIC
Date: Wed, 10 Jul 2024 11:13:09 +0100 [thread overview]
Message-ID: <4a51397a-85d9-4467-80f8-0d4c3d997eae@oracle.com> (raw)
In-Reply-To: <zonwu3dsyz6fk5unic2rgxqpvrceqrtj4k5epb6hdj44fbzxkm@vbfqorsyw7te>
On 09/07/2024 17:53, Alejandro Colomar wrote:
>>> +.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. See the description
>>> +of the flag of the same name in
>> Maybe?:
>>
>> of this same flag in
> Or just to be less ambiguous:
>
> See the description of
> .B RWF_ATOMIC
> in
ok, that seems better.
Thanks,
John
next prev parent reply other threads:[~2024-07-10 10:13 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-08 11:42 [PATCH v3 0/3] man2: Document RWF_ATOMIC John Garry
2024-07-08 11:42 ` [PATCH v3 1/3] statx.2: Document STATX_WRITE_ATOMIC John Garry
2024-07-09 16:48 ` Alejandro Colomar
2024-07-10 10:11 ` John Garry
2024-07-10 10:23 ` Alejandro Colomar
2024-07-08 11:42 ` [PATCH v3 2/3] readv.2: Document RWF_ATOMIC flag John Garry
2024-07-09 16:51 ` Alejandro Colomar
2024-07-08 11:42 ` [PATCH v3 3/3] io_submit.2: Document RWF_ATOMIC John Garry
2024-07-09 16:52 ` Alejandro Colomar
2024-07-09 16:53 ` Alejandro Colomar
2024-07-10 10:13 ` John Garry [this message]
2024-07-09 16:43 ` [PATCH v3 0/3] man2: " Alejandro Colomar
2024-07-10 10:07 ` John Garry
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=4a51397a-85d9-4467-80f8-0d4c3d997eae@oracle.com \
--to=john.g.garry@oracle.com \
--cc=alx@kernel.org \
--cc=axboe@kernel.dk \
--cc=dchinner@redhat.com \
--cc=djwong@kernel.org \
--cc=hch@lst.de \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-man@vger.kernel.org \
--cc=martin.petersen@oracle.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 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).