From: Sudip Mukherjee <sudipm.mukherjee@gmail.com>
To: David Howells <dhowells@redhat.com>
Cc: linux-am33-list@redhat.com, linux-kernel@vger.kernel.org,
Sudip Mukherjee <sudipm.mukherjee@gmail.com>
Subject: [PATCH 1/2] mn10300: fix build failure
Date: Tue, 16 Jun 2015 18:16:30 +0530 [thread overview]
Message-ID: <1434458791-13384-2-git-send-email-sudipm.mukherjee@gmail.com> (raw)
In-Reply-To: <1434458791-13384-1-git-send-email-sudipm.mukherjee@gmail.com>
allmodconfig build fails with the error:
invalid use of undefined type 'struct kprobe_ctlblk'
just declared the two basic structures after checking the struct in other
architectures.
Signed-off-by: Sudip Mukherjee <sudip@vectorindia.org>
---
arch/mn10300/include/asm/kprobes.h | 12 ++++++++++++
1 file changed, 12 insertions(+)
diff --git a/arch/mn10300/include/asm/kprobes.h b/arch/mn10300/include/asm/kprobes.h
index c800b59..c90d2b1 100644
--- a/arch/mn10300/include/asm/kprobes.h
+++ b/arch/mn10300/include/asm/kprobes.h
@@ -47,4 +47,16 @@ extern int kprobe_exceptions_notify(struct notifier_block *self,
extern void arch_remove_kprobe(struct kprobe *p);
+struct prev_kprobe {
+ struct kprobe *kp;
+ unsigned long status;
+};
+
+struct kprobe_ctlblk {
+ unsigned int kprobe_status;
+ struct pt_regs jprobe_saved_regs;
+ char jprobes_stack[MAX_STACK_SIZE];
+ struct prev_kprobe prev_kprobe;
+};
+
#endif /* _ASM_KPROBES_H */
--
1.8.1.2
next prev parent reply other threads:[~2015-06-16 12:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-16 12:46 [PATCH 0/2] fix build failure of mn10300 Sudip Mukherjee
2015-06-16 12:46 ` Sudip Mukherjee [this message]
2015-06-16 12:46 ` [PATCH 2/2] mn10300: Provide dummy dma_alloc_attrs() and dma_free_attrs() Sudip Mukherjee
2015-06-18 11:32 ` [PATCH 0/2] fix build failure of mn10300 Sudip Mukherjee
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=1434458791-13384-2-git-send-email-sudipm.mukherjee@gmail.com \
--to=sudipm.mukherjee@gmail.com \
--cc=dhowells@redhat.com \
--cc=linux-am33-list@redhat.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