From: Jonathan Corbet <corbet@lwn.net>
To: Julia Lawall <Julia.Lawall@inria.fr>
Cc: kernel-janitors@vger.kernel.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] docs: filesystems: vfs: correct sync_mode flag names
Date: Mon, 27 Jul 2020 16:15:49 -0600 [thread overview]
Message-ID: <20200727161549.1d3e31a0@lwn.net> (raw)
In-Reply-To: <1595791341-13209-1-git-send-email-Julia.Lawall@inria.fr>
On Sun, 26 Jul 2020 21:22:21 +0200
Julia Lawall <Julia.Lawall@inria.fr> wrote:
> Change the nonexistent flag names WBC_SYNC_ALL and WBC_SYNC_NONE to
> WB_SYNC_ALL and WB_SYNC_NONE, respectively, as used in the code with
> wbc->sync_mode.
>
> Signed-off-by: Julia Lawall <Julia.Lawall@inria.fr>
>
> ---
> Documentation/filesystems/vfs.rst | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/Documentation/filesystems/vfs.rst b/Documentation/filesystems/vfs.rst
> index da4b735..57e9b51 100644
> --- a/Documentation/filesystems/vfs.rst
> +++ b/Documentation/filesystems/vfs.rst
> @@ -766,9 +766,9 @@ cache in your filesystem. The following members are defined:
>
> ``writepages``
> called by the VM to write out pages associated with the
> - address_space object. If wbc->sync_mode is WBC_SYNC_ALL, then
> + address_space object. If wbc->sync_mode is WB_SYNC_ALL, then
> the writeback_control will specify a range of pages that must be
> - written out. If it is WBC_SYNC_NONE, then a nr_to_write is
> + written out. If it is WB_SYNC_NONE, then a nr_to_write is
> given and that many pages should be written if possible. If no
> ->writepages is given, then mpage_writepages is used instead.
> This will choose pages from the address space that are tagged as
Applied, thanks.
jon
prev parent reply other threads:[~2020-07-27 22:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-26 19:22 [PATCH] docs: filesystems: vfs: correct sync_mode flag names Julia Lawall
2020-07-27 22:15 ` Jonathan Corbet [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=20200727161549.1d3e31a0@lwn.net \
--to=corbet@lwn.net \
--cc=Julia.Lawall@inria.fr \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@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).