Re: [PATCH for v3.5] V4L2 spec fix

[Guennadi Liakhovetski <g.liakhovetski@xxxxxx>]

Thanks for the patch, Hans

On Wed, 6 Jun 2012, Hans Verkuil wrote:

> Two small docbook fixes:
> 
> - prepare-buf was not positioned in alphabetical order, moved to the right place.
> - the format field in create_bufs had the wrong type in the documentation
> 
> Regards,
> 
> 	Hans
> 
> Signed-off-by: Hans Verkuil <hans.verkuil@xxxxxxxxx>

Reviewed-by: Guennadi Liakhovetski <g.liakhovetski@xxxxxx>

Thanks
Guennadi

> 
> diff --git a/Documentation/DocBook/media/v4l/v4l2.xml b/Documentation/DocBook/media/v4l/v4l2.xml
> index 015c561..008c2d7 100644
> --- a/Documentation/DocBook/media/v4l/v4l2.xml
> +++ b/Documentation/DocBook/media/v4l/v4l2.xml
> @@ -560,6 +560,7 @@ and discussions on the V4L mailing list.</revremark>
>      &sub-g-tuner;
>      &sub-log-status;
>      &sub-overlay;
> +    &sub-prepare-buf;
>      &sub-qbuf;
>      &sub-querybuf;
>      &sub-querycap;
> @@ -567,7 +568,6 @@ and discussions on the V4L mailing list.</revremark>
>      &sub-query-dv-preset;
>      &sub-query-dv-timings;
>      &sub-querystd;
> -    &sub-prepare-buf;
>      &sub-reqbufs;
>      &sub-s-hw-freq-seek;
>      &sub-streamon;
> diff --git a/Documentation/DocBook/media/v4l/vidioc-create-bufs.xml b/Documentation/DocBook/media/v4l/vidioc-create-bufs.xml
> index 765549f..6cd2bc3 100644
> --- a/Documentation/DocBook/media/v4l/vidioc-create-bufs.xml
> +++ b/Documentation/DocBook/media/v4l/vidioc-create-bufs.xml
> @@ -108,7 +108,7 @@ information.</para>
>  /></entry>
>  	  </row>
>  	  <row>
> -	    <entry>__u32</entry>
> +	    <entry>struct&nbsp;v4l2_format</entry>
>  	    <entry><structfield>format</structfield></entry>
>  	    <entry>Filled in by the application, preserved by the driver.
>  	    See <xref linkend="v4l2-format" />.</entry>
> 

---
Guennadi Liakhovetski, Ph.D.
Freelance Open-Source Software Developer
http://www.open-technology.de/
--
To unsubscribe from this list: send the line "unsubscribe linux-media" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html