From: Hans Verkuil <hverkuil@xs4all.nl>
To: Antti Palosaari <crope@iki.fi>, linux-media@vger.kernel.org
Cc: Philipp Zabel <p.zabel@pengutronix.de>
Subject: Re: [PATCH] DocBook: fix vidioc-qbuf.xml doc validation
Date: Sun, 17 May 2015 13:14:16 +0200 [thread overview]
Message-ID: <55587808.4070605@xs4all.nl> (raw)
In-Reply-To: <1431828874-8108-1-git-send-email-crope@iki.fi>
Duplicate of http://www.spinics.net/lists/linux-media/msg89715.html
Just posted the pull request containing that patch.
I noticed the same problem on Friday :-)
Regards,
Hans
On 05/17/2015 04:14 AM, Antti Palosaari wrote:
> element varlistentry: validity error : Element varlistentry content
> does not follow the DTD, expecting (term+ , listitem), got (term
> listitem term listitem )
>
> commit 8cee396bfa77ce3a2e5fe48f597206c1cd547f9c
> [media] DocBook media: document codec draining flow
> breaks document validation. Fix it.
>
> Cc: Philipp Zabel <p.zabel@pengutronix.de>
> Cc: Hans Verkuil <hverkuil@xs4all.nl>
> Signed-off-by: Antti Palosaari <crope@iki.fi>
> ---
> Documentation/DocBook/media/v4l/vidioc-qbuf.xml | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/Documentation/DocBook/media/v4l/vidioc-qbuf.xml b/Documentation/DocBook/media/v4l/vidioc-qbuf.xml
> index 6cfc53b..f5cef97 100644
> --- a/Documentation/DocBook/media/v4l/vidioc-qbuf.xml
> +++ b/Documentation/DocBook/media/v4l/vidioc-qbuf.xml
> @@ -186,6 +186,8 @@ In that case the application should be able to safely reuse the buffer and
> continue streaming.
> </para>
> </listitem>
> + </varlistentry>
> + <varlistentry>
> <term><errorcode>EPIPE</errorcode></term>
> <listitem>
> <para><constant>VIDIOC_DQBUF</constant> returns this on an empty
>
prev parent reply other threads:[~2015-05-17 11:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-17 2:14 [PATCH] DocBook: fix vidioc-qbuf.xml doc validation Antti Palosaari
2015-05-17 11:14 ` Hans Verkuil [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=55587808.4070605@xs4all.nl \
--to=hverkuil@xs4all.nl \
--cc=crope@iki.fi \
--cc=linux-media@vger.kernel.org \
--cc=p.zabel@pengutronix.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.