From: Daniel Walker <dwalker@mvista.com>
To: Dirk Behme <dirk.behme@googlemail.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 22:54:47 -0800 [thread overview]
Message-ID: <1165042487.15319.11.camel@imap.mvista.com> (raw)
In-Reply-To: <4571192D.8040807@gmail.com>
On Sat, 2006-12-02 at 07:11 +0100, Dirk Behme wrote:
> > When Thomas did his -mm update all the clocksources got dropped
>
> I'm not talking about (OMAP) clocksource here. I'm talking
> about the rest [3], especially OMAP clockevent patch.
ok.
> - OMAP clockevent is potentially something for this list as
> well. But currently, it isn't discussed here and I can't
> find it discussed or included anywhere else. So it looks to
> me that it is lost (until anybody cares again). This is the
> core of my question: Is it currently nowhere maintained?
I guess Kevin and I maintain it. It's not such a large piece of code.
The reason that it's not getting pushed hard at the moment is because
HRT is testing in -mm .. So we're at a limbo point when we can't move
the code to RMK, and it's not really appropriate for the code to go into
-mm .. We just have to wait till HRT gets shaken out in -mm .
The reason we are able to send the clocksource to RMK is cause generic
time went into the 2.6.18 stable release.
> - The other patches, e.g. for ixp4xx and versatile, I think
> nobody will care on this list and update them here. So until
> they are not handled somewhere else (are they?), they will
> be lost as well.
>
> > Nothing should go via Thomas.
>
> You originally sent most of the patches to Thomas, don't you? ;)
Yes, before HRT went to -mm. The reason that it was useful to send them
to Thomas was for our own testing, and progressing HRT at an early
point. I wouldn't have minded if the OMAP clockevents when into -mm ,
but I've never seen anything like that happen (i.e. non-i386 board
specific code going into -mm).
Daniel
next prev parent reply other threads:[~2006-12-02 6:54 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
2006-12-02 3:21 ` Daniel Walker
2006-12-02 6:11 ` Dirk Behme
2006-12-02 6:54 ` Daniel Walker [this message]
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=1165042487.15319.11.camel@imap.mvista.com \
--to=dwalker@mvista.com \
--cc=dirk.behme@googlemail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox