From: Tim Sander <tstone@vlsi.informatik.tu-darmstadt.de>
To: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
Cc: linux-rt-users@vger.kernel.org
Subject: Re: Ooops 805 2.6.31.12-rt20
Date: Thu, 28 Jan 2010 20:41:30 +0100 [thread overview]
Message-ID: <201001282041.30610.tstone@vlsi.informatik.tu-darmstadt.de> (raw)
In-Reply-To: <20100128080125.GC13756@pengutronix.de>
Hi
> This is already fixed in mainline. (And you were Cc:d for the two
> most relevant patches!)
Oh, then sorry for the noise. I really forgot it seems as if last year is like long ago...
> 84177a2 and 81538e7 are the important ones for you, I didn't check the
Ok thanks.
Btw. is there a up to date preempt rt git tree. I looked on git.kernel.org but i didn't
find any recent preemt-rt linux tree? I mean one where the mainline
fixes and the -rt patches are in one tree?
Best regards
Tim
Btw heres a little typo fix (colon missing). Probably the wrong mailing list, but the right people 8-)
diff --git a/arch/arm/plat-mxc/include/mach/iomux-mx35.h b/arch/arm/plat-mxc/include/mach/iomux-mx35.h
index 00b0ac1..c88d407 100644
--- a/arch/arm/plat-mxc/include/mach/iomux-mx35.h
+++ b/arch/arm/plat-mxc/include/mach/iomux-mx35.h
@@ -671,7 +671,7 @@
#define MX35_PAD_LD8__SDMA_SDMA_DEBUG_PC_8 IOMUX_PAD(0x634, 0x1d0, 6, 0x0, 0, NO_PAD_CTRL)
#define MX35_PAD_LD9__IPU_DISPB_DAT_9 IOMUX_PAD(0x638, 0x1d4, 0, 0x0, 0, NO_PAD_CTRL)
-#define MX35_PAD_LD9__GPIO2_9 IOMUX_PAD(0x638, 0x1d4, 5, 0x8e4 0, NO_PAD_CTRL)
+#define MX35_PAD_LD9__GPIO2_9 IOMUX_PAD(0x638, 0x1d4, 5, 0x8e4, 0, NO_PAD_CTRL)
#define MX35_PAD_LD9__SDMA_SDMA_DEBUG_PC_9 IOMUX_PAD(0x638, 0x1d4, 6, 0x0, 0, NO_PAD_CTRL)
#define MX35_PAD_LD10__IPU_DISPB_DAT_10 IOMUX_PAD(0x63c, 0x1d8, 0, 0x0, 0, NO_PAD_CTRL)
next prev parent reply other threads:[~2010-01-28 19:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-27 14:09 Ooops 805 2.6.31.12-rt20 Tim Sander
2010-01-28 8:01 ` Uwe Kleine-König
2010-01-28 19:41 ` Tim Sander [this message]
2010-01-28 19:54 ` Uwe Kleine-König
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=201001282041.30610.tstone@vlsi.informatik.tu-darmstadt.de \
--to=tstone@vlsi.informatik.tu-darmstadt.de \
--cc=linux-rt-users@vger.kernel.org \
--cc=u.kleine-koenig@pengutronix.de \
/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;
as well as URLs for NNTP newsgroup(s).