From: Dirk Behme <dirk.behme@googlemail.com>
To: tony@atomide.com
Cc: OMAP-Linux <linux-omap-open-source@linux.omap.com>
Subject: Re: [RFC] Send OMAP clocksource and clockevent to rt mailing list
Date: Wed, 20 Dec 2006 22:35:49 +0100 [thread overview]
Message-ID: <4589ACB5.1000401@gmail.com> (raw)
In-Reply-To: <20061220184439.GF22783@atomide.com>
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?
Btw, I got some feedback not to send the
clocksource/clockevent patches to -rt mailing list. Instead
LKML should be used. I will see to find some time to send it
to LKML as well.
Dirk
[1]
http://linux.omap.com/pipermail/linux-omap-open-source/2006-December/008569.html
next prev parent reply other threads:[~2006-12-20 21:35 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 [this message]
2006-12-21 0:02 ` Kevin Hilman
2006-12-21 19:51 ` Tony Lindgren
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=4589ACB5.1000401@gmail.com \
--to=dirk.behme@googlemail.com \
--cc=linux-omap-open-source@linux.omap.com \
--cc=tony@atomide.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