From: Pavel Machek <pavel@ucw.cz>
To: Mauro Carvalho Chehab <mchehab+samsung@kernel.org>
Cc: Jonathan Corbet <corbet@lwn.net>,
"Rafael J. Wysocki" <rjw@rjwysocki.net>,
Len Brown <len.brown@intel.com>,
linux-doc@vger.kernel.org, linux-pm@vger.kernel.org
Subject: Re: [PATCH 02/14] docs: power: add it to to the main documentation index
Date: Tue, 16 Jul 2019 20:42:34 +0200 [thread overview]
Message-ID: <20190716184234.GA9135@amd> (raw)
In-Reply-To: <95abe2e389f5bfb9dd03d55de384c2b9b5bb78da.1563277838.git.mchehab+samsung@kernel.org>
[-- Attachment #1: Type: text/plain, Size: 801 bytes --]
On Tue 2019-07-16 09:10:41, Mauro Carvalho Chehab wrote:
> The power docs are orphaned at the documentation body.
>
> While it could likely be moved to be inside some guide, I'm opting to just
> adding it to the main index.rst, removing the :orphan: and adding the SPDX
> header.
>
> The reason is similar to what it was done for other driver-specific
> subsystems: the docs there contain a mix of Kernelspace, uAPI and
> admin-guide. So, better to keep them on its own directory,
> while the docs there are not properly classified.
>
> Signed-off-by: Mauro Carvalho Chehab <mchehab+samsung@kernel.org>
Acked-by: Pavel Machek <pavel@ucw.cz>
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]
next prev parent reply other threads:[~2019-07-16 18:42 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-16 12:10 [PATCH 00/14] pending doc patches for 5.3-rc Mauro Carvalho Chehab
2019-07-16 12:10 ` Mauro Carvalho Chehab
2019-07-16 12:10 ` Mauro Carvalho Chehab
2019-07-16 12:10 ` Mauro Carvalho Chehab
2019-07-16 12:10 ` Mauro Carvalho Chehab
2019-07-16 12:10 ` [PATCH 01/14] docs: powerpc: convert docs to ReST and rename to *.rst Mauro Carvalho Chehab
2019-07-16 12:10 ` Mauro Carvalho Chehab
2019-07-16 12:10 ` Mauro Carvalho Chehab
2019-07-16 12:10 ` Mauro Carvalho Chehab
2019-07-16 12:10 ` [PATCH 02/14] docs: power: add it to to the main documentation index Mauro Carvalho Chehab
2019-07-16 18:42 ` Pavel Machek [this message]
2019-07-16 12:10 ` [PATCH 03/14] docs: fix broken doc references due to renames Mauro Carvalho Chehab
2019-07-16 12:10 ` Mauro Carvalho Chehab
2019-07-16 12:10 ` Mauro Carvalho Chehab
2019-07-16 16:18 ` Jerry Hoemann
2019-07-22 11:38 ` Wolfram Sang
2019-07-22 11:38 ` Wolfram Sang
2019-07-16 12:10 ` [PATCH 04/14] docs: pdf: add all Documentation/*/index.rst to PDF output Mauro Carvalho Chehab
2019-07-16 12:10 ` [PATCH 05/14] docs: conf.py: add CJK package needed by translations Mauro Carvalho Chehab
2019-07-16 12:10 ` [PATCH 06/14] docs: conf.py: only use CJK if the font is available Mauro Carvalho Chehab
2019-07-16 12:10 ` [PATCH 12/14] docs: load_config.py: avoid needing a conf.py just due to LaTeX docs Mauro Carvalho Chehab
2019-07-16 12:10 ` [PATCH 13/14] docs: remove extra conf.py files Mauro Carvalho Chehab
2019-07-16 12:10 ` Mauro Carvalho Chehab
2019-07-16 12:10 ` Mauro Carvalho Chehab
2019-07-16 12:10 ` [PATCH 14/14] docs: virtual: add it to the documentation body Mauro Carvalho Chehab
2019-07-16 12:15 ` Paolo Bonzini
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=20190716184234.GA9135@amd \
--to=pavel@ucw.cz \
--cc=corbet@lwn.net \
--cc=len.brown@intel.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=mchehab+samsung@kernel.org \
--cc=rjw@rjwysocki.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.