mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Ben Hutchings <ben@decadent.org.uk>
To: Masanari Iida <standby24x7@gmail.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Jonathan Corbet <corbet@lwn.net>,
	lunar@debian.org
Subject: Re: make htmldocs on linux-next failed with warnings.
Date: Thu, 16 Jul 2015 15:28:56 +0100	[thread overview]
Message-ID: <1437056936.3469.37.camel@decadent.org.uk> (raw)
In-Reply-To: <CALLJCT2fQvoR0L1MNFUPu9F9rPZM5kQE7gSZrrZdHChhbgpV8g@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1868 bytes --]

On Thu, 2015-07-16 at 23:22 +0900, Masanari Iida wrote:
> make htmldocs on linux-next have some parser warnings.
> Following commit cause the warning.

Yes it has warnings but they should be non-fatal.

Ben.

> commit b44158b17099ed5c7c8f4bfb7029942adbfbc318
> Author: Ben Hutchings <ben@decadent.org.uk>
> Date:   Wed Jul 8 20:07:05 2015 +0100
> 
>     DocBook: Avoid building man pages repeatedly and inconsistently
> 
> Warning message detail.
> /home/iida/Repo/linux-next/Documentation/DocBook/device-drivers.xml:
> 36171: parser warning : xmlParsePITarget: invalid name prefix 'xml'
>  <?xmlif if excludeextra='1'?>
>        ^
> /home/iida/Repo/linux-next/Documentation/DocBook/device-drivers.xml:
> 36172: parser warning : xmlParsePITarget: invalid name prefix 'xml'
> <?xmlif else?>
>        ^
> /home/iida/Repo/linux-next/Documentation/DocBook/device-drivers.xml:
> 36457: parser warning : xmlParsePITarget: invalid name prefix 'xml'
> <?xmlif fi?>
>        ^
> /home/iida/Repo/linux-next/Documentation/DocBook/device-drivers.xml:
> 36908: parser warning : xmlParsePITarget: invalid name prefix 'xml'
> <?xmlif if excludeextra='1'?>
>        ^
> /home/iida/Repo/linux-next/Documentation/DocBook/device-drivers.xml:
> 36909: parser warning : xmlParsePITarget: invalid name prefix 'xml'
> <?xmlif else?>
>        ^
> /home/iida/Repo/linux-next/Documentation/DocBook/device-drivers.xml:
> 45909: parser warning : xmlParsePITarget: invalid name prefix 'xml'
> <?xmlif fi?>
>        ^
> How to reproduce
> (1) Clone linux-next repo.
> (2) make cleandocs
> (3) make htmldocs
> 
> This symptom can be reproduced current head (as of July/16th),
> as well as between "next-20150713" and "next-20150716".
> 
> Masanari Iida
-- 
Ben Hutchings
In a hierarchy, every employee tends to rise to his level of incompetence.


[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 811 bytes --]

  reply	other threads:[~2015-07-16 14:29 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-16 14:22 Masanari Iida
2015-07-16 14:28 ` Ben Hutchings [this message]
2015-07-16 14:31   ` Jonathan Corbet
2015-08-06 18:43     ` Jonathan Corbet
2015-08-06 22:39       ` Ben Hutchings

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=1437056936.3469.37.camel@decadent.org.uk \
    --to=ben@decadent.org.uk \
    --cc=corbet@lwn.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lunar@debian.org \
    --cc=standby24x7@gmail.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

Powered by JetHome