From: Thomas Gleixner <tglx@linutronix.de>
To: Pierre Peiffer <pierre.peiffer@bull.net>
Cc: "Ingo Molnar" <mingo@elte.hu>,
LKML <linux-kernel@vger.kernel.org>,
"Sébastien Dugué" <sebastien.dugue@bull.net>
Subject: Re: How to distinguish original kernel vs -rt kernel
Date: Wed, 07 Mar 2007 10:54:50 +0100 [thread overview]
Message-ID: <1173261291.24738.581.camel@localhost.localdomain> (raw)
In-Reply-To: <45EE8829.4060304@bull.net>
On Wed, 2007-03-07 at 10:38 +0100, Pierre Peiffer wrote:
> In fact, I'm facing the problem of HRTIMER_ABS/REL being renamed to
> HRTIMER_MODE_ABS/REL with patch -rt. Is there a reason of this ?
>
> Does anyone have an objection of keeping it the same (let's say
> HRTIMER_ABS/REL) in kernel -rt ?
It is HRTIMER_MODE_xx in mainline as of 2.6.21-rc1. -rt kernels are
always a bit ahead of time. :)
tglx
next prev parent reply other threads:[~2007-03-07 9:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-07 9:38 Pierre Peiffer
2007-03-07 9:54 ` Thomas Gleixner [this message]
2007-03-07 13:00 ` Pierre Peiffer
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=1173261291.24738.581.camel@localhost.localdomain \
--to=tglx@linutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=pierre.peiffer@bull.net \
--cc=sebastien.dugue@bull.net \
/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
Powered by JetHome