From: Christoph Hellwig <hch@lst.de>
To: "Michael Kerrisk (man-pages)" <mtk.manpages@gmail.com>
Cc: Matthew Wilcox <willy@infradead.org>,
Christoph Hellwig <hch@lst.de>,
linux-man <linux-man@vger.kernel.org>,
"linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>,
Milosz Tanski <milosz@adfin.com>
Subject: Re: [PATCH] readv.2: document RWF_NOWAIT
Date: Thu, 9 Nov 2017 16:01:34 +0100 [thread overview]
Message-ID: <20171109150133.GA25025@lst.de> (raw)
In-Reply-To: <CAKgNAkhbNxpKLcO8aGS0rid2iZSUi76NY7e5WTh1BmY7NNcKWA@mail.gmail.com>
On Thu, Nov 09, 2017 at 02:40:38PM +0100, Michael Kerrisk (man-pages) wrote:
> > The phrasing is a bit tortured ... try this:
> >
> > .TP
> > .BR RWF_NOWAIT " (since Linux 4.14)"
> > Do not wait for data which is not immediately available.
> > If this flag is specified the
> > .BR preadv2 ()
> > system call will return instantly if it would have to read data from
> > the backing storage or wait for a lock.
> > If some data was successfully read, it will return the number of bytes read.
> > If no bytes were read, it will return -1 and set
> > .IR errno to
> > .BR EAGAIN .
> > This flag is meaningful only for
> > .BR preadv2 ()
> > at the moment.
> > .\" commit 3239d834847627b6634a4139cf1dc58f6f137a46
> > .\" commit 91f9943e1c7b6638f27312d03fe71fcc67b23571
>
> What are your thoughts on Matthew's proposed rewording?
The look good to me. I'll try to find some time to respin the patch
with them incorporated.
prev parent reply other threads:[~2017-11-09 15:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-29 8:40 [PATCH] readv.2: document RWF_NOWAIT Christoph Hellwig
2017-10-29 9:17 ` Silvan Jegen
2017-10-29 9:41 ` Matthew Wilcox
2017-11-09 13:40 ` Michael Kerrisk (man-pages)
2017-11-09 15:01 ` Christoph Hellwig [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=20171109150133.GA25025@lst.de \
--to=hch@lst.de \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-man@vger.kernel.org \
--cc=milosz@adfin.com \
--cc=mtk.manpages@gmail.com \
--cc=willy@infradead.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).