147843401SDan WilliamsLIBNVDIMM Maintainer Entry Profile 247843401SDan Williams================================== 347843401SDan Williams 447843401SDan WilliamsOverview 547843401SDan Williams-------- 647843401SDan WilliamsThe libnvdimm subsystem manages persistent memory across multiple 747843401SDan Williamsarchitectures. The mailing list, is tracked by patchwork here: 847843401SDan Williamshttps://patchwork.kernel.org/project/linux-nvdimm/list/ 947843401SDan Williams...and that instance is configured to give feedback to submitters on 1047843401SDan Williamspatch acceptance and upstream merge. Patches are merged to either the 1147843401SDan Williams'libnvdimm-fixes', or 'libnvdimm-for-next' branch. Those branches are 1247843401SDan Williamsavailable here: 1347843401SDan Williamshttps://git.kernel.org/pub/scm/linux/kernel/git/nvdimm/nvdimm.git/ 1447843401SDan Williams 1547843401SDan WilliamsIn general patches can be submitted against the latest -rc, however if 1647843401SDan Williamsthe incoming code change is dependent on other pending changes then the 1747843401SDan Williamspatch should be based on the libnvdimm-for-next branch. However, since 1847843401SDan Williamspersistent memory sits at the intersection of storage and memory there 1947843401SDan Williamsare cases where patches are more suitable to be merged through a 2047843401SDan WilliamsFilesystem or the Memory Management tree. When in doubt copy the nvdimm 2147843401SDan Williamslist and the maintainers will help route. 2247843401SDan Williams 2347843401SDan WilliamsSubmissions will be exposed to the kbuild robot for compile regression 2447843401SDan Williamstesting. It helps to get a success notification from that infrastructure 2547843401SDan Williamsbefore submitting, but it is not required. 2647843401SDan Williams 2747843401SDan Williams 2847843401SDan WilliamsSubmit Checklist Addendum 2947843401SDan Williams------------------------- 3047843401SDan WilliamsThere are unit tests for the subsystem via the ndctl utility: 3147843401SDan Williamshttps://github.com/pmem/ndctl 3247843401SDan WilliamsThose tests need to be passed before the patches go upstream, but not 3347843401SDan Williamsnecessarily before initial posting. Contact the list if you need help 3447843401SDan Williamsgetting the test environment set up. 3547843401SDan Williams 3647843401SDan Williams### ACPI Device Specific Methods (_DSM) 3747843401SDan WilliamsBefore patches enabling for a new _DSM family will be considered it must 3847843401SDan Williamsbe assigned a format-interface-code from the NVDIMM Sub-team of the ACPI 3947843401SDan WilliamsSpecification Working Group. In general, the stance of the subsystem is 4047843401SDan Williamsto push back on the proliferation of NVDIMM command sets, do strongly 4147843401SDan Williamsconsider implementing support for an existing command set. See 4247843401SDan Williamsdrivers/acpi/nfit/nfit.h for the set of support command sets. 4347843401SDan Williams 4447843401SDan Williams 4547843401SDan WilliamsKey Cycle Dates 4647843401SDan Williams--------------- 4747843401SDan WilliamsNew submissions can be sent at any time, but if they intend to hit the 4847843401SDan Williamsnext merge window they should be sent before -rc4, and ideally 4947843401SDan Williamsstabilized in the libnvdimm-for-next branch by -rc6. Of course if a 5047843401SDan Williamspatch set requires more than 2 weeks of review -rc4 is already too late 5147843401SDan Williamsand some patches may require multiple development cycles to review. 5247843401SDan Williams 5347843401SDan Williams 5447843401SDan WilliamsReview Cadence 5547843401SDan Williams-------------- 5647843401SDan WilliamsIn general, please wait up to one week before pinging for feedback. A 5747843401SDan Williamsprivate mail reminder is preferred. Alternatively ask for other 5847843401SDan Williamsdevelopers that have Reviewed-by tags for libnvdimm changes to take a 5947843401SDan Williamslook and offer their opinion. 60