summaryrefslogtreecommitdiff
path: root/scripts/generate_rust_analyzer.py
diff options
context:
space:
mode:
authorPaul Moore <paul@paul-moore.com>2025-03-05 01:10:48 +0300
committerPaul Moore <paul@paul-moore.com>2025-03-07 20:13:51 +0300
commitb51543e9fb39760453e2a8a55ebf0e79838ce4b4 (patch)
tree64ddd15e2f6a3012f241bf7d308e552b2b5c4bc8 /scripts/generate_rust_analyzer.py
parentab938b59e9de924de20ba4a8f768649573421204 (diff)
downloadlinux-b51543e9fb39760453e2a8a55ebf0e79838ce4b4.tar.xz
MAINTAINERS: add an explicit credentials entry
The lack of an explicit credential (kernel/cred.c) entry has caused confusion in the past among new, and not-so-new developers, about where to send credential patches for discussion and merging. Those patches that are sent can often rot on the mailing lists for months as there is no clear maintainer tasked with reviewing and merging patches. I'm volunteering for the cred maintainer role to try and reduce the confusion and help cred patches find their way up to Linus' tree. As there generally aren't a lot of cred patches I'll start with simply folding them into the LSM tree, but if this changes I'll setup a dedicated cred tree. Link: https://lore.kernel.org/all/20250304222304.214704-2-paul@paul-moore.com Signed-off-by: Paul Moore <paul@paul-moore.com>
Diffstat (limited to 'scripts/generate_rust_analyzer.py')
0 files changed, 0 insertions, 0 deletions