linux-next: build warning after merge of the kvm tree
Subsystems (3)
Hi all,
After merging the kvm tree, today's linux-next build (htmldocs) produced this warning:
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.
Introduced by commit
e4c866e72563 ("fs: Rename anon_inode_getfile_secure() and anon_inode_getfd_secure()")
Signature · 2 lines
Cheers, Stephen Rothwell
Paolo Bonzini
maintainerQuoted 7 lines · Stephen Rothwell
Hi all,
After merging the kvm tree, today's linux-next build (htmldocs) produced this warning:
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.
This reproduces with the version of sphinx in Documentation/sphinx/requirements.txt. The fix is simply this, for which I will send a patch:
fs/anon_inodes.c +4 -0
@@ -163,8 +163,10 @@ 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 * the size returned by fstat() *
@@ -250,8 +252,10 @@ EXPORT_SYMBOL_GPL(anon_inode_getfd);* * 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 * the size returned by fstat() *
Paolo