From: Philippe Gerum <rpm@xenomai.org>
To: Jan Kiszka <jan.kiszka@domain.hid>
Cc: adeos-main <adeos-main@gna.org>
Subject: Re: [Adeos-main] [PATCH] Fix include for kernel/panic.c
Date: Mon, 29 Dec 2008 17:00:32 +0100 [thread overview]
Message-ID: <4958F420.7030109@domain.hid> (raw)
In-Reply-To: <4958E439.9040503@domain.hid>
Jan Kiszka wrote:
> Not all archs include ipipe_trace.h implicitly so that bulding
> kernel/panic.c may break in oops_enter (seen on ARM with tracer
> disabled). Fix this with a proper include.
>
Thanks. Fix a bit earlier on ppc as well. I will push my tree soon now since
things seem to have gone back to normal wrt 2.6.27.
> Signed-off-by: Jan Kiszka <jan.kiszka@domain.hid>
>
> ---
> kernel/panic.c | 1 +
> 1 file changed, 1 insertion(+)
>
> Index: b/kernel/panic.c
> ===================================================================
> --- a/kernel/panic.c
> +++ b/kernel/panic.c
> @@ -21,6 +21,7 @@
> #include <linux/debug_locks.h>
> #include <linux/random.h>
> #include <linux/kallsyms.h>
> +#include <linux/ipipe_trace.h>
>
> int panic_on_oops;
> int tainted;
>
>
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> Adeos-main mailing list
> Adeos-main@domain.hid
> https://mail.gna.org/listinfo/adeos-main
--
Philippe.
prev parent reply other threads:[~2008-12-29 16:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-29 14:52 [Adeos-main] [PATCH] Fix include for kernel/panic.c Jan Kiszka
2008-12-29 15:55 ` Gilles Chanteperdrix
2008-12-29 17:28 ` Jan Kiszka
2008-12-29 17:31 ` Gilles Chanteperdrix
2008-12-29 18:10 ` Jan Kiszka
2008-12-29 20:32 ` Philippe Gerum
2008-12-29 16:00 ` Philippe Gerum [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=4958F420.7030109@domain.hid \
--to=rpm@xenomai.org \
--cc=adeos-main@gna.org \
--cc=jan.kiszka@domain.hid \
/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.