<feed xmlns='http://www.w3.org/2005/Atom'>
<title>lwn.git/Documentation/media/uapi/v4l/dev-osd.rst, branch docs-6.8</title>
<subtitle>Linux kernel documentation tree maintained by Jonathan Corbet</subtitle>
<id>http://mirrors.hust.edu.cn/git/lwn.git/atom?h=docs-6.8</id>
<link rel='self' href='http://mirrors.hust.edu.cn/git/lwn.git/atom?h=docs-6.8'/>
<link rel='alternate' type='text/html' href='http://mirrors.hust.edu.cn/git/lwn.git/'/>
<updated>2020-04-14T08:31:49+00:00</updated>
<entry>
<title>media: docs: move uAPI book to userspace-api/media</title>
<updated>2020-04-14T08:31:49+00:00</updated>
<author>
<name>Mauro Carvalho Chehab</name>
<email>mchehab+huawei@kernel.org</email>
</author>
<published>2020-03-04T09:21:39+00:00</published>
<link rel='alternate' type='text/html' href='http://mirrors.hust.edu.cn/git/lwn.git/commit/?id=54f38fcae536ea202ce7d6a359521492fba30c1f'/>
<id>urn:sha1:54f38fcae536ea202ce7d6a359521492fba30c1f</id>
<content type='text'>
Since 2017, there is an space reserved for userspace API,
created by changeset 1d596dee3862 ("docs: Create a user-space API guide").

As the media subsystem was one of the first subsystems to use
Sphinx, until this patch, we were keeping things on a separate
place.

Let's just use the new location, as having all uAPI altogether
will likely make things easier for developers.

Signed-off-by: Mauro Carvalho Chehab &lt;mchehab+huawei@kernel.org&gt;
</content>
</entry>
<entry>
<title>media: add SPDX header to media uAPI files</title>
<updated>2018-12-05T15:39:18+00:00</updated>
<author>
<name>Mauro Carvalho Chehab</name>
<email>mchehab+samsung@kernel.org</email>
</author>
<published>2018-08-30T14:15:26+00:00</published>
<link rel='alternate' type='text/html' href='http://mirrors.hust.edu.cn/git/lwn.git/commit/?id=82559ac0273a68addb15535899cb1662de50a586'/>
<id>urn:sha1:82559ac0273a68addb15535899cb1662de50a586</id>
<content type='text'>
All those files are under GFDL 1.1 or later, with no invariant sections.
Tag them as such.

Signed-off-by: Mauro Carvalho Chehab &lt;mchehab+samsung@kernel.org&gt;
</content>
</entry>
<entry>
<title>media: remove text encoding from rst files</title>
<updated>2018-12-05T15:37:18+00:00</updated>
<author>
<name>Mauro Carvalho Chehab</name>
<email>mchehab+samsung@kernel.org</email>
</author>
<published>2018-08-30T14:09:48+00:00</published>
<link rel='alternate' type='text/html' href='http://mirrors.hust.edu.cn/git/lwn.git/commit/?id=18e6830a636cb61072c3ed970e1e4106df48ca29'/>
<id>urn:sha1:18e6830a636cb61072c3ed970e1e4106df48ca29</id>
<content type='text'>
This is not needed there. Also, the same UTF-8 encoding should
be used on all documents.

Signed-off-by: Mauro Carvalho Chehab &lt;mchehab+samsung@kernel.org&gt;
</content>
</entry>
<entry>
<title>[media] docs-rst: fix some broken struct references</title>
<updated>2016-09-09T12:55:18+00:00</updated>
<author>
<name>Mauro Carvalho Chehab</name>
<email>mchehab@s-opensource.com</email>
</author>
<published>2016-09-08T08:48:50+00:00</published>
<link rel='alternate' type='text/html' href='http://mirrors.hust.edu.cn/git/lwn.git/commit/?id=a17a954efde487f4072a33f05c5388bc42c51efc'/>
<id>urn:sha1:a17a954efde487f4072a33f05c5388bc42c51efc</id>
<content type='text'>
The :c:type: references point to the structure name, and not to
struct foo.

Fixed via this shell script:

	for i in `find Documentation/media -type f`; do perl -ne 'if (s/\:c\:type\:\`struct\s*(\S+)\`/struct :c:type:`$1`/) { s/struct\s+struct/struct/;  s/(struct\s+\:c\:type\:\`\S+\`)\s+structure/$1/;  } print $_' &lt;$i &gt;a &amp;&amp; mv a $i; done

Signed-off-by: Mauro Carvalho Chehab &lt;mchehab@s-opensource.com&gt;
</content>
</entry>
<entry>
<title>[media] docs-rst: simplify c:type: cross references</title>
<updated>2016-09-09T12:54:54+00:00</updated>
<author>
<name>Mauro Carvalho Chehab</name>
<email>mchehab@s-opensource.com</email>
</author>
<published>2016-09-08T08:43:01+00:00</published>
<link rel='alternate' type='text/html' href='http://mirrors.hust.edu.cn/git/lwn.git/commit/?id=fc78c7c7a1747912293ad9f78374f5be7f0acc6d'/>
<id>urn:sha1:fc78c7c7a1747912293ad9f78374f5be7f0acc6d</id>
<content type='text'>
Instead of using c:type:`struct foo &lt;foo&gt;`, use:
	struct c:type:`foo`

