From: Christian Brauner <brauner@kernel.org>
To: linux-kernel@vger.kernel.org, Randy Dunlap <rdunlap@infradead.org>
Cc: Christian Brauner <brauner@kernel.org>,
"Matthew Wilcox (Oracle)" <willy@infradead.org>,
Alexander Viro <viro@zeniv.linux.org.uk>, Jan Kara <jack@suse.cz>,
linux-fsdevel@vger.kernel.org,
Namjae Jeon <linkinjeon@kernel.org>,
Dave Chinner <david@fromorbit.com>,
Anton Altaparmakov <anton@tuxera.com>,
Jonathan Corbet <corbet@lwn.net>,
linux-doc@vger.kernel.org
Subject: Re: [PATCH -next] fs: remove NTFS classic from docum. index
Date: Wed, 24 Jan 2024 12:12:09 +0100 [thread overview]
Message-ID: <20240124-jemals-bauarbeiten-01fad2b4e889@brauner> (raw)
In-Reply-To: <20240124011424.731-1-rdunlap@infradead.org>
On Tue, 23 Jan 2024 17:14:24 -0800, Randy Dunlap wrote:
> With the remove of the NTFS classic filesystem, also remove its
> documentation entry from the filesystems index to prevent a
> kernel-doc warning:
>
> Documentation/filesystems/index.rst:63: WARNING: toctree contains reference to nonexisting document 'filesystems/ntfs'
>
>
> [...]
Applied to the vfs.fs branch of the vfs/vfs.git tree.
Patches in the vfs.fs branch should appear in linux-next soon.
Please report any outstanding bugs that were missed during review in a
new review to the original patch series allowing us to drop it.
It's encouraged to provide Acked-bys and Reviewed-bys even though the
patch has now been applied. If possible patch trailers will be updated.
Note that commit hashes shown below are subject to change due to rebase,
trailer updates or similar. If in doubt, please check the listed branch.
tree: https://git.kernel.org/pub/scm/linux/kernel/git/vfs/vfs.git
branch: vfs.fs
[1/1] fs: remove NTFS classic from docum. index
https://git.kernel.org/vfs/vfs/c/06b8db3a7dde
prev parent reply other threads:[~2024-01-24 11:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-24 1:14 [PATCH -next] fs: remove NTFS classic from docum. index Randy Dunlap
2024-01-24 11:12 ` Christian Brauner [this message]
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=20240124-jemals-bauarbeiten-01fad2b4e889@brauner \
--to=brauner@kernel.org \
--cc=anton@tuxera.com \
--cc=corbet@lwn.net \
--cc=david@fromorbit.com \
--cc=jack@suse.cz \
--cc=linkinjeon@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rdunlap@infradead.org \
--cc=viro@zeniv.linux.org.uk \
--cc=willy@infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox