From: liubo <liubo2009@cn.fujitsu.com>
To: Chris Mason <chris.mason@oracle.com>
Cc: Linux Btrfs <linux-btrfs@vger.kernel.org>,
Josef Bacik <josef@redhat.com>
Subject: Re: [PATCH] Btrfs: add initial tracepoint support for btrfs
Date: Tue, 29 Mar 2011 09:16:11 +0800 [thread overview]
Message-ID: <4D9132DB.9000507@cn.fujitsu.com> (raw)
In-Reply-To: <1301273942-sup-2832@think>
On 03/28/2011 08:59 AM, Chris Mason wrote:
> Excerpts from Chris Mason's message of 2011-03-26 08:12:04 -0400:
>> Excerpts from liubo's message of 2011-03-24 07:18:59 -0400:
>>> Tracepoints can provide insight into why btrfs hits bugs and be greatly
>>> helpful for debugging, e.g
>> This is really neat, I've queued it up.
>
> Whoops, it has a lot of warnings when compiled on 32 bit machines.
> Please take a look:
>
> include/trace/events/btrfs.h:47:1: warning: large integer implicitly truncated to unsigned type
> include/trace/events/btrfs.h:47:1: warning: large integer implicitly truncated to unsigned type
> include/trace/events/btrfs.h:47:1: warning: large integer implicitly truncated to unsigned type
> include/trace/events/btrfs.h:68:1: warning: large integer implicitly truncated to unsigned type
> include/trace/events/btrfs.h:68:1: warning: large integer implicitly truncated to unsigned type
> include/trace/events/btrfs.h:68:1: warning: large integer implicitly truncated to unsigned type
> include/trace/events/btrfs.h:144:1: warning: large integer implicitly truncated to unsigned type
>
Ahh, I figure it out.
Will send a new version to clear warnings.
Thanks,
liubo
> -chris
> --
> To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
next prev parent reply other threads:[~2011-03-29 1:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-24 11:18 [PATCH] Btrfs: add initial tracepoint support for btrfs liubo
2011-03-26 12:12 ` Chris Mason
2011-03-28 0:59 ` Chris Mason
2011-03-29 1:16 ` liubo [this message]
2011-03-29 7:47 ` liubo
2011-03-29 8:30 ` liubo
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=4D9132DB.9000507@cn.fujitsu.com \
--to=liubo2009@cn.fujitsu.com \
--cc=chris.mason@oracle.com \
--cc=josef@redhat.com \
--cc=linux-btrfs@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.