From: "Michael Kerrisk (man-pages)" <mtk.manpages@gmail.com>
To: Mike Christie <mchristi@redhat.com>
Cc: Bart Van Assche <bvanassche@acm.org>,
Linux API <linux-api@vger.kernel.org>,
Dave Chinner <david@fromorbit.com>,
Michal Hocko <mhocko@suse.com>,
masato.suzuki@wdc.com, damien.lemoal@wdc.com,
"Darrick J. Wong" <darrick.wong@oracle.com>,
linux-man <linux-man@vger.kernel.org>
Subject: Re: [PATCH] prctl.2: doc PR_SET/GET_IO_FLUSHER - V4
Date: Thu, 2 Apr 2020 22:12:25 +0200 [thread overview]
Message-ID: <CAKgNAki_5SBbQJdjg1j0i5BvfUu7sXUiBbgBU8QJY+Av-Ok-pg@mail.gmail.com> (raw)
In-Reply-To: <c2451ffc-da39-9914-2d2e-e3a9a8356298@redhat.com>
On Thu, 2 Apr 2020 at 16:01, Michael Christie <mchristi@redhat.com> wrote:
>
> On 04/01/2020 10:46 PM, Bart Van Assche wrote:
> > On 2020-04-01 19:08, Mike Christie wrote:
> >> +.TP
> >> +.B PR_GET_IO_FLUSHER (Since Linux 5.6)
> >> +Return as the function result 1 if the caller is in the IO_FLUSHER state and
> >> +0 if not.
> >
> > Although I'm not at all a language expert, the word order at the start
> > of the above sentence seems a bit weird to me?
> >
>
> Do you mean the "Return as the function result" part or something else?
>
> That is how the other commands worded it. It looks like I messed up and
> dropped the (). This is how they did it:
>
> "Return (as the function result)"
>
> I will resend with that fix.
>
> If I misunderstood you I will fix that too.
I already fixed this piece. There are still the open questions in my
other mail though.
--
Michael Kerrisk
Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/
Linux/UNIX System Programming Training: http://man7.org/training/
next prev parent reply other threads:[~2020-04-02 20:12 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-02 2:08 [PATCH] prctl.2: doc PR_SET/GET_IO_FLUSHER - V4 Mike Christie
2020-04-02 3:46 ` Bart Van Assche
2020-04-02 12:16 ` Michael Kerrisk (man-pages)
2020-04-02 14:01 ` Michael Christie
2020-04-02 20:12 ` Michael Kerrisk (man-pages) [this message]
2020-04-02 6:47 ` Michal Hocko
2020-04-02 12:16 ` Michael Kerrisk (man-pages)
2020-04-02 12:16 ` Michael Kerrisk (man-pages)
2020-04-04 21:07 ` Mike Christie
2020-04-06 11:00 ` Michael Kerrisk (man-pages)
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=CAKgNAki_5SBbQJdjg1j0i5BvfUu7sXUiBbgBU8QJY+Av-Ok-pg@mail.gmail.com \
--to=mtk.manpages@gmail.com \
--cc=bvanassche@acm.org \
--cc=damien.lemoal@wdc.com \
--cc=darrick.wong@oracle.com \
--cc=david@fromorbit.com \
--cc=linux-api@vger.kernel.org \
--cc=linux-man@vger.kernel.org \
--cc=masato.suzuki@wdc.com \
--cc=mchristi@redhat.com \
--cc=mhocko@suse.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).