ksummit.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: Daniel Vetter <daniel.vetter@ffwll.ch>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: "ksummit-discuss@lists.linuxfoundation.org"
	<ksummit-discuss@lists.linuxfoundation.org>,
	Dan Carpenter <dan.carpenter@oracle.com>
Subject: Re: [Ksummit-discuss] [CORE TOPIC] Documentation
Date: Tue, 4 Aug 2015 16:29:25 +0200	[thread overview]
Message-ID: <CAKMK7uEb8=FoudmUiX+yLievB2qP2aaiUMuA_4m+N--qWspyMA@mail.gmail.com> (raw)
In-Reply-To: <CAMuHMdUK2_7+Y9+ffpJKTy8LcwogFcg+XAGrif0YcTT4C4u-wQ@mail.gmail.com>

On Tue, Aug 4, 2015 at 4:05 PM, Geert Uytterhoeven <geert@linux-m68k.org> wrote:
> On Tue, Aug 4, 2015 at 3:50 PM, Dan Carpenter <dan.carpenter@oracle.com> wrote:
>> I have all the tools to read it.  I remember this because it requires
>> 700MB of dependencies.  I was downloading it to read the kdbus
>> documentation.  I remember this.  I don't think I read the kdbus
>> documentation in the end.  I certainly don't know, without googling, how
>> to use build the docbook output.
>
> I gave up trying to build the docbook docs many years ago.
>
> Cross-compiling kernels for niche architectures is peanuts compared to
> generating docbook output ;-(

Don't build the pdf, it's useless. Build the html pages with all the
links and stuff, and that just about requires an xlstproc plus the
docbook stylesheets. Building the html pages is as simple as

$ make htmldocs

and make help will tell you that too.
-Daniel
-- 
Daniel Vetter
Software Engineer, Intel Corporation
+41 (0) 79 365 57 48 - http://blog.ffwll.ch

  reply	other threads:[~2015-08-04 14:29 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-01 14:41 Jonathan Corbet
2015-08-02  7:07 ` Davidlohr Bueso
2015-08-03 13:35   ` Rafael J. Wysocki
2015-08-03 13:27     ` Konstantin Ryabitsev
2015-08-03 14:33     ` Jonathan Corbet
2015-08-03 20:45       ` Dmitry Torokhov
2015-08-04 10:59         ` Daniel Vetter
2015-08-04  0:52       ` Rafael J. Wysocki
2015-08-04 12:50       ` Laurent Pinchart
2015-08-04 13:03         ` Daniel Vetter
2015-08-04 14:28           ` Laurent Pinchart
2015-08-04 14:30             ` Daniel Vetter
2015-08-04 13:50         ` Dan Carpenter
2015-08-04 14:05           ` Geert Uytterhoeven
2015-08-04 14:29             ` Daniel Vetter [this message]
2015-08-04 14:30             ` Laurent Pinchart
2015-08-04 17:10               ` Geert Uytterhoeven
2015-08-04 14:42           ` Konstantin Ryabitsev
2015-08-04 18:21             ` Tim Bird
2015-08-04 21:00               ` Laurent Pinchart
2015-08-04 15:35         ` Mark Brown
2015-08-05 17:07           ` Michael Kerrisk (man-pages)
2015-08-04 17:24         ` Jonathan Corbet
2015-08-04  7:12 ` Michael Ellerman
2015-08-04  7:42   ` Marcel Holtmann
2015-08-04  8:33     ` Peter Huewe
2015-08-05 17:08       ` Michael Kerrisk (man-pages)
2015-08-05 17:19         ` josh
2015-08-05 17:21         ` Konstantin Ryabitsev
2015-08-04 12:54   ` Laurent Pinchart
2015-08-04 13:07     ` Daniel Vetter
2015-08-04 11:09 ` Daniel Vetter

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='CAKMK7uEb8=FoudmUiX+yLievB2qP2aaiUMuA_4m+N--qWspyMA@mail.gmail.com' \
    --to=daniel.vetter@ffwll.ch \
    --cc=dan.carpenter@oracle.com \
    --cc=geert@linux-m68k.org \
    --cc=ksummit-discuss@lists.linuxfoundation.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