Re: [Ksummit-discuss] [PATCH v2 3/3] libnvdimm, MAINTAINERS: Maintainer Entry Profile
Jani Nikula <[email protected]>
| Newsgroups | org.linuxfoundation.lists.ksummit-discuss,dev.linux.lists.ksummit,dev.linux.lists.nvdimm,org.01.lists.linux-nvdimm,org.kernel.vger.bpf,org.kernel.vger.linux-kernel |
|---|---|
| Organization | Intel Finland Oy - BIC 0357606-4 - Westendinkatu 7, 02160 Espoo |
| Message-ID | <[email protected]> |
On Fri, 13 Sep 2019, Dan Carpenter <[email protected]> wrote: > And the documentation doesn't help. For example, I knew people's rules > about capitalizing the subject but I'd just forget. I say that if you > can't be bothered to add it to checkpatch then it means you don't really > care that strongly. It would be entirely possible to add the subsystem/driver specific checkpatch rules to MAINTAINERS entries or directory specific config files. As checkpatch options directly. For example --strict --max-line-length=100 --ignore=BIT_MACRO,SPLIT_STRING,LONG_LINE_STRING,BOOL_MEMBER or whatever. SMOP. ;) BR, Jani. -- Jani Nikula, Intel Open Source Graphics Center _______________________________________________ Ksummit-discuss mailing list [email protected] https://lists.linuxfoundation.org/mailman/listinfo/ksummit-discuss