From: Christoph Hellwig <hch-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org>
To: Eric Sandeen <sandeen-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
Cc: linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-mm-Bw31MaZKKs3YtjvyW6yDsg@public.gmane.org,
Jonathan Corbet <corbet-T1hC0tSOHrs@public.gmane.org>,
cgroups-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-f2fs-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org,
linux-xfs <linux-xfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: [PATCH] doc: cgroup: add f2fs and xfs to supported list for writeback
Date: Tue, 30 Jun 2020 06:42:17 +0100 [thread overview]
Message-ID: <20200630054217.GA27221@infradead.org> (raw)
In-Reply-To: <c8271324-9132-388c-5242-d7699f011892-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
On Mon, Jun 29, 2020 at 02:08:09PM -0500, Eric Sandeen wrote:
> f2fs and xfs have both added support for cgroup writeback:
>
> 578c647 f2fs: implement cgroup writeback support
> adfb5fb xfs: implement cgroup aware writeback
>
> so add them to the supported list in the docs.
>
> Signed-off-by: Eric Sandeen <sandeen-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
> ---
>
> TBH I wonder about the wisdom of having this detail in
> the doc, as it apparently gets missed quite often ...
I'd rather remove the list of file systems. It has no chance of
staying uptodate.
next prev parent reply other threads:[~2020-06-30 5:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-29 19:08 [PATCH] doc: cgroup: add f2fs and xfs to supported list for writeback Eric Sandeen
[not found] ` <c8271324-9132-388c-5242-d7699f011892-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2020-06-30 1:18 ` Chao Yu
2020-06-30 5:42 ` Christoph Hellwig [this message]
[not found] ` <20200630054217.GA27221-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org>
2020-06-30 13:59 ` Eric Sandeen
2020-07-01 8:32 ` Christoph Hellwig
[not found] ` <20200701083224.GI20101-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org>
2020-07-01 13:25 ` Eric Sandeen
2020-07-05 20:35 ` Jonathan Corbet
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=20200630054217.GA27221@infradead.org \
--to=hch-wegcikhe2lqwvfeawa7xhq@public.gmane.org \
--cc=cgroups-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=corbet-T1hC0tSOHrs@public.gmane.org \
--cc=linux-f2fs-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-mm-Bw31MaZKKs3YtjvyW6yDsg@public.gmane.org \
--cc=linux-xfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=sandeen-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.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