From: Ralf Baechle <ralf@linux-mips.org>
To: wu zhangjin <wuzhangjin@gmail.com>
Cc: Deng-Cheng Zhu <dengcheng.zhu@gmail.com>,
linux-mips <linux-mips@linux-mips.org>
Subject: Re: [BUG] The Perf support of MIPS is broken for the upstream changes
Date: Thu, 4 Nov 2010 15:30:57 +0000 [thread overview]
Message-ID: <20101104153055.GA22377@linux-mips.org> (raw)
In-Reply-To: <AANLkTinnya458ReBBaJtVFg3OP-XQE5MkeVnFT8zUeMN@mail.gmail.com>
On Thu, Nov 04, 2010 at 11:20:19PM +0800, wu zhangjin wrote:
> $ git log {kernel/perf_event.c,include/linux/perf_event.h}
>
> Of course, at first, you may need to clone/pull a latest mainline kernel.
Note that the linux-mips.org kernel repository is a superset of the
mainline kernel. To reduce the confusion I just don't push any of Linus'
tags but the kernel objects are all there.
Anybody who wants to get Linus' tags or a linus branch as well can fetch
from Linus tree. The size increase is minimal.
Ralf
prev parent reply other threads:[~2010-11-04 15:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-04 15:20 [BUG] The Perf support of MIPS is broken for the upstream changes wu zhangjin
2010-11-04 15:30 ` Ralf Baechle [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=20101104153055.GA22377@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=dengcheng.zhu@gmail.com \
--cc=linux-mips@linux-mips.org \
--cc=wuzhangjin@gmail.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