From: Andi Kleen <ak@suse.de>
To: eranian@hpl.hp.com
Cc: linux-kernel@vger.kernel.org, akpm@linux-foundation.org
Subject: Re: [PATCH] i386 make NMI use PERFCTR1 for architectural perfmon
Date: Sun, 18 Feb 2007 17:56:05 +0100 [thread overview]
Message-ID: <200702181756.05672.ak@suse.de> (raw)
In-Reply-To: <20070217160656.GA16715@frankl.hpl.hp.com>
On Saturday 17 February 2007 17:06, Stephane Eranian wrote:
> Hello,
>
> This patch against 2.6.20
Please always submit against mainline:
patching file arch/i386/kernel/nmi.c
Hunk #1 FAILED at 288.
Hunk #2 succeeded at 740 (offset 55 lines).
Hunk #3 succeeded at 1017 with fuzz 1 (offset 59 lines).
1 out of 3 hunks FAILED -- rejects in file arch/i386/kernel/nmi.c
Patch patches/i386-make-nmi-use-perfctr1-for-architectural-perfmon does not apply (enforce with -f)
-Andi
next prev parent reply other threads:[~2007-02-18 16:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-17 16:06 [PATCH] i386 make NMI use PERFCTR1 for architectural perfmon Stephane Eranian
2007-02-18 16:56 ` Andi Kleen [this message]
2007-02-19 16:36 ` Stephane Eranian
2007-02-19 16:38 ` Andi Kleen
2007-02-19 22:32 ` [PATCH] i386 make NMI use PERFCTR1 for architectural perfmon (take 2) Stephane Eranian
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=200702181756.05672.ak@suse.de \
--to=ak@suse.de \
--cc=akpm@linux-foundation.org \
--cc=eranian@hpl.hp.com \
--cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox