linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH RFC] drm: add of_graph endpoint helper to find possible CRTCs
Date: Wed, 9 Jul 2014 19:32:40 +0100	[thread overview]
Message-ID: <20140709183240.GV21766@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <CAF6AEGt0yq-Feuq13ewY7_4YkgOW6FKjLHnNDELXiyzOWdO5=w@mail.gmail.com>

On Wed, Jul 09, 2014 at 02:11:18PM -0400, Rob Clark wrote:
> On Wed, Jul 9, 2014 at 11:16 AM, Russell King - ARM Linux
> <linux@arm.linux.org.uk> wrote:
> > Warning(.../include/drm/drm_flip_work.h:68): No description found for parameter ')'
> > Warning(.../include/drm/drm_flip_work.h:68): Excess struct/union/enum/typedef member 'fifo' description in 'drm_flip_work'
> > Warning(.../include/drm/drm_flip_work.h:68): No description found for parameter ')'
> > Warning(.../include/drm/drm_flip_work.h:68): Excess struct/union/enum/typedef member 'fifo' description in 'drm_flip_work'
> >   DOCPROC Documentation/DocBook/w1.xml
> >   DOCPROC Documentation/DocBook/writing_musb_glue_layer.xml
> >   PDF     Documentation/DocBook/z8530book.pdf
> > Making portrait pages on A4 paper (210mmx297mm)
> > sh: /usr/share/xmlto/format/docbook/../fo/pdf: No such file or directory
> > make[2]: *** [Documentation/DocBook/z8530book.pdf] Error 1
> > make[2]: *** Waiting for unfinished jobs....
> > make[1]: *** [pdfdocs] Error 2
> > make: *** [sub-make] Error 2
> 
> hmm, I usually use 'make htmldocs'.. hadn't really bothered to try to
> build pdf docs.   It was a while ago, but I think 'xmlto-tex' would be
> what you need for fedora to get docs to build.  Hopefully the package
> has a similar name on other distros.
> 
> There are unfortunately a lot of warnings..  the headerdoc stuff is
> not always as clever as you would like.

Thanks, that helps it get a bit further, but it spits out a whole truck
load of errors before it gets anywhere near DRM stuff.  Either this
stuff isn't maintained, or it's for a newer flavour of TEX.  From what
I read on the web, this kind of problem is fairly typical where TEX
stuff goes (no two tex versions are compatible.)

I think I'll leave the kerneldoc stuff to someone who knows (a) how to
deal with it.

-- 
FTTC broadband for 0.8mile line: currently at 9.5Mbps down 400kbps up
according to speedtest.net.

      reply	other threads:[~2014-07-09 18:32 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-03 16:49 [PATCH RFC] drm: add of_graph endpoint helper to find possible CRTCs Russell King
2014-07-03 22:17 ` Rob Clark
2014-07-03 22:41   ` Russell King - ARM Linux
2014-07-05 12:21     ` Rob Clark
2014-07-03 22:36 ` Rob Clark
2014-07-09 15:16   ` Russell King - ARM Linux
2014-07-09 18:11     ` Rob Clark
2014-07-09 18:32       ` Russell King - ARM Linux [this message]

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=20140709183240.GV21766@n2100.arm.linux.org.uk \
    --to=linux@arm.linux.org.uk \
    --cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).