From: Bagas Sanjaya <bagasdotme@gmail.com>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Documentation <linux-doc@vger.kernel.org>,
Linux bcachefs <linux-bcachefs@vger.kernel.org>
Cc: Kent Overstreet <kent.overstreet@linux.dev>,
Brian Foster <bfoster@redhat.com>,
Jonathan Corbet <corbet@lwn.net>,
"Darrick J. Wong" <djwong@kernel.org>,
Bagas Sanjaya <bagasdotme@gmail.com>,
Chandan Babu R <chandanbabu@kernel.org>,
Namjae Jeon <linkinjeon@kernel.org>,
Steve French <stfrench@microsoft.com>,
Randy Dunlap <rdunlap@infradead.org>
Subject: [PATCH 2/2] MAINTAINERS: Add entry for bcachefs documentation
Date: Fri, 5 Apr 2024 14:23:19 +0700 [thread overview]
Message-ID: <20240405072320.23416-3-bagasdotme@gmail.com> (raw)
In-Reply-To: <20240405072320.23416-1-bagasdotme@gmail.com>
Now that bcachefs docs exist in Documentation/filesystems/bcachefs/,
cover it in MAINTAINERS entry for the filesystem.
Signed-off-by: Bagas Sanjaya <bagasdotme@gmail.com>
---
MAINTAINERS | 1 +
1 file changed, 1 insertion(+)
diff --git a/MAINTAINERS b/MAINTAINERS
index 7c121493f43d01..c0091a206fd206 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -3573,6 +3573,7 @@ S: Supported
C: irc://irc.oftc.net/bcache
T: git https://evilpiepirate.org/git/bcachefs.git
F: fs/bcachefs/
+F: Documentation/filesystems/bcachefs/
BDISP ST MEDIA DRIVER
M: Fabien Dessenne <fabien.dessenne@foss.st.com>
--
An old man doll... just what I always wanted! - Clara
next prev parent reply other threads:[~2024-04-05 7:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-05 7:23 [PATCH 0/2] toctree fix for bcachefs docs Bagas Sanjaya
2024-04-05 7:23 ` [PATCH 1/2] Documentation: filesystems: Add bcachefs toctree Bagas Sanjaya
2024-04-05 7:23 ` Bagas Sanjaya [this message]
2024-04-06 5:25 ` [PATCH 0/2] toctree fix for bcachefs docs Kent Overstreet
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=20240405072320.23416-3-bagasdotme@gmail.com \
--to=bagasdotme@gmail.com \
--cc=bfoster@redhat.com \
--cc=chandanbabu@kernel.org \
--cc=corbet@lwn.net \
--cc=djwong@kernel.org \
--cc=kent.overstreet@linux.dev \
--cc=linkinjeon@kernel.org \
--cc=linux-bcachefs@vger.kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rdunlap@infradead.org \
--cc=stfrench@microsoft.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox