From: Kevin Hilman <khilman@mvista.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: Tue, 19 Dec 2006 16:53:31 -0800 [thread overview]
Message-ID: <1166576011.6906.77.camel@vence.hilman.org> (raw)
In-Reply-To: <45883982.8080207@gmail.com>
On Tue, 2006-12-19 at 20:12 +0100, Dirk Behme wrote:
> Any objections to send these patches in attachment to rt
> mailing list?
No objections here.
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? Or would you
rather I do it separately?
Kevin
next prev parent reply other threads:[~2006-12-20 0:53 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 [this message]
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
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=1166576011.6906.77.camel@vence.hilman.org \
--to=khilman@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