From: Jan Kara <jack@suse.cz>
To: Luis de Bethencourt <luisbg@osg.samsung.com>
Cc: linux-kernel@vger.kernel.org, tytso@mit.edu, jack@suse.com,
linux-ext4@vger.kernel.org
Subject: Re: [PATCH] jbd2: remove excess descriptions for handle_s
Date: Mon, 21 Mar 2016 09:41:30 +0100 [thread overview]
Message-ID: <20160321084130.GA30819@quack.suse.cz> (raw)
In-Reply-To: <1458407163-10849-1-git-send-email-luisbg@osg.samsung.com>
On Sat 19-03-16 17:06:03, Luis de Bethencourt wrote:
> Commit bf6993276f74 ("jbd2: Use tracepoints for history file")
> removed the members j_history, j_history_max and j_history_cur from struct
> handle_s but the descriptions stayed lingering. Removing them.
>
> Signed-off-by: Luis de Bethencourt <luisbg@osg.samsung.com>
Looks good. You can add:
Reviewed-by: Jan Kara <jack@suse.cz>
Honza
> ---
> Hi,
>
> Noticed this issue when running make htmldocs.
>
> It gives the following warnings:
> .//include/linux/jbd2.h:1033: warning: Excess struct/union/enum/typedef member 'j_history' description in 'journal_s'
> .//include/linux/jbd2.h:1033: warning: Excess struct/union/enum/typedef member 'j_history_max' description in 'journal_s'
> .//include/linux/jbd2.h:1033: warning: Excess struct/union/enum/typedef member 'j_history_cur' description in 'journal_s'
>
> Thanks,
> Luis
>
> include/linux/jbd2.h | 3 ---
> 1 file changed, 3 deletions(-)
>
> diff --git a/include/linux/jbd2.h b/include/linux/jbd2.h
> index fd1083c..401792d 100644
> --- a/include/linux/jbd2.h
> +++ b/include/linux/jbd2.h
> @@ -781,9 +781,6 @@ jbd2_time_diff(unsigned long start, unsigned long end)
> * @j_wbufsize: maximum number of buffer_heads allowed in j_wbuf, the
> * number that will fit in j_blocksize
> * @j_last_sync_writer: most recent pid which did a synchronous write
> - * @j_history: Buffer storing the transactions statistics history
> - * @j_history_max: Maximum number of transactions in the statistics history
> - * @j_history_cur: Current number of transactions in the statistics history
> * @j_history_lock: Protect the transactions statistics history
> * @j_proc_entry: procfs entry for the jbd statistics directory
> * @j_stats: Overall statistics
> --
> 2.5.1
>
>
--
Jan Kara <jack@suse.com>
SUSE Labs, CR
next prev parent reply other threads:[~2016-03-21 8:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-19 17:06 [PATCH] jbd2: remove excess descriptions for handle_s Luis de Bethencourt
2016-03-21 8:41 ` Jan Kara [this message]
2016-05-06 2:37 ` [RESEND Patch] " Theodore Ts'o
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=20160321084130.GA30819@quack.suse.cz \
--to=jack@suse.cz \
--cc=jack@suse.com \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luisbg@osg.samsung.com \
--cc=tytso@mit.edu \
/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).