From: Lachlan McIlroy <lachlan@sgi.com>
To: David Chinner <dgc@sgi.com>
Cc: xfs-dev <xfs-dev@sgi.com>, xfs-oss <xfs@oss.sgi.com>
Subject: Re: [PATCH] Fix non-debug build for xfsidbg.c
Date: Wed, 30 Apr 2008 17:17:24 +1000 [thread overview]
Message-ID: <48181D04.4030902@sgi.com> (raw)
In-Reply-To: <20080430065937.GC108924158@sgi.com>
Dave, would the code look cleaner if iclog_bak was printed on a line by itself?
That way we wouldn't need the #else and we wouldn't be duplicating code.
David Chinner wrote:
> Make the use of l_iclog_bak conditional on debug configs.
>
> Signed-off-by: Dave Chinner <dgc@sgi.com>
> ---
> fs/xfs/xfsidbg.c | 5 +++++
> 1 file changed, 5 insertions(+)
>
> Index: 2.6.x-xfs-new/fs/xfs/xfsidbg.c
> ===================================================================
> --- 2.6.x-xfs-new.orig/fs/xfs/xfsidbg.c 2008-04-30 16:47:06.000000000 +1000
> +++ 2.6.x-xfs-new/fs/xfs/xfsidbg.c 2008-04-30 16:49:33.615164895 +1000
> @@ -5845,9 +5845,14 @@ xfsidbg_xlog(xlog_t *log)
> kdb_printf("curr_cycle: %d prev_cycle: %d curr_block: %d prev_block: %d\n",
> log->l_curr_cycle, log->l_prev_cycle, log->l_curr_block,
> log->l_prev_block);
> +#ifdef DEBUG
> kdb_printf("iclog_bak: 0x%p iclog_size: 0x%x (%d) num iclogs: %d\n",
> log->l_iclog_bak, log->l_iclog_size, log->l_iclog_size,
> log->l_iclog_bufs);
> +#else
> + kdb_printf("iclog_size: 0x%x (%d) num iclogs: %d\n",
> + log->l_iclog_size, log->l_iclog_size, log->l_iclog_bufs);
> +#endif
> kdb_printf("l_iclog_hsize %d l_iclog_heads %d\n",
> log->l_iclog_hsize, log->l_iclog_heads);
> kdb_printf("l_sectbb_log %u l_sectbb_mask %u\n",
>
next prev parent reply other threads:[~2008-04-30 7:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-30 6:59 [PATCH] Fix non-debug build for xfsidbg.c David Chinner
2008-04-30 7:17 ` Lachlan McIlroy [this message]
2008-05-01 0:49 ` David Chinner
2008-05-01 1:42 ` Lachlan McIlroy
2008-05-01 3:01 ` David Chinner
2008-05-01 7:22 ` Lachlan McIlroy
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=48181D04.4030902@sgi.com \
--to=lachlan@sgi.com \
--cc=dgc@sgi.com \
--cc=xfs-dev@sgi.com \
--cc=xfs@oss.sgi.com \
/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