From: Arun Sharma <asharma@fb.com>
To: avagin@gmail.com
Cc: linux-perf-users@vger.kernel.org, David Ahern <dsahern@gmail.com>
Subject: Re: Trouble parsing trace events
Date: Tue, 22 Nov 2011 23:14:37 -0800 [thread overview]
Message-ID: <4ECC9D5D.3080108@fb.com> (raw)
In-Reply-To: <4ECC9AD8.3010801@gmail.com>
On 11/22/11 11:03 PM, Andrew Vagin wrote:
> Hello Arun,
>
> This bug was fixed already, but the commit isn't in Linus's tree yet.
> http://git.kernel.org/?p=linux/kernel/git/tip/tip.git;a=commit;h=49908a1b25d448d68fd26faca260e1850201575f
Thanks. I was confused about where various git trees live these days and
was fetching from
git://git.kernel.org/pub/scm/linux/kernel/git/mingo/tip.git
which doesn't have the commit you're referring to.
-Arun
prev parent reply other threads:[~2011-11-23 7:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-23 6:51 Trouble parsing trace events Arun Sharma
2011-11-23 7:03 ` Andrew Vagin
2011-11-23 7:14 ` Arun Sharma [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=4ECC9D5D.3080108@fb.com \
--to=asharma@fb.com \
--cc=avagin@gmail.com \
--cc=dsahern@gmail.com \
--cc=linux-perf-users@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.