<feed xmlns='http://www.w3.org/2005/Atom'>
<title>wireguard-linux/Documentation/media/uapi/dvb/headers.rst, branch jd/unified-crypt-queue</title>
<subtitle>WireGuard for the Linux kernel</subtitle>
<id>https://git.zx2c4.com/wireguard-linux/atom/Documentation/media/uapi/dvb/headers.rst?h=jd%2Funified-crypt-queue</id>
<link rel='self' href='https://git.zx2c4.com/wireguard-linux/atom/Documentation/media/uapi/dvb/headers.rst?h=jd%2Funified-crypt-queue'/>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/wireguard-linux/'/>
<updated>2018-12-05T15:39:18Z</updated>
<entry>
<title>media: add SPDX header to media uAPI files</title>
<updated>2018-12-05T15:39:18Z</updated>
<author>
<name>Mauro Carvalho Chehab</name>
<email>mchehab+samsung@kernel.org</email>
</author>
<published>2018-08-30T14:15:26Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/wireguard-linux/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: dvb uapi docs: better organize header files</title>
<updated>2017-09-05T10:14:16Z</updated>
<author>
<name>Mauro Carvalho Chehab</name>
<email>mchehab@s-opensource.com</email>
</author>
<published>2017-09-01T14:02:23Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/wireguard-linux/commit/?id=07ebca6202380c2f9d700e1b37a98a63b68b72c7'/>
<id>urn:sha1:07ebca6202380c2f9d700e1b37a98a63b68b72c7</id>
<content type='text'>
Instead of having one chapter per file, place all of them at
the same chapter. That better organize the chapters at the uAPI
documentation.

As a side effect, now all uAPI headers are at the same page,
at the html output, with makes easier to use it as a reference
index for the spec.

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