driver-api/media/maintainer-entry-profile.rst

5 --------
8 capture, analog and digital TV streams, cameras, remote controllers, HDMI CEC
13   - drivers/media
14   - drivers/staging/media
15   - Documentation/admin-guide/media
16   - Documentation/driver-api/media
17   - Documentation/userspace-api/media
18   - Documentation/devicetree/bindings/media/\ [1]_
19   - include/media
33 maintainership model is to have sub-maintainers that have a broad
34 knowledge of a specific aspect of the subsystem. It is the sub-maintainers'
40 at linux-media@vger.kernel.org as plain text only e-mail. Emails with
42 to also copy the sub-maintainer(s).
45 is submitted, the e-mail will first be accepted by the mailing list
48    - https://patchwork.linuxtv.org/project/linux-media/list/
57    - https://lore.kernel.org/linux-media/
68 sub-maintainers), and another senior developer responsible for the
74 - Remote Controllers (infrared):
77 - HDMI CEC:
80 - Media controller drivers:
83 - ISP, v4l2-async, v4l2-fwnode, v4l2-flash-led-class and Sensor drivers:
86 - V4L2 drivers and core V4L2 frameworks:
97 -------------------------
104 There is a set of compliance tools at https://git.linuxtv.org/v4l-utils.git/
111 V4L2 drivers\ [3]_	``v4l2-compliance``
112 V4L2 virtual drivers	``contrib/test/test-media``
113 CEC drivers		``cec-compliance``
116 .. [3] The ``v4l2-compliance`` also covers the media controller usage inside
126 	make CF=-D__CHECK_ENDIAN__ CONFIG_DEBUG_SECTION_MISMATCH=y C=1 W=1 CHECK=check_script
131 	/devel/smatch/smatch -p=kernel $@ >&2
156 	$ ./scripts/checkpatch.pl --strict --max-line-length=80
169 characters per line. This could include using re-factoring code that leads
175     - on strings, as they shouldn't be broken due to line length limits;
176     - when a function or variable name need to have a big identifier name,
178     - on arithmetic expressions, when breaking lines makes them harder to
180     - when they avoid a line to end with an open parenthesis or an open
184 ---------------
187 next merge window they should be sent before -rc5, and ideally stabilized
188 in the linux-media branch by -rc6.
191 --------------
194 be sooner or later handled, so you don't need to re-submit a patch.
197 tree between -rc6 and the next -rc1.
202 other developers to publicly add Reviewed-by and, more importantly,
203 ``Tested-by:`` tags.
205 Please note that we expect a detailed description for ``Tested-by:``,