From: Martin Kepplinger <martink@posteo.de>
To: "Jonathan Neuschäfer" <j.neuschaefer@gmx.net>
Cc: linux-doc@vger.kernel.org, Jonathan Corbet <corbet@lwn.net>,
Federico Vaga <federico.vaga@vaga.pv.it>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Documentation: kernel-docs: Move vfs.txt under "Docs at the Linux Kernel tree"
Date: Mon, 01 Apr 2019 07:19:02 +0200 [thread overview]
Message-ID: <423faa6a06fee4e1106f8b0c83bcd78d@posteo.de> (raw)
In-Reply-To: <20190331221439.22892-1-j.neuschaefer@gmx.net>
Am 01.04.2019 00:14 schrieb Jonathan Neuschäfer:
> It's unnecessary to point to an external mirror of the Documentation
> directory. Also, drop the date field, because in-kernel documentation
> is
> continually updated.
>
> Signed-off-by: Jonathan Neuschäfer <j.neuschaefer@gmx.net>
> ---
>
> Alternatively, we might drop this entry of the list entirely, because
> Documentation/ is already covered.
> ---
> Documentation/process/kernel-docs.rst | 23 +++++++++++------------
> 1 file changed, 11 insertions(+), 12 deletions(-)
>
> diff --git a/Documentation/process/kernel-docs.rst
> b/Documentation/process/kernel-docs.rst
> index ab12dddc773e..92488e59943d 100644
> --- a/Documentation/process/kernel-docs.rst
> +++ b/Documentation/process/kernel-docs.rst
> @@ -52,6 +52,17 @@ The Sphinx books should be built with ``make
> {htmldocs | pdfdocs | epubdocs}``.
> (including this document itself) have been moved there, and
> might
> be more up to date than the web version.
>
> + * Title: **Overview of the Virtual File System**
> +
> + :Author: Richard Gooch.
> + :Location: Documentation/filesystems/vfs.txt
> + :Keywords: VFS, File System, mounting filesystems, opening
> files,
> + dentries, dcache.
> + :Description: Brief introduction to the Linux Virtual File
> System.
> + What is it, how it works, operations taken when opening a file
> or
> + mounting a file system and description of important data
> + structures explaining the purpose of each of their entries.
> +
> On-line docs
> ------------
>
> @@ -95,18 +106,6 @@ On-line docs
> [...]. This paper examines some common problems for
> submitting larger changes and some strategies to avoid
> problems.
>
> - * Title: **Overview of the Virtual File System**
> -
> - :Author: Richard Gooch.
> - :URL:
> http://www.mjmwired.net/kernel/Documentation/filesystems/vfs.txt
> - :Date: 2007
> - :Keywords: VFS, File System, mounting filesystems, opening
> files,
> - dentries, dcache.
> - :Description: Brief introduction to the Linux Virtual File
> System.
> - What is it, how it works, operations taken when opening a file
> or
> - mounting a file system and description of important data
> - structures explaining the purpose of each of their entries.
> -
> * Title: **Linux Device Drivers, Third Edition**
>
> :Author: Jonathan Corbet, Alessandro Rubini, Greg Kroah-Hartman
> --
> 2.20.1
Reviewed-by: Martin Kepplinger <martink@posteo.de>
thanks
next prev parent reply other threads:[~2019-04-01 5:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-31 22:14 [PATCH] Documentation: kernel-docs: Move vfs.txt under "Docs at the Linux Kernel tree" Jonathan Neuschäfer
2019-04-01 5:19 ` Martin Kepplinger [this message]
2019-04-02 15:43 ` Jonathan Corbet
2019-04-02 19:13 ` Jonathan Neuschäfer
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=423faa6a06fee4e1106f8b0c83bcd78d@posteo.de \
--to=martink@posteo.de \
--cc=corbet@lwn.net \
--cc=federico.vaga@vaga.pv.it \
--cc=j.neuschaefer@gmx.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.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).