€•1IŒsphinx.addnodes”Œdocument”“”)”}”(Œ rawsource”Œ”Œchildren”]”(Œ translations”Œ LanguagesNode”“”)”}”(hhh]”(hŒ pending_xref”“”)”}”(hhh]”Œdocutils.nodes”ŒText”“”ŒChinese (Simplified)”…””}”(hhŒparent”hubaŒ attributes”}”(Œids”]”Œclasses”]”Œnames”]”Œdupnames”]”Œbackrefs”]”Œ refdomain”Œstd”Œreftype”Œdoc”Œ reftarget”Œ7/translations/zh_CN/maintainer/maintainer-entry-profile”Œmodname”NŒ classname”NŒ refexplicit”ˆuŒtagname”hhh ubh)”}”(hhh]”hŒChinese (Traditional)”…””}”(hhhh2ubah}”(h]”h ]”h"]”h$]”h&]”Œ refdomain”h)Œreftype”h+Œ reftarget”Œ7/translations/zh_TW/maintainer/maintainer-entry-profile”Œmodname”NŒ classname”NŒ refexplicit”ˆuh1hhh ubh)”}”(hhh]”hŒItalian”…””}”(hhhhFubah}”(h]”h ]”h"]”h$]”h&]”Œ refdomain”h)Œreftype”h+Œ reftarget”Œ7/translations/it_IT/maintainer/maintainer-entry-profile”Œmodname”NŒ classname”NŒ refexplicit”ˆuh1hhh ubh)”}”(hhh]”hŒJapanese”…””}”(hhhhZubah}”(h]”h ]”h"]”h$]”h&]”Œ refdomain”h)Œreftype”h+Œ reftarget”Œ7/translations/ja_JP/maintainer/maintainer-entry-profile”Œmodname”NŒ classname”NŒ refexplicit”ˆuh1hhh ubh)”}”(hhh]”hŒKorean”…””}”(hhhhnubah}”(h]”h ]”h"]”h$]”h&]”Œ refdomain”h)Œreftype”h+Œ reftarget”Œ7/translations/ko_KR/maintainer/maintainer-entry-profile”Œmodname”NŒ classname”NŒ refexplicit”ˆuh1hhh ubh)”}”(hhh]”hŒSpanish”…””}”(hhhh‚ubah}”(h]”h ]”h"]”h$]”h&]”Œ refdomain”h)Œreftype”h+Œ reftarget”Œ7/translations/sp_SP/maintainer/maintainer-entry-profile”Œmodname”NŒ classname”NŒ refexplicit”ˆuh1hhh ubeh}”(h]”h ]”h"]”h$]”h&]”Œcurrent_language”ŒEnglish”uh1h hhŒ _document”hŒsource”NŒline”NubhŒtarget”“”)”}”(hŒ.. _maintainerentryprofile:”h]”h}”(h]”h ]”h"]”h$]”h&]”Œrefid”Œmaintainerentryprofile”uh1h¡h KhhhžhhŸŒQ/var/lib/git/docbuild/linux/Documentation/maintainer/maintainer-entry-profile.rst”ubhŒsection”“”)”}”(hhh]”(hŒtitle”“”)”}”(hŒMaintainer Entry Profile”h]”hŒMaintainer Entry Profile”…””}”(hh¹hh·hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hµhh²hžhhŸh¯h KubhŒ paragraph”“”)”}”(hX¥The Maintainer Entry Profile supplements the top-level process documents (submitting-patches, submitting drivers...) with subsystem/device-driver-local customs as well as details about the patch submission life-cycle. A contributor uses this document to level set their expectations and avoid common mistakes; maintainers may use these profiles to look across subsystems for opportunities to converge on common practices.”h]”hX¥The Maintainer Entry Profile supplements the top-level process documents (submitting-patches, submitting drivers...) with subsystem/device-driver-local customs as well as details about the patch submission life-cycle. A contributor uses this document to level set their expectations and avoid common mistakes; maintainers may use these profiles to look across subsystems for opportunities to converge on common practices.”…””}”(hhÉhhÇhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÅhŸh¯h Khh²hžhubh±)”}”(hhh]”(h¶)”}”(hŒOverview”h]”hŒOverview”…””}”(hhÚhhØhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hµhhÕhžhhŸh¯h KubhÆ)”}”(hŒâProvide an introduction to how the subsystem operates. While MAINTAINERS tells the contributor where to send patches for which files, it does not convey other subsystem-local infrastructure and mechanisms that aid development.”h]”hŒâProvide an introduction to how the subsystem operates. While MAINTAINERS tells the contributor where to send patches for which files, it does not convey other subsystem-local infrastructure and mechanisms that aid development.”…””}”(hhèhhæhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÅhŸh¯h KhhÕhžhubhÆ)”}”(hŒExample questions to consider:”h]”hŒExample questions to consider:”…””}”(hhöhhôhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÅhŸh¯h KhhÕhžhubhŒ bullet_list”“”)”}”(hhh]”(hŒ list_item”“”)”}”(hŒWAre there notifications when patches are applied to the local tree, or merged upstream?”h]”hÆ)”}”(hŒWAre there notifications when patches are applied to the local tree, or merged upstream?”h]”hŒWAre there notifications when patches are applied to the local tree, or merged upstream?”…””}”(hjhj hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÅhŸh¯h Khj ubah}”(h]”h ]”h"]”h$]”h&]”uh1jhjhžhhŸh¯h Nubj)”}”(hŒSDoes the subsystem have a patchwork instance? Are patchwork state changes notified?”h]”hÆ)”}”(hŒSDoes the subsystem have a patchwork instance? Are patchwork state changes notified?”h]”hŒSDoes the subsystem have a patchwork instance? Are patchwork state changes notified?”…””}”(hj'hj%hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÅhŸh¯h Khj!ubah}”(h]”h ]”h"]”h$]”h&]”uh1jhjhžhhŸh¯h Nubj)”}”(hŒ~Any bots or CI infrastructure that watches the list, or automated testing feedback that the subsystem uses to gate acceptance?”h]”hÆ)”}”(hŒ~Any bots or CI infrastructure that watches the list, or automated testing feedback that the subsystem uses to gate acceptance?”h]”hŒ~Any bots or CI infrastructure that watches the list, or automated testing feedback that the subsystem uses to gate acceptance?”…””}”(hj?hj=hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÅhŸh¯h Khj9ubah}”(h]”h ]”h"]”h$]”h&]”uh1jhjhžhhŸh¯h Nubj)”}”(hŒ(Git branches that are pulled into -next?”h]”hÆ)”}”(hjSh]”hŒ(Git branches that are pulled into -next?”…””}”(hjShjUhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÅhŸh¯h KhjQubah}”(h]”h ]”h"]”h$]”h&]”uh1jhjhžhhŸh¯h Nubj)”}”(hŒ/What branch should contributors submit against?”h]”hÆ)”}”(hjjh]”hŒ/What branch should contributors submit against?”…””}”(hjjhjlhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÅhŸh¯h Khjhubah}”(h]”h ]”h"]”h$]”h&]”uh1jhjhžhhŸh¯h Nubj)”}”(hŒðLinks to any other Maintainer Entry Profiles? For example a device-driver may point to an entry for its parent subsystem. This makes the contributor aware of obligations a maintainer may have for other maintainers in the submission chain. ”h]”hÆ)”}”(hŒîLinks to any other Maintainer Entry Profiles? For example a device-driver may point to an entry for its parent subsystem. This makes the contributor aware of obligations a maintainer may have for other maintainers in the submission chain.”h]”hŒîLinks to any other Maintainer Entry Profiles? For example a device-driver may point to an entry for its parent subsystem. This makes the contributor aware of obligations a maintainer may have for other maintainers in the submission chain.”…””}”(hj…hjƒhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÅhŸh¯h K hjubah}”(h]”h ]”h"]”h$]”h&]”uh1jhjhžhhŸh¯h Nubeh}”(h]”h ]”h"]”h$]”h&]”Œbullet”Œ-”uh1jhŸh¯h KhhÕhžhubeh}”(h]”Œoverview”ah ]”h"]”Œoverview”ah$]”h&]”uh1h°hh²hžhhŸh¯h Kubh±)”}”(hhh]”(h¶)”}”(hŒSubmit Checklist Addendum”h]”hŒSubmit Checklist Addendum”…””}”(hj¬hjªhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hµhj§hžhhŸh¯h K'ubhÆ)”}”(hŒôList mandatory and advisory criteria, beyond the common "submit-checklist", for a patch to be considered healthy enough for maintainer attention. For example: "pass checkpatch.pl with no errors, or warning. Pass the unit test detailed at $URI".”h]”hŒüList mandatory and advisory criteria, beyond the common “submit-checklistâ€, for a patch to be considered healthy enough for maintainer attention. For example: “pass checkpatch.pl with no errors, or warning. Pass the unit test detailed at $URIâ€.”…””}”(hjºhj¸hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÅhŸh¯h K(hj§hžhubhÆ)”}”(hŒåThe Submit Checklist Addendum can also include details about the status of related hardware specifications. For example, does the subsystem require published specifications at a certain revision before patches will be considered.”h]”hŒåThe Submit Checklist Addendum can also include details about the status of related hardware specifications. For example, does the subsystem require published specifications at a certain revision before patches will be considered.”…””}”(hjÈhjÆhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÅhŸh¯h K-hj§hžhubeh}”(h]”Œsubmit-checklist-addendum”ah ]”h"]”Œsubmit checklist addendum”ah$]”h&]”uh1h°hh²hžhhŸh¯h K'ubh±)”}”(hhh]”(h¶)”}”(hŒKey Cycle Dates”h]”hŒKey Cycle Dates”…””}”(hjáhjßhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hµhjÜhžhhŸh¯h K4ubhÆ)”}”(hXÎOne of the common misunderstandings of submitters is that patches can be sent at any time before the merge window closes and can still be considered for the next -rc1. The reality is that most patches need to be settled in soaking in linux-next in advance of the merge window opening. Clarify for the submitter the key dates (in terms of -rc release week) that patches might be considered for merging and when patches need to wait for the next -rc. At a minimum:”h]”hXÎOne of the common misunderstandings of submitters is that patches can be sent at any time before the merge window closes and can still be considered for the next -rc1. The reality is that most patches need to be settled in soaking in linux-next in advance of the merge window opening. Clarify for the submitter the key dates (in terms of -rc release week) that patches might be considered for merging and when patches need to wait for the next -rc. At a minimum:”…””}”(hjïhjíhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÅhŸh¯h K5hjÜhžhubj)”}”(hhh]”(j)”}”(hXéLast -rc for new feature submissions: New feature submissions targeting the next merge window should have their first posting for consideration before this point. Patches that are submitted after this point should be clear that they are targeting the NEXT+1 merge window, or should come with sufficient justification why they should be considered on an expedited schedule. A general guideline is to set expectation with contributors that new feature submissions should appear before -rc5. ”h]”hÆ)”}”(hXèLast -rc for new feature submissions: New feature submissions targeting the next merge window should have their first posting for consideration before this point. Patches that are submitted after this point should be clear that they are targeting the NEXT+1 merge window, or should come with sufficient justification why they should be considered on an expedited schedule. A general guideline is to set expectation with contributors that new feature submissions should appear before -rc5.”h]”hXèLast -rc for new feature submissions: New feature submissions targeting the next merge window should have their first posting for consideration before this point. Patches that are submitted after this point should be clear that they are targeting the NEXT+1 merge window, or should come with sufficient justification why they should be considered on an expedited schedule. A general guideline is to set expectation with contributors that new feature submissions should appear before -rc5.”…””}”(hjhjhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÅhŸh¯h K=hjþubah}”(h]”h ]”h"]”h$]”h&]”uh1jhjûhžhhŸh¯h Nubj)”}”(hX…Last -rc to merge features: Deadline for merge decisions Indicate to contributors the point at which an as yet un-applied patch set will need to wait for the NEXT+1 merge window. Of course there is no obligation to ever accept any given patchset, but if the review has not concluded by this point the expectation is the contributor should wait and resubmit for the following merge window. ”h]”hÆ)”}”(hX„Last -rc to merge features: Deadline for merge decisions Indicate to contributors the point at which an as yet un-applied patch set will need to wait for the NEXT+1 merge window. Of course there is no obligation to ever accept any given patchset, but if the review has not concluded by this point the expectation is the contributor should wait and resubmit for the following merge window.”h]”hX„Last -rc to merge features: Deadline for merge decisions Indicate to contributors the point at which an as yet un-applied patch set will need to wait for the NEXT+1 merge window. Of course there is no obligation to ever accept any given patchset, but if the review has not concluded by this point the expectation is the contributor should wait and resubmit for the following merge window.”…””}”(hjhjhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÅhŸh¯h KFhjubah}”(h]”h ]”h"]”h$]”h&]”uh1jhjûhžhhŸh¯h Nubeh}”(h]”h ]”h"]”h$]”h&]”jjžuh1jhŸh¯h K=hjÜhžhubhÆ)”}”(hŒ Optional:”h]”hŒ Optional:”…””}”(hj6hj4hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÅhŸh¯h KMhjÜhžhubj)”}”(hhh]”j)”}”(hŒ…First -rc at which the development baseline branch, listed in the overview section, should be considered ready for new submissions. ”h]”hÆ)”}”(hŒƒFirst -rc at which the development baseline branch, listed in the overview section, should be considered ready for new submissions.”h]”hŒƒFirst -rc at which the development baseline branch, listed in the overview section, should be considered ready for new submissions.”…””}”(hjKhjIhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÅhŸh¯h KOhjEubah}”(h]”h ]”h"]”h$]”h&]”uh1jhjBhžhhŸh¯h Nubah}”(h]”h ]”h"]”h$]”h&]”jjžuh1jhŸh¯h KOhjÜhžhubeh}”(h]”Œkey-cycle-dates”ah ]”h"]”Œkey cycle dates”ah$]”h&]”uh1h°hh²hžhhŸh¯h K4ubh±)”}”(hhh]”(h¶)”}”(hŒReview Cadence”h]”hŒReview Cadence”…””}”(hjphjnhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hµhjkhžhhŸh¯h KTubhÆ)”}”(hXÊOne of the largest sources of contributor angst is how soon to ping after a patchset has been posted without receiving any feedback. In addition to specifying how long to wait before a resubmission this section can also indicate a preferred style of update like, resend the full series, or privately send a reminder email. This section might also list how review works for this code area and methods to get feedback that are not directly from the maintainer.”h]”hXÊOne of the largest sources of contributor angst is how soon to ping after a patchset has been posted without receiving any feedback. In addition to specifying how long to wait before a resubmission this section can also indicate a preferred style of update like, resend the full series, or privately send a reminder email. This section might also list how review works for this code area and methods to get feedback that are not directly from the maintainer.”…””}”(hj~hj|hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÅhŸh¯h KUhjkhžhubeh}”(h]”Œreview-cadence”ah ]”h"]”Œreview cadence”ah$]”h&]”uh1h°hh²hžhhŸh¯h KTubh±)”}”(hhh]”(h¶)”}”(hŒExisting profiles”h]”hŒExisting profiles”…””}”(hj—hj•hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hµhj’hžhhŸh¯h K^ubhÆ)”}”(hŒxFor now, existing maintainer profiles are listed here; we will likely want to do something different in the near future.”h]”hŒxFor now, existing maintainer profiles are listed here; we will likely want to do something different in the near future.”…””}”(hj¥hj£hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÅhŸh¯h K`hj’hžhubhŒcompound”“”)”}”(hhh]”hŒtoctree”“”)”}”(hhh]”h}”(h]”h ]”h"]”h$]”h&]”hŒ#maintainer/maintainer-entry-profile”Œentries”]”(NŒdoc-guide/maintainer-profile”†”NŒnvdimm/maintainer-entry-profile”†”NŒarch/riscv/patch-acceptance”†”NŒprocess/maintainer-soc”†”NŒ process/maintainer-soc-clean-dts”†”NŒ)driver-api/media/maintainer-entry-profile”†”NŒprocess/maintainer-netdev”†”NŒ5driver-api/vfio-pci-device-specific-driver-acceptance”†”NŒnvme/feature-and-quirk-policy”†”NŒ,filesystems/xfs/xfs-maintainer-entry-profile”†”eŒ includefiles”]”(jÄjÆjÈjÊjÌjÎjÐjÒjÔjÖeŒmaxdepth”KŒcaption”NŒglob”‰Œhidden”‰Œ includehidden”‰Œnumbered”KŒ titlesonly”‰Œ rawentries”]”uh1j¶hŸh¯h Kchj³ubah}”(h]”h ]”Œtoctree-wrapper”ah"]”h$]”h&]”uh1j±hj’hžhhŸh¯h Nubeh}”(h]”Œexisting-profiles”ah ]”h"]”Œexisting profiles”ah$]”h&]”uh1h°hh²hžhhŸh¯h K^ubeh}”(h]”(Œmaintainer-entry-profile”h®eh ]”h"]”(Œmaintainer entry profile”Œmaintainerentryprofile”eh$]”h&]”uh1h°hhhžhhŸh¯h KŒexpect_referenced_by_name”}”jøh£sŒexpect_referenced_by_id”}”h®h£subeh}”(h]”h ]”h"]”h$]”h&]”Œsource”h¯uh1hŒcurrent_source”NŒ current_line”NŒsettings”Œdocutils.frontend”ŒValues”“”)”}”(hµNŒ generator”NŒ datestamp”NŒ source_link”NŒ source_url”NŒ toc_backlinks”Œentry”Œfootnote_backlinks”KŒ sectnum_xform”KŒstrip_comments”NŒstrip_elements_with_classes”NŒ strip_classes”NŒ report_level”KŒ halt_level”KŒexit_status_level”KŒdebug”NŒwarning_stream”NŒ traceback”ˆŒinput_encoding”Œ utf-8-sig”Œinput_encoding_error_handler”Œstrict”Œoutput_encoding”Œutf-8”Œoutput_encoding_error_handler”j"Œerror_encoding”ŒUTF-8”Œerror_encoding_error_handler”Œbackslashreplace”Œ language_code”Œen”Œrecord_dependencies”NŒconfig”NŒ id_prefix”hŒauto_id_prefix”Œid”Œ dump_settings”NŒdump_internals”NŒdump_transforms”NŒdump_pseudo_xml”NŒexpose_internals”NŒstrict_visitor”NŒ_disable_config”NŒ_source”h¯Œ _destination”NŒ _config_files”]”Œ7/var/lib/git/docbuild/linux/Documentation/docutils.conf”aŒpep_references”NŒ pep_base_url”Œhttps://peps.python.org/”Œpep_file_url_template”Œpep-%04d”Œrfc_references”NŒ rfc_base_url”Œ&https://datatracker.ietf.org/doc/html/”Œ tab_width”KŒtrim_footnote_reference_space”‰Œfile_insertion_enabled”ˆŒ raw_enabled”KŒline_length_limit”M'Œsyntax_highlight”Œlong”Œ smart_quotes”ˆŒsmartquotes_locales”]”Œcharacter_level_inline_markup”‰Œdoctitle_xform”‰Œ docinfo_xform”KŒsectsubtitle_xform”‰Œ image_loading”Œlink”Œembed_stylesheet”‰Œcloak_email_addresses”ˆŒsection_self_link”‰Œ embed_images”‰Œenv”NubŒreporter”NŒindirect_targets”]”Œsubstitution_defs”}”Œsubstitution_names”}”Œrefnames”}”Œrefids”}”h®]”h£asŒnameids”}”(jøh®j÷jôj¤j¡jÙjÖjhjejjŒjïjìuŒ nametypes”}”(jøˆj÷Nj¤NjÙNjhNjNjïNuh}”(h®h²jôh²j¡hÕjÖj§jejÜjŒjkjìj’uŒ footnote_refs”}”Œ citation_refs”}”Œ autofootnotes”]”Œautofootnote_refs”]”Œsymbol_footnotes”]”Œsymbol_footnote_refs”]”Œ footnotes”]”Œ citations”]”Œautofootnote_start”KŒsymbol_footnote_start”KŒ id_counter”Œ collections”ŒCounter”“”}”…”R”Œparse_messages”]”Œtransform_messages”]”hŒsystem_message”“”)”}”(hhh]”hÆ)”}”(hhh]”hŒ