This patch was generated via this shell script:

	for i in `find Documentation/media -type f`; do perl -ne 'if (m/\:c\:type\:\`struct\s+(\S+)\s*\&lt;(\S+)\&gt;\`/) { $s=$1; $r=$2; if ($s eq $r) { s/\:c\:type\:\`struct\s+(\S+)\s*\&lt;(\S+)\&gt;\`/struct :c:type:`$2`/; s/struct\s+struct/struct/;  s/(struct\s+\:c\:type\:\`\S+\`)\s+structure/$1/;  }} print $_' &lt;$i &gt;a &amp;&amp; mv a $i; done

Signed-off-by: Mauro Carvalho Chehab &lt;mchehab@s-opensource.com&gt;
</content>
</entry>
<entry>
<title>[media] docs-rst: convert uAPI structs to C domain</title>
<updated>2016-09-09T12:34:01+00:00</updated>
<author>
<name>Mauro Carvalho Chehab</name>
<email>mchehab@s-opensource.com</email>
</author>
<published>2016-08-29T20:37:59+00:00</published>
<link rel='alternate' type='text/html' href='http://mirrors.hust.edu.cn/git/lwn.git/commit/?id=e8be7e97e639af6f968473e5a598afbebc737b9c'/>
<id>urn:sha1:e8be7e97e639af6f968473e5a598afbebc737b9c</id>
<content type='text'>
instead of declaring the uAPI structs using usual refs, e. g.:
	.. _foo-struct:

Use the C domain way:
	.. c:type:: foo_struct

This way, the kAPI documentation can use cross-references to
point to the uAPI symbols.

That solves about ~100 undefined warnings like:
	WARNING: c:type reference target not found: foo_struct

Signed-off-by: Mauro Carvalho Chehab &lt;mchehab@s-opensource.com&gt;
</content>
</entry>
<entry>
<title>[media] docs-rst: better use the .. note:: tag</title>
<updated>2016-08-22T13:02:29+00:00</updated>
<author>
<name>Mauro Carvalho Chehab</name>
<email>mchehab@s-opensource.com</email>
</author>
<published>2016-08-15T20:49:50+00:00</published>
<link rel='alternate' type='text/html' href='http://mirrors.hust.edu.cn/git/lwn.git/commit/?id=b6b6e67824ec0593878afbee5958d80205606210'/>
<id>urn:sha1:b6b6e67824ec0593878afbee5958d80205606210</id>
<content type='text'>
Change multi-line note tags to be more symetric, e. g. not starting
the text together witht the tag.

Signed-off-by: Mauro Carvalho Chehab &lt;mchehab@s-opensource.com&gt;
</content>
</entry>
<entry>
<title>Revert "[media] docs-rst: escape [] characters"</title>
<updated>2016-07-13T11:43:30+00:00</updated>
<author>
<name>Mauro Carvalho Chehab</name>
<email>mchehab@s-opensource.com</email>
</author>
<published>2016-07-13T11:43:30+00:00</published>
<link rel='alternate' type='text/html' href='http://mirrors.hust.edu.cn/git/lwn.git/commit/?id=8968da9b8622f2da9b7f0a695acbe341ea28f55e'/>
<id>urn:sha1:8968da9b8622f2da9b7f0a695acbe341ea28f55e</id>
<content type='text'>
This patch touches on places where it shouldn't: image
files and code examples. Also, it doesn't fix all array
occurrences.

So, let's revert it.

This reverts commit ffbab694ede33c294e5864a5e0bf4d1474446a71.
</content>
</entry>
<entry>
<title>[media] docs-rst: escape [] characters</title>
<updated>2016-07-12T18:20:11+00:00</updated>
<author>
<name>Mauro Carvalho Chehab</name>
<email>mchehab@s-opensource.com</email>
</author>
<published>2016-07-12T18:20:11+00:00</published>
<link rel='alternate' type='text/html' href='http://mirrors.hust.edu.cn/git/lwn.git/commit/?id=ffbab694ede33c294e5864a5e0bf4d1474446a71'/>
<id>urn:sha1:ffbab694ede33c294e5864a5e0bf4d1474446a71</id>
<content type='text'>
Those characters are used for citations. Better to escape, to
avoid them to be misinterpreted.

Signed-off-by: Mauro Carvalho Chehab &lt;mchehab@s-opensource.com&gt;
</content>
</entry>
<entry>
<title>[media] doc-rst: improve display of notes and warnings</title>
<updated>2016-07-10T15:06:28+00:00</updated>
<author>
<name>Mauro Carvalho Chehab</name>
<email>mchehab@s-opensource.com</email>
</author>
<published>2016-07-10T14:57:43+00:00</published>
<link rel='alternate' type='text/html' href='http://mirrors.hust.edu.cn/git/lwn.git/commit/?id=706f8a9975cb8889742d1f606ff466205ed29805'/>
<id>urn:sha1:706f8a9975cb8889742d1f606ff466205ed29805</id>
<content type='text'>
There are several notes and warning mesages in the middle of
the media docbook. Use the ReST tags for that, as it makes
them visually better and hightlights them.

While here, modify a few ones to make them clearer.

Signed-off-by: Mauro Carvalho Chehab &lt;mchehab@s-opensource.com&gt;
</content>
</entry>
</feed>
