From: Mauro Carvalho Chehab <mchehab+samsung@kernel.org>
To: Jonathan Corbet <corbet@lwn.net>
Cc: Linux Doc Mailing List <linux-doc@vger.kernel.org>,
Mauro Carvalho Chehab <mchehab@infradead.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 5/6] docs: fs: convert porting to ReST
Date: Wed, 31 Jul 2019 17:22:19 -0300 [thread overview]
Message-ID: <20190731172219.2f07d420@coco.lan> (raw)
In-Reply-To: <20190731141707.6f3d21d7@lwn.net>
Em Wed, 31 Jul 2019 14:17:07 -0600
Jonathan Corbet <corbet@lwn.net> escreveu:
> On Wed, 31 Jul 2019 17:08:52 -0300
> Mauro Carvalho Chehab <mchehab+samsung@kernel.org> wrote:
>
> > This file has its own proper style, except that, after a while,
> > the coding style gets violated and whitespaces are placed on
> > different ways.
> >
> > As Sphinx and ReST are very sentitive to whitespace differences,
> > I had to opt if each entry after required/mandatory/... fields
> > should start with zero spaces or with a tab. I opted to start them
> > all from the zero position, in order to avoid needing to break lines
> > with more than 80 columns, with would make harder for review.
> >
> > Most of the other changes at porting.rst were made to use an unified
> > notation with works nice as a text file while also produce a good html
> > output after being parsed.
> >
> > Signed-off-by: Mauro Carvalho Chehab <mchehab+samsung@kernel.org>
> > ---
> > Documentation/filesystems/porting.rst | 2 +-
> > 1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > diff --git a/Documentation/filesystems/porting.rst b/Documentation/filesystems/porting.rst
> > index 66aa521e6376..f18506083ced 100644
> > --- a/Documentation/filesystems/porting.rst
> > +++ b/Documentation/filesystems/porting.rst
> > @@ -158,7 +158,7 @@ Callers of notify_change() need ->i_mutex now.
> > New super_block field ``struct export_operations *s_export_op`` for
> > explicit support for exporting, e.g. via NFS. The structure is fully
> > documented at its declaration in include/linux/fs.h, and in
> > -Documentation/filesystems/nfs/Exporting.
> > +Documentation/filesystems/nfs/exporting.rst.
> >
> > Briefly it allows for the definition of decode_fh and encode_fh operations
> > to encode and decode filehandles, and allows the filesystem to use
>
> This patch doesn't match the changelog at all. I think it's one leftover
> fix after the previous version of the patch was applied...?
Gah, sorry. Yeah, you're right: this is just a fixup patch.
>
> jon
Thanks,
Mauro
next prev parent reply other threads:[~2019-07-31 20:22 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-31 20:08 [PATCH 0/6] ReST conversion patches not applied yet Mauro Carvalho Chehab
2019-07-31 20:08 ` [PATCH 1/6] docs: fix a couple of new broken references Mauro Carvalho Chehab
2019-07-31 20:21 ` Rob Herring
2019-07-31 20:36 ` Dave Kleikamp
2019-07-31 20:08 ` [PATCH 2/6] docs: writing-schema.md: convert from markdown to ReST Mauro Carvalho Chehab
2019-07-31 20:45 ` Rob Herring
2019-07-31 20:48 ` Jonathan Corbet
2019-07-31 21:30 ` Rob Herring
2019-07-31 20:08 ` [PATCH 3/6] spi: docs: convert to ReST and add it to the kABI bookset Mauro Carvalho Chehab
2019-07-31 20:08 ` [PATCH 4/6] docs: fs: cifs: convert to ReST and add to admin-guide book Mauro Carvalho Chehab
2019-07-31 20:08 ` [PATCH 5/6] docs: fs: convert porting to ReST Mauro Carvalho Chehab
2019-07-31 20:17 ` Jonathan Corbet
2019-07-31 20:22 ` Mauro Carvalho Chehab [this message]
2019-07-31 20:08 ` [PATCH 6/6] docs: w1: convert to ReST and add to the kAPI group of docs Mauro Carvalho Chehab
2019-07-31 20:17 ` [PATCH 0/6] ReST conversion patches not applied yet Jonathan Corbet
2019-07-31 20:20 ` Mark Brown
2019-07-31 20:26 ` Mauro Carvalho Chehab
2019-07-31 20:37 ` Mark Brown
2019-07-31 21:27 ` Mauro Carvalho Chehab
2019-07-31 21:55 ` Mark Brown
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=20190731172219.2f07d420@coco.lan \
--to=mchehab+samsung@kernel.org \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.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).