From: Markus Heiser <markus.heiser@darmarit.de>
To: David Howells <dhowells@redhat.com>
Cc: Mauro Carvalho Chehab <mchehab+samsung@kernel.org>,
Linux Doc Mailing List <linux-doc@vger.kernel.org>,
Mauro Carvalho Chehab <mchehab@infradead.org>,
linux-kernel@vger.kernel.org, Jonathan Corbet <corbet@lwn.net>,
Andrea Parri <andrea.parri@amarulasolutions.com>,
Nicholas Piggin <npiggin@gmail.com>,
linux-arch@vger.kernel.org, Peter Zijlstra <peterz@infradead.org>,
Boqun Feng <boqun.feng@gmail.com>,
Luc Maranget <luc.maranget@inria.fr>,
Alan Stern <stern@rowland.harvard.edu>,
Akira Yokosawa <akiyks@gmail.com>,
Will Deacon <will.deacon@arm.com>,
"Paul E. McKenney" <paulmck@linux.ibm.com>,
Daniel Lustig <dlustig@nvidia.com>,
Jade Alglave <j.alglave@ucl.ac.uk>
Subject: Re: [PATCH 0/8] Prepare files under Documentation/*.txt to build with Sphinx
Date: Fri, 12 Apr 2019 14:34:25 +0200 [thread overview]
Message-ID: <df609cad-fa5b-ac15-314f-ac8759771d90@darmarit.de> (raw)
In-Reply-To: <27303.1555071586@warthog.procyon.org.uk>
Am 12.04.19 um 14:19 schrieb David Howells:
> Markus Heiser <markus.heiser@darmarit.de> wrote:
>
>> Which is already named in our 'How to write kernel documentation' introduction
>>
>> - https://www.kernel.org/doc/html/latest/doc-guide/sphinx.html#writing-documentation
>
> This should really be in Documentation/ directory.
>
I agree with you, it is a kind of information hiding. If you know proper
places, please send a patch to Jon.
-- Markus --
next prev parent reply other threads:[~2019-04-12 12:34 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-10 9:56 [PATCH 0/8] Prepare files under Documentation/*.txt to build with Sphinx Mauro Carvalho Chehab
2019-04-10 9:56 ` Mauro Carvalho Chehab
2019-04-10 9:56 ` [PATCH 2/8] docs: atomic_bitops.txt: add a title for this document Mauro Carvalho Chehab
2019-04-10 9:56 ` Mauro Carvalho Chehab
2019-04-11 18:37 ` [PATCH 0/8] Prepare files under Documentation/*.txt to build with Sphinx Jonathan Corbet
2019-04-11 18:37 ` Jonathan Corbet
2019-04-12 10:21 ` David Howells
2019-04-12 10:21 ` David Howells
2019-04-12 10:31 ` Markus Heiser
2019-04-12 10:31 ` Markus Heiser
2019-04-12 12:19 ` David Howells
2019-04-12 12:19 ` David Howells
2019-04-12 12:34 ` Markus Heiser [this message]
2019-04-12 12:34 ` Markus Heiser
2019-04-12 15:39 ` Jonathan Corbet
2019-04-12 15:39 ` Jonathan Corbet
2019-04-12 16:45 ` Markus Heiser
2019-04-12 16:45 ` Markus Heiser
2019-04-12 14:13 ` Jani Nikula
2019-04-12 14:13 ` Jani Nikula
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=df609cad-fa5b-ac15-314f-ac8759771d90@darmarit.de \
--to=markus.heiser@darmarit.de \
--cc=akiyks@gmail.com \
--cc=andrea.parri@amarulasolutions.com \
--cc=boqun.feng@gmail.com \
--cc=corbet@lwn.net \
--cc=dhowells@redhat.com \
--cc=dlustig@nvidia.com \
--cc=j.alglave@ucl.ac.uk \
--cc=linux-arch@vger.kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luc.maranget@inria.fr \
--cc=mchehab+samsung@kernel.org \
--cc=mchehab@infradead.org \
--cc=npiggin@gmail.com \
--cc=paulmck@linux.ibm.com \
--cc=peterz@infradead.org \
--cc=stern@rowland.harvard.edu \
--cc=will.deacon@arm.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