From: Dirk Behme <dirk.behme@googlemail.com>
To: Daniel Walker <dwalker@mvista.com>, Kevin Hilman <khilman@mvista.com>
Cc: OMAP-Linux <linux-omap-open-source@linux.omap.com>
Subject: Re: [RFC] [PATCH] ARM: OMAP1: Add clocksource driver for OMAP1
Date: Fri, 01 Dec 2006 17:12:20 +0100 [thread overview]
Message-ID: <45705464.3070105@gmail.com> (raw)
In-Reply-To: <1164909003.17665.1.camel@imap.mvista.com>
Daniel Walker wrote:
> On Thu, 2006-11-30 at 18:55 +0100, Dirk Behme wrote:
>
>>I checked links below and can't find anything of your
>>patches integrated there. Do I miss anything?
>>
>>I wonder because 2.6.19 is out now and mainline patch window
>>opens for 2.6.20.
>>
>>http://tglx.de/projects/hrtimers/2.6.19-rc4-mm1/patch-2.6.19-rc4-mm1-hrt-dyntick4.patch
>>http://people.redhat.com/mingo/realtime-preempt/patch-2.6.19-rt1
>>http://kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.19-rc6/2.6.19-rc6-mm2/
>
> They went to RMK as far as I know. Someplace in his patch system.
Yes and no ;)
The Versatile and OMAP clocksource patches are in RMKs patch
system. The OMAP one is updated here on the list.
But as I understand Kevin, the rest has been submitted to
Thomas Gleixner and was planned to be included in the
-hrt-dyntick patcheset and then in -mm. And there I couldn't
find them. Would be a shame if they get lost. Especially the
OMAP clockevent one.
Cheers
Dirk
Content of your patches-2.6.19-rc2.tar.bz2:
arm-hrt-kconfig.patch
arm-ixp4xx-clockevent.patch
arm-leds-timer.patch
arm-no-hz.patch
arm-versatile-clockevents.patch
arm-versatile-clocksource.patch -> RMK patch system
arm_omap_clockevents.patch
arm_omap_clocksource.patch -> RMK patch system/ OMAP list
hrt-add-regs-include.patch
next prev parent reply other threads:[~2006-12-01 16:12 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-07 15:32 [RFC] [PATCH] ARM: OMAP1: Add clocksource driver for OMAP1 Dirk Behme
[not found] ` <4550CA9E.6090500@mvista.com>
2006-11-08 16:44 ` Dirk Behme
2006-11-10 0:29 ` Tony Lindgren
2006-11-10 0:48 ` Kevin Hilman
2006-11-10 0:53 ` Tony Lindgren
2006-11-30 19:57 ` Woodruff, Richard
2006-11-30 21:30 ` David Brownell
2006-11-30 21:49 ` Woodruff, Richard
2006-11-30 22:32 ` David Brownell
2006-11-30 22:57 ` Woodruff, Richard
2006-11-30 22:12 ` tony
2006-11-30 21:59 ` tony
2006-11-30 22:24 ` Woodruff, Richard
2006-11-30 22:37 ` tony
2006-11-30 17:55 ` Dirk Behme
2006-11-30 17:50 ` Daniel Walker
2006-12-01 16:12 ` Dirk Behme [this message]
2006-12-02 3:21 ` Daniel Walker
2006-12-02 6:11 ` Dirk Behme
2006-12-02 6:54 ` Daniel Walker
2006-12-02 7:06 ` Dirk Behme
2006-12-02 7:18 ` Daniel Walker
2006-12-04 23:34 ` Kevin Hilman
2006-11-30 19:14 ` David Brownell
2006-11-30 20:33 ` Dirk Behme
2006-11-30 21:22 ` [RFC] [PATCH] ARM: Add clocksource driver for OMAP1 and OMAP2 David Brownell
2006-12-01 18:21 ` Dirk Behme
2006-12-01 19:03 ` David Brownell
2006-12-01 22:13 ` Tony Lindgren
2006-12-03 2:58 ` David Brownell
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=45705464.3070105@gmail.com \
--to=dirk.behme@googlemail.com \
--cc=dwalker@mvista.com \
--cc=khilman@mvista.com \
--cc=linux-omap-open-source@linux.omap.com \
/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.