Linux-Media Archive on
 help / color / Atom feed
From: Mauro Carvalho Chehab <>
To: Linux Media Mailing List <>
Cc: Mauro Carvalho Chehab <>,
	Mauro Carvalho Chehab <>,
	Dan Williams <>,
Subject: [PATCH] media: add a subsystem profile documentation
Date: Fri, 13 Sep 2019 13:19:21 -0300
Message-ID: <> (raw)
In-Reply-To: <>

Document the basic policies of the media subsystem profile.

Signed-off-by: Mauro Carvalho Chehab <>

That's basically a modified version of:

Applied to the new template

 Documentation/media/index.rst                 |   1 +
 .../media/maintainer-entry-profile.rst        | 140 ++++++++++++++++++
 MAINTAINERS                                   |   1 +
 3 files changed, 142 insertions(+)
 create mode 100644 Documentation/media/maintainer-entry-profile.rst

diff --git a/Documentation/media/index.rst b/Documentation/media/index.rst
index 0301c25ff887..ac94685b822a 100644
--- a/Documentation/media/index.rst
+++ b/Documentation/media/index.rst
@@ -12,6 +12,7 @@ Linux Media Subsystem Documentation
 .. toctree::
    :maxdepth: 2
+   maintainer-entry-profile
diff --git a/Documentation/media/maintainer-entry-profile.rst b/Documentation/media/maintainer-entry-profile.rst
new file mode 100644
index 000000000000..81d3b0f9c36a
--- /dev/null
+++ b/Documentation/media/maintainer-entry-profile.rst
@@ -0,0 +1,140 @@
+Media Subsystem Profile
+The media subsystem cover support for a variety of devices: stream
+capture, analog and digital TV, cameras, remote controllers, HDMI CEC
+and media pipeline control.
+It covers, mainly, the contents of those directories:
+  - drivers/media
+  - drivers/staging/media
+  - Documentation/media
+  - include/media
+Both media userspace and Kernel APIs are documented and should be kept in
+sync with the API changes. It means that all patches that add new
+features to the subsystem should also bring changes to the corresponding
+API files.
+Also, patches for device drivers that changes the Open Firmware/Device
+Tree bindings should be reviewed by the Device Tree maintainers.
+Due to the size and wide scope of the media subsystem, media's
+maintainership model is to have sub-maintainers that have a broad
+knowledge of an specific aspect of the subsystem. It is a
+sub-maintainers task to review the patches, providing feedback to users
+if the patches are following the subsystem rules and are properly using
+the media internal and external APIs.
+Patches for the media subsystem should be sent to the media mailing list
+at as plain text only e-mail. Emails with
+HTML will be automatically rejected by the mail server. There's no need
+to copy the maintainer or sub-maintainer(s).
+Media's workflow is heavily based on Patchwork, meaning that, once a patch
+is submitted, it should appear at:
+   -
+If it doesn't automatically appear there after a few minutes, then
+probably something got wrong on your submission. Please check if the
+email is in plain text only and if your emailer is not mangling with
+whitespaces before complaining or submit it again.
+At the media subsystem, we have a group of senior developers that are
+responsible for doing the code reviews at the drivers (called
+sub-maintainers), and another senior developer responsible for the
+subsystem as a hole. For core changes, whenever possible, multiple
+media (sub-)maintainers do the review.
+The sub-maintainers work on specific areas of the subsystem, as
+described below:
+Digital TV:
+  Sean Young <>
+  Hans Verkuil <>
+Media controller drivers:
+  Laurent Pinchart <>
+Remote Controllers:
+  Sean Young <>
+Sensor drivers:
+  Sakari Ailus <>
+V4L2 drivers:
+  Hans Verkuil <>
+Submit Checklist Addendum
+There is a set of compliance tools at
+that should be used in order to check if the drivers are properly
+implementing the media APIs.
+Those tests need to be passed before the patches go upstream.
+Also, please notice that we build the Kernel with::
+Where the check script is::
+	#!/bin/bash
+	/devel/smatch/smatch -p=kernel $@ >&2
+	/devel/sparse/sparse $@ >&2
+Be sure to not introduce new warnings on your patches.
+Key Cycle Dates
+New submissions can be sent at any time, but if they intend to hit the
+next merge window they should be sent before -rc5, and ideally stabilized
+in the linux-media branch by -rc6.
+Coding Style Addendum
+Media development uses checkpatch on strict mode to verify the code style, e. g.::
+	$ ./script/ --strict
+Review Cadence
+Provided that your patch is at, it should
+be sooner or later handled, so you don't need to re-submit a patch.
+Except for bug fixes, we don't usually add new patches to the development
+tree between -rc6 and the next -rc1.
+Please notice that the media subsystem is a high traffic one, so it
+could take a while for us to be able to review your patches. Feel free
+to ping if you don't get a feedback on a couple of weeks or to ask
+other developers to publicly add Reviewed-by and, more importantly,
+Tested-by tags.
+Please notice that we expect a detailed description for Tested-by,
+identifying what boards were used at the test and what it was tested.
+Style Cleanup Patches
+Style-cleanups are welcome when they come together with other changes
+at the files where the style changes will affect.
+We may accept pure standalone style-cleanups, but they should be grouped
+per directory. So, for example, if you're doing a cleanup at drivers
+under drivers/media, please send a single patch for all drivers under
+drivers/media/pci, another one for drivers/media/usb and so on.
index 7c62b45201d7..e7f44ec05a42 100644
@@ -10077,6 +10077,7 @@ W:
 T:	git git://
 S:	Maintained
+P:	Documentation/media/maintainer-entry-profile.rst
 F:	Documentation/devicetree/bindings/media/
 F:	Documentation/media/
 F:	drivers/media/

           reply index

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <>]

Reply instructions:

You may reply publically 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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \ \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

Linux-Media Archive on

Archives are clonable:
	git clone --mirror linux-media/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 linux-media linux-media/ \
	public-inbox-index linux-media

Newsgroup available over NNTP:

AGPL code for this site: git clone public-inbox