From: Tejun Heo <tj@kernel.org>
To: Mauro Carvalho Chehab <mchehab+samsung@kernel.org>
Cc: Linux Doc Mailing List <linux-doc@vger.kernel.org>,
Mauro Carvalho Chehab <mchehab@infradead.org>,
linux-kernel@vger.kernel.org, Jonathan Corbet <corbet@lwn.net>,
Li Zefan <lizefan@huawei.com>,
Johannes Weiner <hannes@cmpxchg.org>
Subject: Re: [PATCH v2 02/11] docs: admin-guide: add cgroup-v2 documentation
Date: Thu, 10 May 2018 11:40:18 -0700 [thread overview]
Message-ID: <20180510184018.GS2368884@devbig577.frc2.facebook.com> (raw)
In-Reply-To: <1a62d2ec4d1eef268dd2256a1e2673df994bee5e.1525870886.git.mchehab+samsung@kernel.org>
On Wed, May 09, 2018 at 10:18:45AM -0300, Mauro Carvalho Chehab wrote:
> The cgroup-v2.txt is already in ReST format. So, move it to the
> admin-guide, where it belongs.
>
> Cc: Tejun Heo <tj@kernel.org>
> Cc: Li Zefan <lizefan@huawei.com>
> Cc: Johannes Weiner <hannes@cmpxchg.org>
> Signed-off-by: Mauro Carvalho Chehab <mchehab+samsung@kernel.org>
Acked-by: Tejun Heo <tj@kernel.org>
Thanks.
--
tejun
--
To unsubscribe from this list: send the line "unsubscribe linux-doc" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2018-05-10 18:40 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-09 13:18 [PATCH v2 00/11] Fix some doc build warnings/errors and broken links Mauro Carvalho Chehab
2018-05-09 13:18 ` [PATCH v2 01/11] docs: can.rst: fix a footnote reference Mauro Carvalho Chehab
2018-05-09 13:18 ` [PATCH v2 02/11] docs: admin-guide: add cgroup-v2 documentation Mauro Carvalho Chehab
2018-05-10 18:40 ` Tejun Heo [this message]
2018-05-10 20:02 ` Jonathan Corbet
2018-05-09 13:18 ` [PATCH v2 03/11] docs: crypto_engine.rst: Fix two parse warnings Mauro Carvalho Chehab
2018-05-09 13:18 ` [PATCH v2 04/11] docs: dell_rbu.txt: fix location of request_firmware Mauro Carvalho Chehab
2018-05-09 15:06 ` Mauro Carvalho Chehab
2018-05-09 13:18 ` [PATCH v2 05/11] docs: uio-howto.rst: use a code block to solve a warning Mauro Carvalho Chehab
2018-05-09 13:18 ` [PATCH v2 06/11] scripts/documentation-file-ref-check: rewrite it in perl with auto-fix mode Mauro Carvalho Chehab
2018-05-09 13:18 ` [PATCH v2 07/11] docs: ranoops.rst: fix location of ramoops.txt Mauro Carvalho Chehab
2018-05-09 13:18 ` [PATCH v2 08/11] docs: refcount-vs-atomic.rst: prefix url with https Mauro Carvalho Chehab
2018-05-09 13:43 ` Andrea Parri
2018-05-09 14:40 ` Mauro Carvalho Chehab
2018-05-09 13:18 ` [PATCH v2 10/11] arch/*: Kconfig: fix documentation for NMI watchdog Mauro Carvalho Chehab
2018-05-09 13:18 ` [PATCH v2 11/11] docs: fix broken references with multiple hints Mauro Carvalho Chehab
2018-05-09 19:22 ` James Morris
2018-05-15 10:28 ` Bartlomiej Zolnierkiewicz
2018-05-15 14:52 ` Steven Rostedt
2018-05-22 17:31 ` Rob Herring
2018-05-10 20:22 ` [PATCH v2 00/11] Fix some doc build warnings/errors and broken links Jonathan Corbet
2018-05-10 21:28 ` Mauro Carvalho Chehab
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=20180510184018.GS2368884@devbig577.frc2.facebook.com \
--to=tj@kernel.org \
--cc=corbet@lwn.net \
--cc=hannes@cmpxchg.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lizefan@huawei.com \
--cc=mchehab+samsung@kernel.org \
--cc=mchehab@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).