From: Jeff Layton <jlayton@kernel.org>
To: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>,
Linux Doc Mailing List <linux-doc@vger.kernel.org>
Cc: Jonathan Corbet <corbet@lwn.net>,
linux-fsdevel@vger.kernel.org, Sage Weil <sage@redhat.com>,
Ilya Dryomov <idryomov@gmail.com>,
ceph-devel@vger.kernel.org
Subject: Re: [PATCH 09/44] docs: filesystems: convert ceph.txt to ReST
Date: Tue, 18 Feb 2020 06:57:44 -0500 [thread overview]
Message-ID: <988af69f85385384738c8a656335e385a3ded827.camel@kernel.org> (raw)
In-Reply-To: <df2f142b5ca5842e030d8209482dfd62dcbe020f.1581955849.git.mchehab+huawei@kernel.org>
On Mon, 2020-02-17 at 17:11 +0100, Mauro Carvalho Chehab wrote:
> - Add a SPDX header;
> - Adjust document title;
> - Some whitespace fixes and new line breaks;
> - Mark literal blocks as such;
> - Add it to filesystems/index.rst.
>
> Signed-off-by: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
> ---
> .../filesystems/{ceph.txt => ceph.rst} | 26 +++++++++++--------
> Documentation/filesystems/index.rst | 1 +
> 2 files changed, 16 insertions(+), 11 deletions(-)
> rename Documentation/filesystems/{ceph.txt => ceph.rst} (91%)
>
Looks fine to me. Mauro, should I merge this via the ceph tree, or are
you merging them in via some other tree? In any case:
Acked-by: Jeff Layton <jlayton@kernel.org>
next prev parent reply other threads:[~2020-02-18 11:57 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-17 16:11 [PATCH 00/44] Manually convert filesystem FS documents to ReST Mauro Carvalho Chehab
2020-02-17 16:11 ` [PATCH 09/44] docs: filesystems: convert ceph.txt " Mauro Carvalho Chehab
2020-02-18 11:57 ` Jeff Layton [this message]
2020-02-18 4:01 ` [PATCH 00/44] Manually convert filesystem FS documents " Matthew Wilcox
2020-02-18 10:04 ` Mauro Carvalho Chehab
2020-02-19 9:32 ` Jonathan Corbet
2020-02-19 15:11 ` Mauro Carvalho Chehab
2020-03-02 21:13 ` 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=988af69f85385384738c8a656335e385a3ded827.camel@kernel.org \
--to=jlayton@kernel.org \
--cc=ceph-devel@vger.kernel.org \
--cc=corbet@lwn.net \
--cc=idryomov@gmail.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=mchehab+huawei@kernel.org \
--cc=sage@redhat.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