mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Markus Heiser <markus.heiser@darmarit.de>
Cc: "Hans J . Koch" <hjk@hansjkoch.de>,
	Stephen Hemminger <stephen@networkplumber.org>,
	Jonathan Corbet <corbet@lwn.net>,
	kvm@vger.kernel.org, devel@linuxdriverproject.org,
	"linux-kernel @ vger . kernel . org Mailing List" 
	<linux-kernel@vger.kernel.org>,
	"linux-doc @ vger . kernel . org Mailing List" 
	<linux-doc@vger.kernel.org>
Subject: Re: [PATCH] doc-rst: DocBook to reST migration of the uio-howto.tmpl
Date: Tue, 18 Oct 2016 17:59:17 +0200	[thread overview]
Message-ID: <20161018155917.GB13567@kroah.com> (raw)
In-Reply-To: <1476805978-23336-2-git-send-email-markus.heiser@darmarit.de>

On Tue, Oct 18, 2016 at 05:52:58PM +0200, Markus Heiser wrote:
> The migration is done with the dbxml2rst project with small additional
> handmade. The uio-howto is chunked along its chapters into smal parts.

"small"?  :)

And why small parts?  Is that the new "desired" way?

> 
> [1] https://return42.github.io/dbxml2rst/
> 
> Signed-off-by: Markus Heiser <markus.heiser@darmarit.de>
> ---
>  Documentation/DocBook/Makefile                   |    2 +-
>  Documentation/DocBook/uio-howto.tmpl             | 1050 ----------------------
>  Documentation/conf.py                            |    2 +
>  Documentation/index.rst                          |    1 +
>  Documentation/uio-howto/about_uio.rst            |  150 ++++
>  Documentation/uio-howto/aboutthisdoc.rst         |  103 +++
>  Documentation/uio-howto/conf.py                  |   10 +
>  Documentation/uio-howto/custom_kernel_module.rst |  245 +++++
>  Documentation/uio-howto/index.rst                |   45 +
>  Documentation/uio-howto/uio_pci_generic.rst      |  168 ++++
>  Documentation/uio-howto/userspace_driver.rst     |   86 ++

As this isn't just a howto, can we have it in Documentation/uio/
instead?  Or, if we are going to mirror the source tree, would
Documentation/drivers/uio/ make more sense?  I'll defer to the
Documentation maintainer about this as I'm sure they have an idea of
what they want to do.

thanks,

greg k-h

  reply	other threads:[~2016-10-18 15:59 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-18 15:52 Markus Heiser
2016-10-18 15:52 ` Markus Heiser
2016-10-18 15:59   ` Greg KH [this message]
2016-10-18 16:37     ` Markus Heiser
2016-10-18 15:58 ` 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=20161018155917.GB13567@kroah.com \
    --to=greg@kroah.com \
    --cc=corbet@lwn.net \
    --cc=devel@linuxdriverproject.org \
    --cc=hjk@hansjkoch.de \
    --cc=kvm@vger.kernel.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=markus.heiser@darmarit.de \
    --cc=stephen@networkplumber.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

Powered by JetHome