linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Tobin C. Harding" <me@tobin.cc>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: "Tobin C. Harding" <tobin@kernel.org>,
	Jonathan Corbet <corbet@lwn.net>,
	linux-doc@vger.kernel.org, linux-fsdevel@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 00/13] Convert vfs.txt to vfs.rst
Date: Mon, 18 Mar 2019 14:34:30 +1100	[thread overview]
Message-ID: <20190318033430.GA27728@eros.localdomain> (raw)
In-Reply-To: <821449c9-e1f7-caa1-ff18-0cc1cc625596@infradead.org>

On Sun, Mar 17, 2019 at 06:46:40PM -0700, Randy Dunlap wrote:
> On 3/12/19 9:09 PM, Tobin C. Harding wrote:
> > Hi,
> > 
> > This set converts the VFS overview documentation to RST format.  I think
> > I'm slowly getting better at structuring these conversions to ease
> > review, if you disagree or you notice any way to further improve please
> > say so.
> 
> Hi Tobin,
> 
> What does this patch set apply to?  Maybe Jon's git tree?

I did this on top of Jon's tree before rc-1 came out (so during the
merge window last week).  I can rebase and fire off another version if
its easier for you Jon.

> I applied it to 5.1-rc1 with some forceful (minor) editing and ran
> 'make htmldocs' successfully, so
> 
> Tested-by: Randy Dunlap <rdunlap@infradead.org>

Thanks Randy.

> although there is at least one new field in struct file_operations: iopoll.

I purposely kept the conversion separate from the update.  Most of this
file explicitly states the kernel version each struct documented is for
(and at least two of them are 2.6.22).

One reason for the separation is that this set should be reviewable by
'docs' folk without having to be too closely looked at by anyone from
filesystems but the update will most likely benefit from at least a
cursory look over by someone from filesystems.

I have started the update to v5.20 but its slow going because I don't
know the VFS.  I'm learning as I go, I should have something together
soon.

thanks,
Tobin.

  reply	other threads:[~2019-03-18  3:35 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-13  4:09 [PATCH 00/13] Convert vfs.txt to vfs.rst Tobin C. Harding
2019-03-13  4:09 ` [PATCH 01/13] docs: filesystems: vfs: Remove space before tab Tobin C. Harding
2019-03-13  4:09 ` [PATCH 02/13] docs: filesystems: vfs: Use uniform space after period Tobin C. Harding
2019-03-13  4:09 ` [PATCH 03/13] docs: filesystems: vfs: Use 72 character column width Tobin C. Harding
2019-03-13  4:09 ` [PATCH 04/13] docs: filesystems: vfs: Use uniform spacing around headings Tobin C. Harding
2019-03-13  4:09 ` [PATCH 05/13] docs: filesystems: vfs: Use correct initial heading Tobin C. Harding
2019-03-13  4:09 ` [PATCH 06/13] docs: filesystems: vfs: Use SPDX identifier Tobin C. Harding
2019-03-13  4:09 ` [PATCH 07/13] docs: filesystems: vfs: Fix pre-amble indentation Tobin C. Harding
2019-03-13  4:09 ` [PATCH 08/13] docs: filesystems: vfs: Use list character for lists Tobin C. Harding
2019-03-13  4:09 ` [PATCH 09/13] docs: filesystems: vfs: Add code-block and txt->RST Tobin C. Harding
2019-03-13  4:09 ` [PATCH 10/13] docs: filesystems: vfs: Use ticks for listed items Tobin C. Harding
2019-03-13  4:09 ` [PATCH 11/13] docs: filesystems: vfs: Clean up lists Tobin C. Harding
2019-03-13  4:09 ` [PATCH 12/13] docs: filesystems: vfs: Do minor grammar fixes Tobin C. Harding
2019-03-13  4:09 ` [PATCH 13/13] docs: filesystems: vfs: Use backticks to guard star Tobin C. Harding
2019-03-18  1:46 ` [PATCH 00/13] Convert vfs.txt to vfs.rst Randy Dunlap
2019-03-18  3:34   ` Tobin C. Harding [this message]
2019-03-18 17:42     ` 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=20190318033430.GA27728@eros.localdomain \
    --to=me@tobin.cc \
    --cc=corbet@lwn.net \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rdunlap@infradead.org \
    --cc=tobin@kernel.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).