public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: tony@atomide.com
To: Dirk Behme <dirk.behme@googlemail.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 10:44:39 -0800	[thread overview]
Message-ID: <20061220184439.GF22783@atomide.com> (raw)
In-Reply-To: <45890397.2080809@gmail.com>

* Dirk Behme <dirk.behme@googlemail.com> [061220 01:41]:
> Kevin Hilman wrote:
> >Tony, I was going to submit the clocksoure/clockevent to RMK, but since
> >we missed the merge window, can we just add the clocksource/clockevent
> >patches to the patch queue that's already going to RMK?
> 
> Clocksource yes, I have it in my pending patches list. But 
> clockevent still needs CONFIG_PREEMPT_RT patch? So this 
> can't directly go to RMK?

Yes, I'll be updating the patch queue. So I guess the plan is
to send clocksource through RMK. But that will take a while
before that gets merged.
 
> 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.

Regards,

Tony

>
> [1] http://news.gmane.org/gmane.linux.rt.user
> (works now)
>

  reply	other threads:[~2006-12-20 18:44 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 [this message]
2006-12-20 21:35       ` Dirk Behme
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=20061220184439.GF22783@atomide.com \
    --to=tony@atomide.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