From: Matthew Wilcox <willy@infradead.org>
To: Sheriff Esseson <sheriffesseson@gmail.com>
Cc: skhan@linuxfoundation.org, corbet@lwn.net,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-xfs@vger.kernel.org,
linux-kernel-mentees@lists.linuxfoundation.org
Subject: Re: [PATCH v1] Doc : fs : convert xfs.txt to ReST
Date: Fri, 28 Jun 2019 18:41:36 -0700 [thread overview]
Message-ID: <20190629014136.GF4286@bombadil.infradead.org> (raw)
In-Reply-To: <20190629010733.GA31770@localhost>
On Sat, Jun 29, 2019 at 02:25:08AM +0100, Sheriff Esseson wrote:
> On Fri, Jun 28, 2019 at 10:43:24PM +0100, Sheriff Esseson wrote:
> > Convert xfs.txt to ReST, markup and rename accordingly. Update
> > Documentation/index.rst.
Don't quote the entire previous patch when submitting a new one.
> Rid Documentation/filesystems/index.rst of ".rst" in toc-tree references.
>
> CC xfs-list.
>
> Correct email indentation.
This text should be below the --- line, and it should be marked as "v2:"
And you didn't update the MAINTAINERS file.
> +For boolean mount options, the names with the "(*)" prefix is the
> +default behaviour. For example, take an behaviour enabled by default to be a one (1) or,
This line is too long. Doesn't checkpatch.pl complain?
> + rtdev=<device>
> + An XFS filesystem has up to three parts: a data section, a log
> + section, and a real-time section. The real-time section is optional.
> + If enabled, ``rtdev`` sets ``device`` to be used as an
> + external real-time section, similar to ``logdev`` above.
Darrick mentioned the indentation was weird here, and you haven't fixed that.
> + sunit=<value>
> + Used to specify the stripe unit for a RAID device
> + or (in conjunction with ``swidth`` below) a stripe volume. ``value`` must be specified in 512-byte
> + block units. This option is only relevant to filesystems
line length
next prev parent reply other threads:[~2019-06-29 1:41 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-28 21:43 Sheriff Esseson
2019-06-28 21:51 ` Matthew Wilcox
2019-06-28 22:18 ` Darrick J. Wong
2019-06-28 21:53 ` Shuah Khan
2019-06-29 1:25 ` Sheriff Esseson
2019-06-29 1:41 ` Matthew Wilcox [this message]
2019-06-29 14:54 ` Sheriff Esseson
2019-06-29 15:01 ` Sheriff Esseson
2019-06-29 15:14 ` Jonathan Corbet
2019-06-29 16:02 ` [linux-kernel-mentees] " Sheriff Esseson
2019-06-29 20:57 ` Sheriff Esseson
2019-06-29 20:59 ` Sheriff Esseson
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=20190629014136.GF4286@bombadil.infradead.org \
--to=willy@infradead.org \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel-mentees@lists.linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=sheriffesseson@gmail.com \
--cc=skhan@linuxfoundation.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
all inboxes | Powered by JetHome®