From: Tony Lindgren <tony@atomide.com>
To: Kevin Hilman <khilman@mvista.com>
Cc: OMAP-Linux <linux-omap-open-source@linux.omap.com>
Subject: Re: [RFC] Send OMAP clocksource and clockevent to rt mailing list
Date: Thu, 21 Dec 2006 11:51:52 -0800 [thread overview]
Message-ID: <20061221195152.GC10399@atomide.com> (raw)
In-Reply-To: <1166659334.6906.123.camel@vence.hilman.org>
* Kevin Hilman <khilman@mvista.com> [061220 16:02]:
> On Wed, 2006-12-20 at 22:35 +0100, Dirk Behme wrote:
> > tony@atomide.com wrote:
> > > * Dirk Behme <dirk.behme@googlemail.com> [061220 01:41]:
> > >>I now sent our clocksource/clockevent patches to -rt mailing
> > >>list [1]. If clocksource goes to RMK as well, we have two
> > >>paths we can get it into mainline. Let us see which is the
> > >>faster and better one. The biggest risk will be some merge
> > >>conflicts if both are successful ;)
> > >
> > > No problem with merge conclicts on the RMK queue, I can easily
> > > refresh that patch series accordingly. So let's send what is
> > > needed to be included in the RT series.
> >
> > I think at least our latest clocksource [1] patch should go
> > to RMK.
> >
> > Kevin: What's about clockevent and RMK?
>
> Sorry for the confusion. Only clocksource patches are going to RMK for
> now since the clockevents are dependent on tglx's -hrt-dyntick patch
> (part of -rt)
Sounds good to me.
Tony
prev parent reply other threads:[~2006-12-21 19:51 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-19 19:12 [RFC] Send OMAP clocksource and clockevent to rt mailing list Dirk Behme
2006-12-19 19:41 ` Daniel Walker
2006-12-20 0:53 ` Kevin Hilman
2006-12-20 9:34 ` Dirk Behme
2006-12-20 18:44 ` tony
2006-12-20 21:35 ` Dirk Behme
2006-12-21 0:02 ` Kevin Hilman
2006-12-21 19:51 ` Tony Lindgren [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=20061221195152.GC10399@atomide.com \
--to=tony@atomide.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.