From: Christian Brauner <brauner@kernel.org>
To: Vegard Nossum <vegard.nossum@oracle.com>
Cc: Christian Brauner <brauner@kernel.org>,
linux-fsdevel@vger.kernel.org, linux-doc@vger.kernel.org,
Amir Goldstein <amir73il@gmail.com>,
Josef Bacik <josef@toxicpanda.com>,
Alexander Viro <viro@zeniv.linux.org.uk>, Jan Kara <jack@suse.cz>
Subject: Re: [PATCH -next] fs: fix __sb_write_started() kerneldoc formatting
Date: Thu, 28 Dec 2023 11:41:15 +0100 [thread overview]
Message-ID: <20231228-behutsam-mut-904e0a059471@brauner> (raw)
In-Reply-To: <20231228100608.3123987-1-vegard.nossum@oracle.com>
On Thu, 28 Dec 2023 11:06:08 +0100, Vegard Nossum wrote:
> When running 'make htmldocs', I see the following warning:
>
> Documentation/filesystems/api-summary:14: ./include/linux/fs.h:1659: WARNING: Definition list ends without a blank line; unexpected unindent.
>
> The official guidance [1] seems to be to use lists, which will prevent
> both the "unexpected unindent" warning as well as ensure that each line
> is formatted on a separate line in the HTML output instead of being
> all considered a single paragraph.
>
> [...]
Applied to the vfs.rw branch of the vfs/vfs.git tree.
Patches in the vfs.rw 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.rw
[1/1] fs: fix __sb_write_started() kerneldoc formatting
https://git.kernel.org/vfs/vfs/c/c39e2ae3943d
next prev parent reply other threads:[~2023-12-28 10:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-28 10:06 [PATCH -next] fs: fix __sb_write_started() kerneldoc formatting Vegard Nossum
2023-12-28 10:41 ` Christian Brauner [this message]
2024-01-02 12:28 ` Jan Kara
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=20231228-behutsam-mut-904e0a059471@brauner \
--to=brauner@kernel.org \
--cc=amir73il@gmail.com \
--cc=jack@suse.cz \
--cc=josef@toxicpanda.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=vegard.nossum@oracle.com \
--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