From: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
To: Tim Sander <tstone@vlsi.informatik.tu-darmstadt.de>
Cc: linux-rt-users@vger.kernel.org
Subject: Re: Ooops 805 2.6.31.12-rt20
Date: Thu, 28 Jan 2010 20:54:57 +0100 [thread overview]
Message-ID: <20100128195457.GA5541@pengutronix.de> (raw)
In-Reply-To: <201001282041.30610.tstone@vlsi.informatik.tu-darmstadt.de>
Hello Tim,
On Thu, Jan 28, 2010 at 08:41:30PM +0100, Tim Sander wrote:
> 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?
It's not trivial to merge Linus' tree and the rt tree. In the mail
announcing 2.6.31.12-rt20 Thomas says to start working at 33-rcX-rt. I
assume you have to wait for that.
> Btw heres a little typo fix (colon missing). Probably the wrong
> mailing list, but the right people 8-)
The right people are reading linux-arm-kernel ML, not this one. I sent
a patch including a commit log to that list.
Best regards
Uwe
--
Pengutronix e.K. | Uwe Kleine-König |
Industrial Linux Solutions | http://www.pengutronix.de/ |
--
To unsubscribe from this list: send the line "unsubscribe linux-rt-users" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2010-01-28 19:54 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
2010-01-28 19:54 ` Uwe Kleine-König [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=20100128195457.GA5541@pengutronix.de \
--to=u.kleine-koenig@pengutronix.de \
--cc=linux-rt-users@vger.kernel.org \
--cc=tstone@vlsi.informatik.tu-darmstadt.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).