From: "Américo Wang" <xiyou.wangcong@gmail.com>
To: linux-cris-kernel@axis.com, LKML <linux-kernel@vger.kernel.org>
Cc: Geert Uytterhoeven <geert@linux-m68k.org>,
Mikael Starvik <starvik@axis.com>,
Andrew Morton <akpm@linux-foundation.org>,
Jesper Nilsson <jesper.nilsson@axis.com>
Subject: [Patch] cris: add missing declaration of kgdb_init() and breakpoint()
Date: Sun, 22 May 2011 22:42:56 +0800 [thread overview]
Message-ID: <BANLkTimdog_wi+7_Vx7Qzpc0ZYor_RHg2g@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 460 bytes --]
This patch fixes such a build error on cris:
arch/cris/arch-v10/kernel/irq.c:239: error: implicit declaration of
function 'kgdb_init'
arch/cris/arch-v10/kernel/irq.c:240: error: implicit declaration of
function 'breakpoint'
So, just declare these two functions.
Reported-by: Geert Uytterhoeven <geert@linux-m68k.org>
Signed-off-by: WANG Cong <xiyou.wangcong@gmail.com>
Cc: Mikael Starvik <starvik@axis.com>
Cc: Jesper Nilsson <jesper.nilsson@axis.com>
---
[-- Attachment #2: cris-fix-build-error-kgdb_init.diff --]
[-- Type: text/x-patch, Size: 544 bytes --]
diff --git a/arch/cris/arch-v10/kernel/irq.c b/arch/cris/arch-v10/kernel/irq.c
index 907cfb5..ba0e596 100644
--- a/arch/cris/arch-v10/kernel/irq.c
+++ b/arch/cris/arch-v10/kernel/irq.c
@@ -20,6 +20,9 @@
#define crisv10_mask_irq(irq_nr) (*R_VECT_MASK_CLR = 1 << (irq_nr));
#define crisv10_unmask_irq(irq_nr) (*R_VECT_MASK_SET = 1 << (irq_nr));
+extern void kgdb_init(void);
+extern void breakpoint(void);
+
/* don't use set_int_vector, it bypasses the linux interrupt handlers. it is
* global just so that the kernel gdb can use it.
*/
next reply other threads:[~2011-05-22 14:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-22 14:42 Américo Wang [this message]
2011-06-01 22:16 ` Andrew Morton
2011-06-02 14:31 ` Américo Wang
2011-06-02 17:21 ` Andrew Morton
2011-06-03 15:32 ` Américo Wang
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=BANLkTimdog_wi+7_Vx7Qzpc0ZYor_RHg2g@mail.gmail.com \
--to=xiyou.wangcong@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=geert@linux-m68k.org \
--cc=jesper.nilsson@axis.com \
--cc=linux-cris-kernel@axis.com \
--cc=linux-kernel@vger.kernel.org \
--cc=starvik@axis.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
all inboxes | Powered by JetHome®