From: Rusty Lynch <rusty.lynch@intel.com>
To: Andrew Morton <akpm@osdl.org>
Cc: Anil S Keshavamurthy <anil.s.keshavamurthy@intel.com>,
linux-kernel@vger.kernel.org
Subject: [patch] ia64 kprobes build fix
Date: Mon, 27 Jun 2005 11:02:03 -0700 [thread overview]
Message-ID: <200506271802.j5RI23OP010589@linux.jf.intel.com> (raw)
The following patch fixes an ia64 build failure when kprobes is enabled
as a result of the single-step out of line patch that expects each architecture
do define MAX_INSN_SIZE.
Signed-off-by: Rusty Lynch <rusty.lynch@intel.com>
include/asm-ia64/kprobes.h | 1 +
1 files changed, 1 insertion(+)
Index: linux-2.6.12-mm2/include/asm-ia64/kprobes.h
===================================================================
--- linux-2.6.12-mm2.orig/include/asm-ia64/kprobes.h
+++ linux-2.6.12-mm2/include/asm-ia64/kprobes.h
@@ -28,6 +28,7 @@
#include <linux/ptrace.h>
#include <asm/break.h>
+#define MAX_INSN_SIZE 16
#define BREAK_INST (long)(__IA64_BREAK_KPROBE << 6)
typedef union cmp_inst {
reply other threads:[~2005-06-27 18:02 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=200506271802.j5RI23OP010589@linux.jf.intel.com \
--to=rusty.lynch@intel.com \
--cc=akpm@osdl.org \
--cc=anil.s.keshavamurthy@intel.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