From: John Crispin <blogic@openwrt.org>
To: Manuel Lauss <manuel.lauss@gmail.com>
Cc: Linux-MIPS <linux-mips@linux-mips.org>,
Ralf Baechle <ralf@linux-mips.org>,
Zi Shen Lim <zlim@netlogicmicro.com>,
Jayachandran C <jchandra@broadcom.com>
Subject: Re: [PATCH v2] MIPS: perf: fix build failure in XLP perf support.
Date: Tue, 18 Dec 2012 13:09:38 +0100 [thread overview]
Message-ID: <50D05D02.1090405@openwrt.org> (raw)
In-Reply-To: <1355729179-5442-1-git-send-email-manuel.lauss@gmail.com>
On 17/12/12 08:26, Manuel Lauss wrote:
> Commit 4be3d2f3966b9f010bb997dcab25e7af489a841e ("MIPS: perf: Add
> XLP support for hardware perf.") added UNSUPPORTED_PERF_EVENT_ID
> which was removed a while back.
>
> Cc: Zi Shen Lim<zlim@netlogicmicro.com>
> Cc: Jayachandran C<jchandra@broadcom.com>
> Signed-off-by: Manuel Lauss<manuel.lauss@gmail.com>
> ---
>
Hi,
my bad, this commit clashed with on in Ralf's tree...
Acked-by: John Crispin <blogic@openwrt.org
prev parent reply other threads:[~2012-12-18 12:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-17 7:26 [PATCH v2] MIPS: perf: fix build failure in XLP perf support Manuel Lauss
2012-12-17 12:46 ` Jayachandran C.
2012-12-18 12:09 ` John Crispin [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=50D05D02.1090405@openwrt.org \
--to=blogic@openwrt.org \
--cc=jchandra@broadcom.com \
--cc=linux-mips@linux-mips.org \
--cc=manuel.lauss@gmail.com \
--cc=ralf@linux-mips.org \
--cc=zlim@netlogicmicro.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.