sphinx.addnodesdocument)}( rawsource children](translations
LanguagesNode)}(hhh](h pending_xref)}(hhh]docutils.nodesTextChinese (Simplified)}parenthsba
attributes}(ids]classes]names]dupnames]backrefs] refdomainstdreftypedoc reftarget=/translations/zh_CN/driver-api/media/maintainer-entry-profilemodnameN classnameNrefexplicitutagnamehhhubh)}(hhh]hChinese (Traditional)}hh2sbah}(h]h ]h"]h$]h&] refdomainh)reftypeh+ reftarget=/translations/zh_TW/driver-api/media/maintainer-entry-profilemodnameN classnameNrefexplicituh1hhhubh)}(hhh]hItalian}hhFsbah}(h]h ]h"]h$]h&] refdomainh)reftypeh+ reftarget=/translations/it_IT/driver-api/media/maintainer-entry-profilemodnameN classnameNrefexplicituh1hhhubh)}(hhh]hJapanese}hhZsbah}(h]h ]h"]h$]h&] refdomainh)reftypeh+ reftarget=/translations/ja_JP/driver-api/media/maintainer-entry-profilemodnameN classnameNrefexplicituh1hhhubh)}(hhh]hKorean}hhnsbah}(h]h ]h"]h$]h&] refdomainh)reftypeh+ reftarget=/translations/ko_KR/driver-api/media/maintainer-entry-profilemodnameN classnameNrefexplicituh1hhhubh)}(hhh]hPortuguese (Brazilian)}hhsbah}(h]h ]h"]h$]h&] refdomainh)reftypeh+ reftarget=/translations/pt_BR/driver-api/media/maintainer-entry-profilemodnameN classnameNrefexplicituh1hhhubh)}(hhh]hSpanish}hhsbah}(h]h ]h"]h$]h&] refdomainh)reftypeh+ reftarget=/translations/sp_SP/driver-api/media/maintainer-entry-profilemodnameN classnameNrefexplicituh1hhhubeh}(h]h ]h"]h$]h&]current_languageEnglishuh1h
hh _documenthsourceNlineNubhcomment)}(h SPDX-License-Identifier: GPL-2.0h]h SPDX-License-Identifier: GPL-2.0}hhsbah}(h]h ]h"]h$]h&] xml:spacepreserveuh1hhhhhhW/var/lib/git/docbuild/linux/Documentation/driver-api/media/maintainer-entry-profile.rsthKubhsection)}(hhh](htitle)}(hMedia Subsystem Profileh]hMedia Subsystem Profile}(hhhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhhhhhKubh)}(hhh](h)}(hOverviewh]hOverview}(hhhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhhhhhKubh paragraph)}(hThe Linux Media Community (aka: the LinuxTV Community) is formed by
developers working on Linux Kernel Media Subsystem, together with users
who also play an important role in testing the code.h]hThe Linux Media Community (aka: the LinuxTV Community) is formed by
developers working on Linux Kernel Media Subsystem, together with users
who also play an important role in testing the code.}(hhhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhK hhhhubh)}(hThe Media Subsystem has code to support a wide variety of media-related
devices: stream capture, analog and digital TV streams, cameras,
video codecs, video processing (resizers, etc.), radio, remote controllers,
HDMI CEC and media pipeline control.h]hThe Media Subsystem has code to support a wide variety of media-related
devices: stream capture, analog and digital TV streams, cameras,
video codecs, video processing (resizers, etc.), radio, remote controllers,
HDMI CEC and media pipeline control.}(hhhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhK
hhhhubh)}(hMThe Media Subsystem consists of the following directories in the kernel
tree:h]hMThe Media Subsystem consists of the following directories in the kernel
tree:}(hj hhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhKhhhhubhblock_quote)}(h- drivers/media
- drivers/staging/media
- include/media
- Documentation/devicetree/bindings/media/\ [1]_
- Documentation/admin-guide/media
- Documentation/driver-api/media
- Documentation/userspace-api/media
h]hbullet_list)}(hhh](h list_item)}(h
drivers/mediah]h)}(hj) h]h
drivers/media}(hj+ hhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhKhj' ubah}(h]h ]h"]h$]h&]uh1j% hj" ubj& )}(hdrivers/staging/mediah]h)}(hj@ h]hdrivers/staging/media}(hjB hhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhKhj> ubah}(h]h ]h"]h$]h&]uh1j% hj" ubj& )}(h
include/mediah]h)}(hjW h]h
include/media}(hjY hhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhKhjU ubah}(h]h ]h"]h$]h&]uh1j% hj" ubj& )}(h.Documentation/devicetree/bindings/media/\ [1]_h]h)}(hjn h](h*Documentation/devicetree/bindings/media/ }(hjp hhhNhNubhfootnote_reference)}(h[1]_h]h1}(hjy hhhNhNubah}(h]id1ah ]h"]h$]h&]refidid2docname)driver-api/media/maintainer-entry-profileuh1jw hjp resolvedKubeh}(h]h ]h"]h$]h&]uh1hhhhKhjl ubah}(h]h ]h"]h$]h&]uh1j% hj" ubj& )}(hDocumentation/admin-guide/mediah]h)}(hj h]hDocumentation/admin-guide/media}(hj hhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhKhj ubah}(h]h ]h"]h$]h&]uh1j% hj" ubj& )}(hDocumentation/driver-api/mediah]h)}(hj h]hDocumentation/driver-api/media}(hj hhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhKhj ubah}(h]h ]h"]h$]h&]uh1j% hj" ubj& )}(h"Documentation/userspace-api/media
h]h)}(h!Documentation/userspace-api/mediah]h!Documentation/userspace-api/media}(hj hhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhKhj ubah}(h]h ]h"]h$]h&]uh1j% hj" ubeh}(h]h ]h"]h$]h&]bullet-uh1j hhhKhj ubah}(h]h ]h"]h$]h&]uh1j hhhKhhhhubhfootnote)}(hDevice tree bindings are maintained by the
OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS maintainers
(see the MAINTAINERS file). So, changes there must be reviewed
by them before being merged into the media subsystem's development
tree.
h](hlabel)}(h1h]h1}(hj hhhNhNubah}(h]h ]h"]h$]h&]uh1j hj ubh)}(hDevice tree bindings are maintained by the
OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS maintainers
(see the MAINTAINERS file). So, changes there must be reviewed
by them before being merged into the media subsystem's development
tree.h]hDevice tree bindings are maintained by the
OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS maintainers
(see the MAINTAINERS file). So, changes there must be reviewed
by them before being merged into the media subsystem’s development
tree.}(hj hhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhKhj ubeh}(h]j ah ]h"]1ah$]h&]j aj j uh1j hhhKhhhhj Kubh)}(hBoth media userspace and Kernel APIs are documented and the documentation
must be kept in sync with the API changes. It means that all patches that
add new features to the subsystem must also bring changes to the
corresponding API documentation.h]hBoth media userspace and Kernel APIs are documented and the documentation
must be kept in sync with the API changes. It means that all patches that
add new features to the subsystem must also bring changes to the
corresponding API documentation.}(hj hhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhK#hhhhubeh}(h]overviewah ]h"]overviewah$]h&]uh1hhhhhhhhKubh)}(hhh](h)}(hMedia Maintainersh]hMedia Maintainers}(hj1 hhhNhNubah}(h]h ]h"]h$]h&]uh1hhj. hhhhhK)ubh)}(hX Media Maintainers are not just people capable of writing code, but they
are developers who have demonstrated their ability to collaborate with
the team, get the most knowledgeable people to review code, contribute
high-quality code, and follow through to fix issues (in code or tests).h]hX Media Maintainers are not just people capable of writing code, but they
are developers who have demonstrated their ability to collaborate with
the team, get the most knowledgeable people to review code, contribute
high-quality code, and follow through to fix issues (in code or tests).}(hj? hhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhK+hj. hhubh)}(hDue to the size and wide scope of the media subsystem, multiple layers of
maintainers are required, each with their own areas of expertise:h]hDue to the size and wide scope of the media subsystem, multiple layers of
maintainers are required, each with their own areas of expertise:}(hjM hhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhK0hj. hhubj! )}(hhh](j& )}(hX< **Media Driver Maintainer**:
Responsible for one or more drivers within the Media Subsystem. They
are listed in the MAINTAINERS file as maintainer for those drivers. Media
Driver Maintainers review patches for those drivers, provide feedback if
patches do not follow the subsystem rules, or are not using the
media kernel or userspace APIs correctly, or if they have poor code
quality.
If you are the patch author, you work with other Media
Maintainers to ensure your patches are reviewed.
Some Media Driver Maintainers have additional responsibilities. They have
been granted Patchwork access and keep
`Patchwork `_
up to date, decide when patches are ready for merging, and create Pull
Requests for the Media Subsystem Maintainers to merge.
h]hdefinition_list)}(hhh]hdefinition_list_item)}(hX" **Media Driver Maintainer**:
Responsible for one or more drivers within the Media Subsystem. They
are listed in the MAINTAINERS file as maintainer for those drivers. Media
Driver Maintainers review patches for those drivers, provide feedback if
patches do not follow the subsystem rules, or are not using the
media kernel or userspace APIs correctly, or if they have poor code
quality.
If you are the patch author, you work with other Media
Maintainers to ensure your patches are reviewed.
Some Media Driver Maintainers have additional responsibilities. They have
been granted Patchwork access and keep
`Patchwork `_
up to date, decide when patches are ready for merging, and create Pull
Requests for the Media Subsystem Maintainers to merge.
h](hterm)}(h**Media Driver Maintainer**:h](hstrong)}(h**Media Driver Maintainer**h]hMedia Driver Maintainer}(hju hhhNhNubah}(h]h ]h"]h$]h&]uh1js hjo ubh:}(hjo hhhNhNubeh}(h]h ]h"]h$]h&]uh1jm hhhKBhji ubh
definition)}(hhh](h)}(hXd Responsible for one or more drivers within the Media Subsystem. They
are listed in the MAINTAINERS file as maintainer for those drivers. Media
Driver Maintainers review patches for those drivers, provide feedback if
patches do not follow the subsystem rules, or are not using the
media kernel or userspace APIs correctly, or if they have poor code
quality.h]hXd Responsible for one or more drivers within the Media Subsystem. They
are listed in the MAINTAINERS file as maintainer for those drivers. Media
Driver Maintainers review patches for those drivers, provide feedback if
patches do not follow the subsystem rules, or are not using the
media kernel or userspace APIs correctly, or if they have poor code
quality.}(hj hhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhK4hj ubh)}(hgIf you are the patch author, you work with other Media
Maintainers to ensure your patches are reviewed.h]hgIf you are the patch author, you work with other Media
Maintainers to ensure your patches are reviewed.}(hj hhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhK;hj ubh)}(hX5 Some Media Driver Maintainers have additional responsibilities. They have
been granted Patchwork access and keep
`Patchwork `_
up to date, decide when patches are ready for merging, and create Pull
Requests for the Media Subsystem Maintainers to merge.h](hqSome Media Driver Maintainers have additional responsibilities. They have
been granted Patchwork access and keep
}(hj hhhNhNubh reference)}(hF`Patchwork `_h]h Patchwork}(hj hhhNhNubah}(h]h ]h"]h$]h&]name Patchworkrefuri7https://patchwork.linuxtv.org/project/linux-media/list/uh1j hj ubhtarget)}(h: h]h}(h] patchworkah ]h"] patchworkah$]h&]refurij uh1j
referencedKhj ubh~
up to date, decide when patches are ready for merging, and create Pull
Requests for the Media Subsystem Maintainers to merge.}(hj hhhNhNubeh}(h]h ]h"]h$]h&]uh1hhhhK>hj ubeh}(h]h ]h"]h$]h&]uh1j hji ubeh}(h]h ]h"]h$]h&]uh1jg hhhKBhjd ubah}(h]h ]h"]h$]h&]uh1jb hj^ ubah}(h]h ]h"]h$]h&]uh1j% hj[ hhhNhNubj& )}(hX} **Media Core Maintainer**:
Media Driver Maintainers with Patchwork access who are also responsible for
one or more media core frameworks.
Core framework changes are done via consensus between the relevant Media
Core Maintainers. Media Maintainers may include core framework changes in
their Pull Requests if they are signed off by the relevant Media Core
Maintainers.
h]jc )}(hhh]jh )}(hXq **Media Core Maintainer**:
Media Driver Maintainers with Patchwork access who are also responsible for
one or more media core frameworks.
Core framework changes are done via consensus between the relevant Media
Core Maintainers. Media Maintainers may include core framework changes in
their Pull Requests if they are signed off by the relevant Media Core
Maintainers.
h](jn )}(h**Media Core Maintainer**:h](jt )}(h**Media Core Maintainer**h]hMedia Core Maintainer}(hj hhhNhNubah}(h]h ]h"]h$]h&]uh1js hj ubh:}(hj hhhNhNubeh}(h]h ]h"]h$]h&]uh1jm hhhKKhj ubj )}(hhh](h)}(hnMedia Driver Maintainers with Patchwork access who are also responsible for
one or more media core frameworks.h]hnMedia Driver Maintainers with Patchwork access who are also responsible for
one or more media core frameworks.}(hj& hhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhKEhj# ubh)}(hCore framework changes are done via consensus between the relevant Media
Core Maintainers. Media Maintainers may include core framework changes in
their Pull Requests if they are signed off by the relevant Media Core
Maintainers.h]hCore framework changes are done via consensus between the relevant Media
Core Maintainers. Media Maintainers may include core framework changes in
their Pull Requests if they are signed off by the relevant Media Core
Maintainers.}(hj4 hhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhKHhj# ubeh}(h]h ]h"]h$]h&]uh1j hj ubeh}(h]h ]h"]h$]h&]uh1jg hhhKKhj ubah}(h]h ]h"]h$]h&]uh1jb hj ubah}(h]h ]h"]h$]h&]uh1j% hj[ hhhNhNubj& )}(hX **Media Subsystem Maintainers**:
Media Core Maintainers who are also responsible for the subsystem as a
whole, with access to the entire subsystem. Responsible for merging Pull
Requests from other Media Maintainers.
Userspace API/ABI changes are made via consensus among Media Subsystem
Maintainers\ [2]_. Media Maintainers may include API/ABI changes in
their Pull Requests if they are signed off by all Media Subsystem
Maintainers.
h]jc )}(hhh]jh )}(hX **Media Subsystem Maintainers**:
Media Core Maintainers who are also responsible for the subsystem as a
whole, with access to the entire subsystem. Responsible for merging Pull
Requests from other Media Maintainers.
Userspace API/ABI changes are made via consensus among Media Subsystem
Maintainers\ [2]_. Media Maintainers may include API/ABI changes in
their Pull Requests if they are signed off by all Media Subsystem
Maintainers.
h](jn )}(h **Media Subsystem Maintainers**:h](jt )}(h**Media Subsystem Maintainers**h]hMedia Subsystem Maintainers}(hji hhhNhNubah}(h]h ]h"]h$]h&]uh1js hje ubh:}(hje hhhNhNubeh}(h]h ]h"]h$]h&]uh1jm hhhKUhja ubj )}(hhh](h)}(hMedia Core Maintainers who are also responsible for the subsystem as a
whole, with access to the entire subsystem. Responsible for merging Pull
Requests from other Media Maintainers.h]hMedia Core Maintainers who are also responsible for the subsystem as a
whole, with access to the entire subsystem. Responsible for merging Pull
Requests from other Media Maintainers.}(hj hhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhKNhj ubh)}(hUserspace API/ABI changes are made via consensus among Media Subsystem
Maintainers\ [2]_. Media Maintainers may include API/ABI changes in
their Pull Requests if they are signed off by all Media Subsystem
Maintainers.h](hTUserspace API/ABI changes are made via consensus among Media Subsystem
Maintainers }(hj hhhNhNubjx )}(h[2]_h]h2}(hj hhhNhNubah}(h]id3ah ]h"]h$]h&]j id4j j uh1jw hj j Kubh. Media Maintainers may include API/ABI changes in
their Pull Requests if they are signed off by all Media Subsystem
Maintainers.}(hj hhhNhNubeh}(h]h ]h"]h$]h&]uh1hhhhKRhj ubeh}(h]h ]h"]h$]h&]uh1j hja ubeh}(h]h ]h"]h$]h&]uh1jg hhhKUhj^ ubah}(h]h ]h"]h$]h&]uh1jb hjZ ubah}(h]h ]h"]h$]h&]uh1j% hj[ hhhNhNubeh}(h]h ]h"]h$]h&]j j uh1j hhhK3hj. hhubh)}(hAll Media Maintainers shall agree with the Kernel development process as
described in Documentation/process/index.rst and with the Kernel development
rules in the Kernel documentation, including its code of conduct.h]hAll Media Maintainers shall agree with the Kernel development process as
described in Documentation/process/index.rst and with the Kernel development
rules in the Kernel documentation, including its code of conduct.}(hj hhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhKWhj. hhubh)}(hOMedia Maintainers are often reachable via the #linux-media IRC channel at OFTC.h]hOMedia Maintainers are often reachable via the #linux-media IRC channel at OFTC.}(hj hhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhK[hj. hhubj )}(hEverything that would break backward compatibility with existing
non-kernel code are API/ABI changes. This includes ioctl and sysfs
interfaces, v4l2 controls, and their behaviors.
h](j )}(h2h]h2}(hj hhhNhNubah}(h]h ]h"]h$]h&]uh1j hj ubh)}(hEverything that would break backward compatibility with existing
non-kernel code are API/ABI changes. This includes ioctl and sysfs
interfaces, v4l2 controls, and their behaviors.h]hEverything that would break backward compatibility with existing
non-kernel code are API/ABI changes. This includes ioctl and sysfs
interfaces, v4l2 controls, and their behaviors.}(hj hhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhK]hj ubeh}(h]j ah ]h"]2ah$]h&]j aj j uh1j hhhK]hj. hhj Kubeh}(h]media-maintainersah ]h"]media maintainersah$]h&]uh1hhhhhhhhK)ubh)}(hhh](h)}(hPatchwork Accessh]hPatchwork Access}(hj hhhNhNubah}(h]h ]h"]h$]h&]uh1hhj hhhhhKbubh)}(hXC All Media Maintainers who have been granted Patchwork access shall ensure that
`Patchwork `_
will reflect the current status, e.g. patches shall be delegated to the Media
Maintainer who is handling them and the patch status shall be updated according
to these rules:h](hOAll Media Maintainers who have been granted Patchwork access shall ensure that
}(hj. hhhNhNubj )}(hF`Patchwork `_h]h Patchwork}(hj6 hhhNhNubah}(h]h ]h"]h$]h&]name Patchworkj 7https://patchwork.linuxtv.org/project/linux-media/list/uh1j hj. ubj )}(h: h]h}(h]id5ah ]h"]h$] patchworkah&]refurijF uh1j j Khj. ubh
will reflect the current status, e.g. patches shall be delegated to the Media
Maintainer who is handling them and the patch status shall be updated according
to these rules:}(hj. hhhNhNubeh}(h]h ]h"]h$]h&]uh1hhhhKdhj hhubj! )}(hhh](j& )}(hc``Under Review``: Used if the patch requires a second opinion
or when it is part of a Pull Request;h]h)}(hc``Under Review``: Used if the patch requires a second opinion
or when it is part of a Pull Request;h](hliteral)}(h``Under Review``h]hUnder Review}(hjk hhhNhNubah}(h]h ]h"]h$]h&]uh1ji hje ubhS: Used if the patch requires a second opinion
or when it is part of a Pull Request;}(hje hhhNhNubeh}(h]h ]h"]h$]h&]uh1hhhhKjhja ubah}(h]h ]h"]h$]h&]uh1j% hj^ hhhhhNubj& )}(hQ``Superseded``: There is a newer version of the patch posted to the
mailing list.h]h)}(hQ``Superseded``: There is a newer version of the patch posted to the
mailing list.h](jj )}(h``Superseded``h]h
Superseded}(hj hhhNhNubah}(h]h ]h"]h$]h&]uh1ji hj ubhC: There is a newer version of the patch posted to the
mailing list.}(hj hhhNhNubeh}(h]h ]h"]h$]h&]uh1hhhhKlhj ubah}(h]h ]h"]h$]h&]uh1j% hj^ hhhhhNubj& )}(ha``Duplicated``: There was another patch doing the same thing from someone
else that was accepted.h]h)}(ha``Duplicated``: There was another patch doing the same thing from someone
else that was accepted.h](jj )}(h``Duplicated``h]h
Duplicated}(hj hhhNhNubah}(h]h ]h"]h$]h&]uh1ji hj ubhS: There was another patch doing the same thing from someone
else that was accepted.}(hj hhhNhNubeh}(h]h ]h"]h$]h&]uh1hhhhKnhj ubah}(h]h ]h"]h$]h&]uh1j% hj^ hhhhhNubj& )}(h``Not Applicable``: Use for patch series that are not merged at media.git
tree (e.g. drm, dmabuf, upstream merge, etc.) but were cross-posted to the
linux-media mailing list.h]h)}(h``Not Applicable``: Use for patch series that are not merged at media.git
tree (e.g. drm, dmabuf, upstream merge, etc.) but were cross-posted to the
linux-media mailing list.h](jj )}(h``Not Applicable``h]hNot Applicable}(hj hhhNhNubah}(h]h ]h"]h$]h&]uh1ji hj ubh: Use for patch series that are not merged at media.git
tree (e.g. drm, dmabuf, upstream merge, etc.) but were cross-posted to the
linux-media mailing list.}(hj hhhNhNubeh}(h]h ]h"]h$]h&]uh1hhhhKphj ubah}(h]h ]h"]h$]h&]uh1j% hj^ hhhhhNubj& )}(h``Accepted``: Once a patch is merged in the multi-committer tree. Only Media
Maintainers with commit rights are allowed to set this state.
h]h)}(h``Accepted``: Once a patch is merged in the multi-committer tree. Only Media
Maintainers with commit rights are allowed to set this state.h](jj )}(h``Accepted``h]hAccepted}(hj hhhNhNubah}(h]h ]h"]h$]h&]uh1ji hj ubh~: Once a patch is merged in the multi-committer tree. Only Media
Maintainers with commit rights are allowed to set this state.}(hj hhhNhNubeh}(h]h ]h"]h$]h&]uh1hhhhKshj ubah}(h]h ]h"]h$]h&]uh1j% hj^ hhhhhNubeh}(h]h ]h"]h$]h&]j j uh1j hhhKjhj hhubh)}(hX If Media Maintainers decide not to accept a patch, they should reply to the
patch authors by e‑mail, explaining why it is not accepted, and
update `Patchwork `_
accordingly with one of the following statuses:h](hIf Media Maintainers decide not to accept a patch, they should reply to the
patch authors by e‑mail, explaining why it is not accepted, and
update }(hj' hhhNhNubj )}(hF`Patchwork `_h]h Patchwork}(hj/ hhhNhNubah}(h]h ]h"]h$]h&]name Patchworkj 7https://patchwork.linuxtv.org/project/linux-media/list/uh1j hj' ubj )}(h: h]h}(h]id6ah ]h"]h$] patchworkah&]refurij? uh1j j Khj' ubh0
accordingly with one of the following statuses:}(hj' hhhNhNubeh}(h]h ]h"]h$]h&]uh1hhhhKvhj hhubj! )}(hhh](j& )}(h7``Changes Requested``: if a new revision was requested;h]h)}(hj\ h](jj )}(h``Changes Requested``h]hChanges Requested}(hja hhhNhNubah}(h]h ]h"]h$]h&]uh1ji hj^ ubh": if a new revision was requested;}(hj^ hhhNhNubeh}(h]h ]h"]h$]h&]uh1hhhhK{hjZ ubah}(h]h ]h"]h$]h&]uh1j% hjW hhhhhNubj& )}(h?``Rejected``: if the proposed change is not acceptable at all.
h]h)}(h>``Rejected``: if the proposed change is not acceptable at all.h](jj )}(h``Rejected``h]hRejected}(hj hhhNhNubah}(h]h ]h"]h$]h&]uh1ji hj ubh2: if the proposed change is not acceptable at all.}(hj hhhNhNubeh}(h]h ]h"]h$]h&]uh1hhhhK|hj ubah}(h]h ]h"]h$]h&]uh1j% hjW hhhhhNubeh}(h]h ]h"]h$]h&]j j uh1j hhhK{hj hhubhnote)}(hPatchwork supports a couple of clients to help semi-automate
status updates via its REST interface:
https://patchwork.readthedocs.io/en/latest/usage/clients/h](h)}(hcPatchwork supports a couple of clients to help semi-automate
status updates via its REST interface:h]hcPatchwork supports a couple of clients to help semi-automate
status updates via its REST interface:}(hj hhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhKhj ubh)}(h9https://patchwork.readthedocs.io/en/latest/usage/clients/h]j )}(hj h]h9https://patchwork.readthedocs.io/en/latest/usage/clients/}(hj hhhNhNubah}(h]h ]h"]h$]h&]refurij uh1j hj ubah}(h]h ]h"]h$]h&]uh1hhhhKhj ubeh}(h]h ]h"]h$]h&]uh1j hj hhhhhNubh)}(hFor patches that fall within their area of responsibility a Media Maintainer
also decides when those patches are ready for merging, and create Pull Requests
for the Media Subsystem Maintainers to merge.h]hFor patches that fall within their area of responsibility a Media Maintainer
also decides when those patches are ready for merging, and create Pull Requests
for the Media Subsystem Maintainers to merge.}(hj hhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhKhj hhubh)}(hThe most important aspect of becoming a Media Maintainer with Patchwork access
is that you have demonstrated an ability to give good code reviews. We value
your ability to deliver thorough, constructive code reviews.h]hThe most important aspect of becoming a Media Maintainer with Patchwork access
is that you have demonstrated an ability to give good code reviews. We value
your ability to deliver thorough, constructive code reviews.}(hj hhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhKhj hhubh)}(hX As such, potential maintainers must earn enough credibility and trust from the
Linux Media Community. To do that, developers shall be familiar with the open
source model and have been active in the Linux Kernel community for some time,
and, in particular, in the media subsystem.h]hX As such, potential maintainers must earn enough credibility and trust from the
Linux Media Community. To do that, developers shall be familiar with the open
source model and have been active in the Linux Kernel community for some time,
and, in particular, in the media subsystem.}(hj hhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhKhj hhubh)}(hVIn addition to actually making the code changes, you are basically
demonstrating your:h]hVIn addition to actually making the code changes, you are basically
demonstrating your:}(hj hhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhKhj hhubj! )}(hhh](j& )}(hcommitment to the project;h]h)}(hj h]hcommitment to the project;}(hj hhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhKhj ubah}(h]h ]h"]h$]h&]uh1j% hj hhhhhNubj& )}(h:ability to collaborate with the team and communicate well;h]h)}(hj1 h]h:ability to collaborate with the team and communicate well;}(hj3 hhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhKhj/ ubah}(h]h ]h"]h$]h&]uh1j% hj hhhhhNubj& )}(htunderstanding of how upstream and the Linux Media Community work
(policies, processes for testing, code review, ...)h]h)}(htunderstanding of how upstream and the Linux Media Community work
(policies, processes for testing, code review, ...)h]htunderstanding of how upstream and the Linux Media Community work
(policies, processes for testing, code review, ...)}(hjJ hhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhKhjF ubah}(h]h ]h"]h$]h&]uh1j% hj hhhhhNubj& )}(hreasonable knowledge about:
- the Kernel development process:
Documentation/process/index.rst
- the Media development profile:
Documentation/driver-api/media/maintainer-entry-profile.rst
h](h)}(hreasonable knowledge about:h]hreasonable knowledge about:}(hjb hhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhKhj^ ubj! )}(hhh](j& )}(h@the Kernel development process:
Documentation/process/index.rst
h]h)}(h?the Kernel development process:
Documentation/process/index.rsth]h?the Kernel development process:
Documentation/process/index.rst}(hjw hhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhKhjs ubah}(h]h ]h"]h$]h&]uh1j% hjp ubj& )}(h[the Media development profile:
Documentation/driver-api/media/maintainer-entry-profile.rst
h]h)}(hZthe Media development profile:
Documentation/driver-api/media/maintainer-entry-profile.rsth]hZthe Media development profile:
Documentation/driver-api/media/maintainer-entry-profile.rst}(hj hhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhKhj ubah}(h]h ]h"]h$]h&]uh1j% hjp ubeh}(h]h ]h"]h$]h&]j j uh1j hhhKhj^ ubeh}(h]h ]h"]h$]h&]uh1j% hj hhhNhNubj& )}(h:understanding of the projects' code base and coding style;h]h)}(hj h]h