From: Bagas Sanjaya <bagasdotme@gmail.com>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Filesystems Development <linux-fsdevel@vger.kernel.org>,
Linux KVM <kvm@vger.kernel.org>
Cc: Alexander Viro <viro@zeniv.linux.org.uk>,
Christian Brauner <brauner@kernel.org>,
Paolo Bonzini <pbonzini@redhat.com>,
Bagas Sanjaya <bagasdotme@gmail.com>,
Stephen Rothwell <sfr@canb.auug.org.au>
Subject: [PATCH] fs: anon-inode: Prepend blank line separator to anon_inode_create_getfile() reasons list
Date: Tue, 14 Nov 2023 16:12:43 +0700 [thread overview]
Message-ID: <20231114091243.32789-1-bagasdotme@gmail.com> (raw)
Stephen Rothwell reported htmldocs warning when merging kvm tree:
Documentation/filesystems/api-summary:74: fs/anon_inodes.c:167: ERROR: Unexpected indentation.
Documentation/filesystems/api-summary:74: fs/anon_inodes.c:168: WARNING: Block quote ends without a blank line; unexpected unindent.
Fix them by prepending blank line separator to reasons list of
anon_inode_create_getfile() to render the list with correct items.
Fixes: e4c866e72563ed ("fs: Rename anon_inode_getfile_secure() and anon_inode_getfd_secure()")
Reported-by: Stephen Rothwell <sfr@canb.auug.org.au>
Closes: https://lore.kernel.org/linux-next/20231114141326.38a3dcd4@canb.auug.org.au/
Signed-off-by: Bagas Sanjaya <bagasdotme@gmail.com>
---
fs/anon_inodes.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/fs/anon_inodes.c b/fs/anon_inodes.c
index e02f4e2e2ecede..c9c02fc3bd0176 100644
--- a/fs/anon_inodes.c
+++ b/fs/anon_inodes.c
@@ -163,6 +163,7 @@ EXPORT_SYMBOL_GPL(anon_inode_getfile);
*
* Create a new anonymous inode and file pair. This can be done for two
* reasons:
+ *
* - for the inode to have its own security context, so that LSMs can enforce
* policy on the inode's creation;
* - if the caller needs a unique inode, for example in order to customize
base-commit: de7a3ded67802c419736e63f939d58fe7efcc9bd
--
An old man doll... just what I always wanted! - Clara
reply other threads:[~2023-11-14 9:12 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=20231114091243.32789-1-bagasdotme@gmail.com \
--to=bagasdotme@gmail.com \
--cc=brauner@kernel.org \
--cc=kvm@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=sfr@canb.auug.org.au \
--cc=viro@zeniv.linux.org.uk \
/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;
as well as URLs for NNTP newsgroup(s).