public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Sam Ravnborg <sam@ravnborg.org>
To: Randy Dunlap <randy.dunlap@oracle.com>
Cc: lkml <linux-kernel@vger.kernel.org>, akpm <akpm@linux-foundation.org>
Subject: Re: [PATCH] docbook: split kernel-api, add device-drivers book
Date: Sun, 15 Feb 2009 10:30:14 +0100	[thread overview]
Message-ID: <20090215093014.GD29094@uranus.ravnborg.org> (raw)
In-Reply-To: <20090211162644.f3feb758.randy.dunlap@oracle.com>

On Wed, Feb 11, 2009 at 04:26:44PM -0800, Randy Dunlap wrote:
> From: Randy Dunlap <randy.dunlap@oracle.com>
> 
> The kernel-api docbook was much larger than any of the others,
> so processing it took longer and needed some docbook extras in
> some cases, so split it into kernel-api (infrastructure etc.)
> and device drivers/device subsystems.  This allows these docbooks
> to be generated in parallel.  (This reduced the docbook processing
> time on my 4-proc system with make -j4 from about 5min:16sec to
> about 2min:01sec.)
> 
> The chapters that were moved from kernel-api to device-drivers are:
> 
> Driver Basics
> Device drivers infrastructure
> Parallel Port Devices
> Message-based devices
> Sound Devices
> 16x50 UART Driver
> Frame Buffer Library
> Input Subsystem
> Serial Peripheral Interface (SPI)
> I2C and SMBus Subsystem
> 
> Signed-off-by: Randy Dunlap <randy.dunlap@oracle.com>

I like the split, and I assume you will carry the patch in a Documentation tree?

Acked-by: Sam Ravnborg <sam@ravnborg.org>

	Sam

  reply	other threads:[~2009-02-15  9:28 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-12  0:26 [PATCH] docbook: split kernel-api, add device-drivers book Randy Dunlap
2009-02-15  9:30 ` Sam Ravnborg [this message]
2009-02-15 18:29   ` Randy Dunlap

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=20090215093014.GD29094@uranus.ravnborg.org \
    --to=sam@ravnborg.org \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=randy.dunlap@oracle.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