From: Theodore Tso <tytso@mit.edu>
To: Dirk Behme <dirk.behme@googlemail.com>
Cc: linux-rt-users@vger.kernel.org, tglx@linutronix.de,
David Brownell <david-b@pacbell.net>,
Daniel Walker <dwalker@mvista.com>,
Kevin Hilman <khilman@mvista.com>
Subject: Re: [patch 0/4] ARM: OMAP: Add clocksource and clockevent driver for OMAP
Date: Wed, 20 Dec 2006 10:55:07 -0500 [thread overview]
Message-ID: <20061220155507.GB1710@thunk.org> (raw)
In-Reply-To: <4588FFC7.5060203@gmail.com>
On Wed, Dec 20, 2006 at 10:17:59AM +0100, Dirk Behme wrote:
>
> the following patches add clocksource and clockevent driver
> for ARM based TI OMAP devices.
>
> They are against linux-2.6.19 + patch-2.6.20-rc1 +
> patch-2.6.20-rc1-rt0. The clocksource patch went through
> several review cycles on OMAP list.
Hi Dirk,
As a suggestion, could you consider sending patches to
linux-kernel@vger.kernel.org? One of the reasons why we (in
consultation with folks like Ingo and tglx) deliberatly didn't create
a RT development list was that in order to promote getting -rt related
patches into mainline as soon as possible, we wanted to keep patch and
development discussion on LKML. For example, it's not clear that the
ARM maintainer subscribes to linux-rt-users; furthermore the more
patch discussion happens on LKML, it helps promote willingness of
other kernel developers that CONFIG_PREEMPT_RT isn't going to go away,
and will probably (hopefully!) be merged into mainline someday soon.
Regards,
- Ted
next prev parent reply other threads:[~2006-12-20 15:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-20 9:17 [patch 0/4] ARM: OMAP: Add clocksource and clockevent driver for OMAP Dirk Behme
2006-12-20 15:55 ` Theodore Tso [this message]
2006-12-20 21:28 ` Dirk Behme
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=20061220155507.GB1710@thunk.org \
--to=tytso@mit.edu \
--cc=david-b@pacbell.net \
--cc=dirk.behme@googlemail.com \
--cc=dwalker@mvista.com \
--cc=khilman@mvista.com \
--cc=linux-rt-users@vger.kernel.org \
--cc=tglx@linutronix.de \
/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.