From: Steve French <smfrench@gmail.com>
To: CIFS <linux-cifs@vger.kernel.org>
Subject: two "maintainerless" files
Date: Sat, 13 Aug 2022 17:27:25 -0500 [thread overview]
Message-ID: <CAH2r5mtrtLZSuSY3=kQfQ7i-Y_eAzTpxaRubJxA6gMCXYxWMaA@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 367 bytes --]
I noticed a report showing hundreds of files without a maintainer
listed, including two that relate to cifs.ko.
include/uapi/linux/cifs/cifs_netlink.h
include/uapi/linux/cifs/cifs_mount.h
One of them was written by Samuel for the witness protocol work.
We could simply add "include/uapi/linux/cifs" to the MAINTAINERS file.
See attached patch
--
Thanks,
Steve
[-- Attachment #2: 0001-cifs-missing-directory-in-MAINTAINERS-file.patch --]
[-- Type: text/x-patch, Size: 820 bytes --]
From 27a38528dce38e90fa47ae83023eddff534338ca Mon Sep 17 00:00:00 2001
From: Steve French <stfrench@microsoft.com>
Date: Sat, 13 Aug 2022 17:22:11 -0500
Subject: [PATCH] cifs: missing directory in MAINTAINERS file
The include/uapi/linux/cifs directory (not just fs/cifs and
fs/smbfs_common) should be included in cifs entry in the
MAINTAINERS file.
Signed-off-by: Steve French <stfrench@microsoft.com>
---
MAINTAINERS | 1 +
1 file changed, 1 insertion(+)
diff --git a/MAINTAINERS b/MAINTAINERS
index eb3d10fa3eed..1a3aa77413de 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -5068,6 +5068,7 @@ T: git git://git.samba.org/sfrench/cifs-2.6.git
F: Documentation/admin-guide/cifs/
F: fs/cifs/
F: fs/smbfs_common/
+F: include/uapi/linux/cifs
COMPACTPCI HOTPLUG CORE
M: Scott Murray <scott@spiteful.org>
--
2.34.1
reply other threads:[~2022-08-13 22:28 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAH2r5mtrtLZSuSY3=kQfQ7i-Y_eAzTpxaRubJxA6gMCXYxWMaA@mail.gmail.com' \
--to=smfrench@gmail.com \
--cc=linux-cifs@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.