All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sebastian Smolorz <ssm@domain.hid>
To: xenomai-core <xenomai@xenomai.org>
Subject: [Xenomai-core] [PATCH] Missing include when compiling an ipiped Linux kernel with CONFIG_PREEMPT for ARM
Date: Fri, 10 Nov 2006 12:23:41 +0100	[thread overview]
Message-ID: <E1GiUTz-00027a-G9@domain.hid> (raw)

[-- Attachment #1: Type: text/plain, Size: 132 bytes --]

Hi,

here comes a fix for I-pipe for ARM. Without it the kernel refuses to compile 
when configured with CONFIG_PREEMPT.

Sebastian

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: ipipe_preempt_compile.patch --]
[-- Type: text/x-diff; charset="us-ascii"; name="ipipe_preempt_compile.patch", Size: 776 bytes --]

--- linux-2.6.15-ipipe.orig/include/asm-arm/ipipe.h	2006-11-08 16:44:02.000000000 +0100
+++ linux-2.6.15-ipipe.work/include/asm-arm/ipipe.h	2006-11-10 12:12:44.000000000 +0100
@@ -34,6 +34,7 @@
 #include <asm/irq.h>
 #include <asm/bitops.h>
 #include <asm/mach/irq.h>
+#include <asm/percpu.h>
 
 #define IPIPE_ARCH_STRING	"1.5-02"
 #define IPIPE_MAJOR_NUMBER	1
@@ -51,7 +52,7 @@
 #endif	/* CONFIG_SMP */
 
 /* Note that we disable the interrupts around context_switch,
- * or we'll get into severe problems when scheduling Xenomaï
+ * or we'll get into severe problems when scheduling Xenomai's
  * user space real time threads.
  * This can however cause high latencies, see for example:
  * 	http://www.ussg.iu.edu/hypermail/linux/kernel/0405.2/1388.html

             reply	other threads:[~2006-11-10 11:23 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-10 11:23 Sebastian Smolorz [this message]
2006-11-11 17:21 ` [Xenomai-core] [PATCH] Missing include when compiling an ipiped Linux kernel with CONFIG_PREEMPT for ARM Philippe Gerum

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=E1GiUTz-00027a-G9@domain.hid \
    --to=ssm@domain.hid \
    --cc=xenomai@xenomai.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 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.