From: Harry Wei <jiaweiwei.xiyou@gmail.com>
To: Randy Dunlap <randy.dunlap@oracle.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [Oops]RFC:include/trace/events/btrfs.h
Date: Tue, 7 Jun 2011 09:03:46 +0800 [thread overview]
Message-ID: <20110607010344.GA8892@gmail.com> (raw)
In-Reply-To: <20110606134719.b24ecc07.randy.dunlap@oracle.com>
On Mon, Jun 06, 2011 at 01:47:19PM -0700, Randy Dunlap wrote:
> On Sun, 5 Jun 2011 11:41:14 +0800 Harry Wei wrote:
>
> > From: Harry Wei <harryxiyou@gmail.com>
> >
> > When i compile 2.6.39.1, it shows something wrong
> > like below. When i open the file include/trace/events/btrfs.h
> > i don't know how to fix these oops. They just give the entry
> > of the function. So i can't get the exact line of the warnings.
> > Can anyone give me some suggestions?
>
> Yeah, those line numbers (below) don't help very much.
>
> There is a patch pending to fix these warnings. It's from
> liubo <liubo2009@cn.fujitsu.com>, posted on 2011-APR-19,
> subject: [PATCH 1/2] tracing: add __print_symbolic_u64 to avoid warnings on 32bit machine
>
Yup, it is well for me.
Thanks.
Harry Wei.
prev parent reply other threads:[~2011-06-07 1:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-05 3:41 [Oops]RFC:include/trace/events/btrfs.h Harry Wei
2011-06-06 20:47 ` [Oops]RFC:include/trace/events/btrfs.h Randy Dunlap
2011-06-07 1:03 ` Harry Wei [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=20110607010344.GA8892@gmail.com \
--to=jiaweiwei.xiyou@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=randy.dunlap@oracle.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 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.