From: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
To: Linux Media Mailing List <linux-media@vger.kernel.org>
Cc: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>,
Jonathan Corbet <corbet@lwn.net>,
linux-doc@vger.kernel.org, Antoine Jacquet <royale@zerezo.com>,
linux-usb@vger.kernel.org
Subject: [PATCH 00/19] media: some documentation updates
Date: Tue, 14 Apr 2020 10:50:46 +0200 [thread overview]
Message-ID: <cover.1586854191.git.mchehab+huawei@kernel.org> (raw)
While looking at the media reorg struct, I noticed some things that
were outdated. So, I went ahead and started updating some documentation,
in order to make them to reflect the current state.
Mauro Carvalho Chehab (19):
media: docs: update cardlists
media: docs: split avermedia.rst contents on two files
media: docs: dvb_intro.rst: update its contents
media: docs: intro.rst actually contain DVB references
media: docs: update avermedia.rst contents
media: docs: bt8xx.rst: update document info
media: docs: update bttv.rst information
media: docs: add a cardlist for cx18 boards
media: docs: cpia2.rst: do some cleanups
media: docs: update Digital TV faq.rst
media: docs: saa7134.rst: update the documentation
media: docs: zr364xx: update documentation
media: docs: get rid of obsoleted udev documentation
media: docs: Add a master topic for the index file
media: docs: cleanup bttv-devel.rst file
media: docs: fix references for vimc
media: docs: move copyrights to the end and update them
media: docs: add GPLv2 for uAPI guide
media: docs: add cros-references to the other media guides
Documentation/admin-guide/media/avermedia.rst | 189 +-----
Documentation/admin-guide/media/bt8xx.rst | 134 ++--
Documentation/admin-guide/media/bttv.rst | 311 ++++-----
Documentation/admin-guide/media/cardlist.rst | 1 +
Documentation/admin-guide/media/cpia2.rst | 10 +-
.../admin-guide/media/cx18-cardlist.rst | 17 +
.../admin-guide/media/cx23885-cardlist.rst | 4 +
.../admin-guide/media/cx88-cardlist.rst | 4 +
Documentation/admin-guide/media/dvb_intro.rst | 616 ++++++++++++++++++
.../admin-guide/media/dvb_references.rst | 29 +
.../admin-guide/media/em28xx-cardlist.rst | 6 +-
Documentation/admin-guide/media/faq.rst | 253 ++++---
Documentation/admin-guide/media/index.rst | 44 +-
Documentation/admin-guide/media/intro.rst | 23 -
Documentation/admin-guide/media/saa7134.rst | 57 +-
Documentation/admin-guide/media/udev.rst | 63 --
Documentation/admin-guide/media/zr364xx.rst | 28 +-
.../driver-api/media/drivers/bttv-devel.rst | 53 +-
.../driver-api/media/drivers/index.rst | 37 +-
.../driver-api/media/drivers/vimc-devel.rst | 4 +-
Documentation/driver-api/media/index.rst | 34 +-
Documentation/userspace-api/media/index.rst | 44 +-
MAINTAINERS | 2 +-
23 files changed, 1228 insertions(+), 735 deletions(-)
create mode 100644 Documentation/admin-guide/media/cx18-cardlist.rst
create mode 100644 Documentation/admin-guide/media/dvb_intro.rst
create mode 100644 Documentation/admin-guide/media/dvb_references.rst
delete mode 100644 Documentation/admin-guide/media/intro.rst
delete mode 100644 Documentation/admin-guide/media/udev.rst
--
2.25.2
next reply other threads:[~2020-04-14 8:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-14 8:50 Mauro Carvalho Chehab [this message]
2020-04-14 8:50 ` [PATCH 12/19] media: docs: zr364xx: update documentation 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.1586854191.git.mchehab+huawei@kernel.org \
--to=mchehab+huawei@kernel.org \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=royale@zerezo.com \
/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;
as well as URLs for NNTP newsgroup(s).