MAINTAINERS improv suggestion
Subsystems (2)
Hi Lukas and everyone in linux-doc ML,
Thanks for your work on doc cleanup. However, there's still one thing left:MAINTAINERS. The patch submitters tips, IMO, need some work.
Here's my notes:
* Nowadays most drivers (especially on embedded architectures like Arm) were initially developed out-of-tree, then follows mainline inclusion process But the second item read "Try to release a few ALPHA test versions to the net. Announce them onto the kernel channel and await results". These drivers were submitted not as ALPHA-grade, but near-production grade.
* The fifth item mentioned using diff -u to generate patches, however since 9f364b605f34e1 ("submitting-patches.rst: presume git will be used"), the documentation elsewhere assumed git would be used.
Thanks.
Signature · 1 line
An old man doll... just what I always wanted! - Clara
Quoted 6 lines · Bagas Sanjaya
Hi Lukas and everyone in linux-doc ML,
Thanks for your work on doc cleanup. However, there's still one thing left:
MAINTAINERS. The patch submitters tips, IMO, need some work.
You are welcome.
Quoted 8 lines
Here's my notes:
* Nowadays most drivers (especially on embedded architectures like Arm) were initially developed out-of-tree, then follows mainline inclusion process But the second item read "Try to release a few ALPHA test versions to the net. Announce them onto the kernel channel and await results". These drivers were submitted not as ALPHA-grade, but near-production grade.
Quoted 5 lines
* The fifth item mentioned using
diff -uto generate patches, however since9f364b605f34e1("submitting-patches.rst: presume git will be used"), the documentation elsewhere assumed git would be used.Thanks.
Thanks for the notes. I will take them into consideration.
Feel free to propose a patch, though.
Eventually, we might decide to delete the complete list of suggestions in MAINTAINERS at some point. But for the time being, making the suggestions a bit better might be worth a patch.
Lukas