From: "Theodore Y. Ts'o" <tytso@mit.edu>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: Linux FS Devel <linux-fsdevel@vger.kernel.org>,
linux-ext4@vger.kernel.org, Jan Kara <jack@suse.com>
Subject: Re: [PATCH] jbd2: fix kernel-doc notation warning
Date: Sun, 15 Dec 2019 21:45:55 -0500 [thread overview]
Message-ID: <20191216024555.GC11512@mit.edu> (raw)
In-Reply-To: <53e3ce27-ceae-560d-0fd4-f95728a33e12@infradead.org>
On Sun, Dec 08, 2019 at 08:31:32PM -0800, Randy Dunlap wrote:
> From: Randy Dunlap <rdunlap@infradead.org>
>
> Fix kernel-doc warning by inserting a beginning '*' character
> for the kernel-doc line.
>
> ../include/linux/jbd2.h:461: warning: bad line: journal. These are dirty buffers and revoke descriptor blocks.
>
> Signed-off-by: Randy Dunlap <rdunlap@infradead.org>
Applied, thanks.
- Ted
prev parent reply other threads:[~2019-12-16 2:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-09 4:31 [PATCH] jbd2: fix kernel-doc notation warning Randy Dunlap
2019-12-10 9:16 ` Jan Kara
2019-12-16 2:45 ` Theodore Y. Ts'o [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=20191216024555.GC11512@mit.edu \
--to=tytso@mit.edu \
--cc=jack@suse.com \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=rdunlap@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;
as well as URLs for NNTP newsgroup(s).