public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: Mauro Carvalho Chehab <mchehab+samsung@kernel.org>
To: Linux Media Mailing List <linux-media@vger.kernel.org>
Cc: Mauro Carvalho Chehab <mchehab+samsung@kernel.org>,
	Mauro Carvalho Chehab <mchehab@infradead.org>,
	Hans Verkuil <hans.verkuil@cisco.com>,
	Sakari Ailus <sakari.ailus@linux.intel.com>
Subject: [PATCH 0/3] Add a glossary and fix some issues at open.rst docs
Date: Tue, 25 Sep 2018 09:06:50 -0300	[thread overview]
Message-ID: <cover.1537876293.git.mchehab+samsung@kernel.org> (raw)

Those three patches were part of an attempt to add definitions for
some terms used at the media subsystem:

	https://lwn.net/Articles/732022/

On that time, the first patch generated heated discussions, on terms
related to mc-centric/vdev-centric. The cern of the discussions were
how to call the subdev API and the non-subdev API part of the 
video4linux API.

I ended by being side-tracked by other things, and didn't have a chance
to submit an updated version.

Well, now I'm doing things differently: at the glossary.rst, I removed
everything related to hardware control. So, it should contain only the
terms that there aren't any divergences. So, I hope we can manage to
merge it this time.

After having this series merged, I'll address again the MC/vdev centric
hardware control on a separate patchset, perhaps using a different
approach together with the new glossary definitions related
to it.

Mauro Carvalho Chehab (3):
  media: add glossary.rst with common terms used at V4L2 spec
  media: open.rst: better document device node naming
  media: open.rst: remove the minor number range

 Documentation/media/uapi/v4l/glossary.rst | 108 ++++++++++++++++++++++
 Documentation/media/uapi/v4l/open.rst     |  53 +++++++++--
 Documentation/media/uapi/v4l/v4l2.rst     |   1 +
 3 files changed, 154 insertions(+), 8 deletions(-)
 create mode 100644 Documentation/media/uapi/v4l/glossary.rst

-- 
2.17.1

             reply	other threads:[~2018-09-25 18:14 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-25 12:06 Mauro Carvalho Chehab [this message]
2018-09-25 12:06 ` [PATCH 1/3] media: add glossary.rst with common terms used at V4L2 spec Mauro Carvalho Chehab
2018-09-25 13:03   ` Sakari Ailus
2018-09-25 14:07     ` Mauro Carvalho Chehab
2018-09-25 14:53       ` [PATCH v2] media: docs: " Mauro Carvalho Chehab
2018-09-25 12:06 ` [PATCH 2/3] media: open.rst: better document device node naming Mauro Carvalho Chehab
2018-09-25 12:06 ` [PATCH 3/3] media: open.rst: remove the minor number range Mauro Carvalho Chehab
2018-09-25 13:04 ` [PATCH 0/3] Add a glossary and fix some issues at open.rst docs Sakari Ailus

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.1537876293.git.mchehab+samsung@kernel.org \
    --to=mchehab+samsung@kernel.org \
    --cc=hans.verkuil@cisco.com \
    --cc=linux-media@vger.kernel.org \
    --cc=mchehab@infradead.org \
    --cc=sakari.ailus@linux.intel.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