From mboxrd@z Thu Jan 1 00:00:00 1970 From: tony@atomide.com Subject: Re: [RFC] Send OMAP clocksource and clockevent to rt mailing list Date: Wed, 20 Dec 2006 10:44:39 -0800 Message-ID: <20061220184439.GF22783@atomide.com> References: <45883982.8080207@gmail.com> <1166576011.6906.77.camel@vence.hilman.org> <45890397.2080809@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: <45890397.2080809@gmail.com> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: linux-omap-open-source-bounces+gplao-linux-omap-open-source=gmane.org@linux.omap.com Errors-To: linux-omap-open-source-bounces+gplao-linux-omap-open-source=gmane.org@linux.omap.com To: Dirk Behme Cc: OMAP-Linux List-Id: linux-omap@vger.kernel.org * Dirk Behme [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) >