From: Ingo Molnar <mingo@elte.hu>
To: Dirk Behme <dirk.behme@googlemail.com>
Cc: linux-kernel@vger.kernel.org, tglx@linutronix.de,
David Brownell <dbrownell@users.sourceforge.net>,
dwalker@mvista.com, khilman@mvista.com
Subject: Re: [PATCH -rt 0/4] ARM: OMAP: Add clocksource and clockevent driver for OMAP
Date: Thu, 21 Dec 2006 10:43:41 +0100 [thread overview]
Message-ID: <20061221094341.GA9203@elte.hu> (raw)
In-Reply-To: <458A471C.3090402@gmail.com>
* Dirk Behme <dirk.behme@googlemail.com> wrote:
> Hi,
>
> the following patches for CONFIG PREEMPT RT add clocksource and
> clockevent driver for ARM based TI OMAP devices.
>
> They are against linux-2.6.19 + patch-2.6.20-rc1 +
> patch-2.6.20-rc1-rt1. The clocksource patch went through several
> review cycles on OMAP list.
thanks. I've added them to the -rt tree and it should be in the next
release (2.6.20-rt2).
(a couple of small suggestions for future submissions: if you send them
as attachments (which is fine to me), please name patches canonically,
i.e. "arm-no-hz.patch", not "arm-no-hz-patch.txt" and include the patch
description in the patch file too - or just send it all as plaintext.
Plus please Cc: everyone who's involved with the patch(es) so that they
can see feedback too - in this case that would be Daniel Walker, Kevin
Hilman and David Brownell.)
> Btw: What's about
>
> [PATCH -rt][RESEND] fix preempt hardirqs on OMAP
> http://www.ussg.iu.edu/hypermail/linux/kernel/0612.1/0642.html
that patch has problems because it breaks non-OMAP platforms. There was
a brief discussion about it but no updated patch AFAICS.
Ingo
next prev parent reply other threads:[~2006-12-21 9:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-21 8:34 [PATCH -rt 0/4] ARM: OMAP: Add clocksource and clockevent driver for OMAP Dirk Behme
2006-12-21 9:43 ` Ingo Molnar [this message]
2006-12-22 8:25 ` Dirk Behme
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=20061221094341.GA9203@elte.hu \
--to=mingo@elte.hu \
--cc=dbrownell@users.sourceforge.net \
--cc=dirk.behme@googlemail.com \
--cc=dwalker@mvista.com \
--cc=khilman@mvista.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tglx@linutronix.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 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.