From: Wolfram Sang <wsa@the-dreams.de>
To: "gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>
Cc: Jonathan Corbet <corbet@lwn.net>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: Documentation: add Kernel Driver Statement to the kernel
Date: Sat, 14 Oct 2017 18:14:13 +0200 [thread overview]
Message-ID: <20171014161413.55k6xmil5qvjbtwk@katana> (raw)
In-Reply-To: <20171006091038.GA16038@kroah.com>
[-- Attachment #1: Type: text/plain, Size: 686 bytes --]
On Fri, Oct 06, 2017 at 11:10:38AM +0200, gregkh@linuxfoundation.org wrote:
> Way back in 2008 we didn't have "robust" in-kernel documentation system,
> so the idea of putting something like the kernel driver statement in the
> kernel tree wasn't even imagined. But now that has changed, so add the
> old document to the kernel source itself to allow for us to properly
> reference it in one canonical place (as the LF wiki keeps moving things
> around.)
Cool, I like it much to see it added to the kernel tree.
But could you explain what "robust" means in this context? And what
has changed which makes it "robust"? Sphinx?
I am interested in how such documents are handled best.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2017-10-14 16:14 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-06 9:10 [PATCH] Documentation: add Kernel Driver Statement to the kernel Greg Kroah-Hartman
2017-10-06 14:44 ` Mauro Carvalho Chehab
2017-10-06 15:03 ` Jonathan Corbet
2017-10-14 16:14 ` Wolfram Sang [this message]
2017-10-14 16:26 ` gregkh
2017-10-14 18:09 ` Wolfram Sang
2017-10-14 19:50 ` gregkh
2017-10-16 14:19 ` 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=20171014161413.55k6xmil5qvjbtwk@katana \
--to=wsa@the-dreams.de \
--cc=corbet@lwn.net \
--cc=gregkh@linuxfoundation.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mchehab@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 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.