From: Mauro Carvalho Chehab <mchehab@s-opensource.com>
To: Linux Doc Mailing List <linux-doc@vger.kernel.org>,
Linux Media Mailing List <linux-media@vger.kernel.org>
Cc: "Mauro Carvalho Chehab" <mchehab@s-opensource.com>,
"Mauro Carvalho Chehab" <mchehab@infradead.org>,
linux-kernel@vger.kernel.org, "Jonathan Corbet" <corbet@lwn.net>,
"Honza Petrouš" <jpetrous@gmail.com>
Subject: [PATCH 0/2] Documents the two remaining CA ioctls
Date: Mon, 4 Sep 2017 09:15:30 -0300 [thread overview]
Message-ID: <cover.1504526763.git.mchehab@s-opensource.com> (raw)
Thanks to some discussions I had with Honza, I got some ideas about how to
document the last three undocumented ioctls from ca.h, together with the
two data structures.
With this series (and the previous one), everything at CA, Net, Demux
and DVBv5 Frontend DVB APIs are now documented. That's IMHO
a very good reason to celebrate! Yay!
Please notice that are still gaps at the DVB API documentation, but
those are related to legacy stuff that aren't touched for ages
(DVBv3 frontend API, audio.h, osd.h and video.h). The legacy
DVBv3 frontend API was completely replaced by DVBv5 API.
The other ones are used only by a single driver (av7110).
Mauro Carvalho Chehab (2):
media: ca docs: document CA_SET_DESCR ioctl and structs
media: ca.h: document ca_msg and the corresponding ioctls
Documentation/media/uapi/dvb/ca-get-msg.rst | 19 ++++++-------------
Documentation/media/uapi/dvb/ca-send-msg.rst | 6 +++++-
Documentation/media/uapi/dvb/ca-set-descr.rst | 15 ++-------------
include/uapi/linux/dvb/ca.h | 20 ++++++++++++++++++--
4 files changed, 31 insertions(+), 29 deletions(-)
--
2.13.5
next reply other threads:[~2017-09-04 12:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-04 12:15 Mauro Carvalho Chehab [this message]
2017-09-04 12:15 ` [PATCH 1/2] media: ca docs: document CA_SET_DESCR ioctl and structs Mauro Carvalho Chehab
2017-09-04 12:15 ` [PATCH 2/2] media: ca.h: document ca_msg and the corresponding ioctls Mauro Carvalho Chehab
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=cover.1504526763.git.mchehab@s-opensource.com \
--to=mchehab@s-opensource.com \
--cc=corbet@lwn.net \
--cc=jpetrous@gmail.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@infradead.org \
/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