public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Peter Williams <pwil3058@bigpond.net.au>
To: Ingo Molnar <mingo@elte.hu>
Cc: Gregory Haskins <ghaskins@novell.com>,
	jim.houston@ccur.com, joe.korty@ccur.com, rostedt@goodmis.org,
	tglx@linutronix.de, dwalker@mvista.com,
	David Bahi <DBahi@novell.com>, Moiz Kohari <MKohari@novell.com>,
	Sven Dietrich <SDietrich@novell.com>,
	dsaxena@plexity.net, williams@redhat.com, abogani@texware.it,
	linux-kernel@vger.kernel.org, linux-rt-users@vger.kernel.org
Subject: Possible error in 2.6.23-rc2-rt1 series
Date: Mon, 06 Aug 2007 11:29:54 +1000	[thread overview]
Message-ID: <46B67992.1080503@bigpond.net.au> (raw)
In-Reply-To: <20070712130958.GB17494@elte.hu>

I've just been reviewing these patches and have spotted a possible
error in the file arch/ia64/kernel/time.c in that the scope of the
#ifdef on CONFIG_TIME_INTERPOLATION seems to have grown quite a lot
since 2.2.23-rc1-rt7.  It used to chop out one if statement and now it
chops out half the file.

Is it correct?
Peter
-- 
Peter Williams                                   pwil3058@bigpond.net.au

"Learning, n. The kind of ignorance distinguishing the studious."
 -- Ambrose Bierce



  parent reply	other threads:[~2007-08-06  3:55 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-12 12:26 Forward port of latest RT patch (2.6.21.5-rt20) to 2.6.22 available Gregory Haskins
2007-07-12 13:09 ` Ingo Molnar
2007-07-13  6:25   ` Peter Williams
2007-07-13  6:52     ` Thomas Gleixner
2007-07-13  8:43     ` Gene Heskett
2007-07-13  9:42       ` Thomas Gleixner
2007-07-14  0:27       ` Peter Williams
2007-07-14  0:52         ` Gene Heskett
2007-07-26  1:24   ` Minor errors in 2.6.23-rc1-rt2 series Peter Williams
2007-07-26  7:36     ` Ingo Molnar
2007-08-06  1:29   ` Peter Williams [this message]
2007-08-06  5:42     ` Possible error in 2.6.23-rc2-rt1 series Ingo Molnar

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=46B67992.1080503@bigpond.net.au \
    --to=pwil3058@bigpond.net.au \
    --cc=DBahi@novell.com \
    --cc=MKohari@novell.com \
    --cc=SDietrich@novell.com \
    --cc=abogani@texware.it \
    --cc=dsaxena@plexity.net \
    --cc=dwalker@mvista.com \
    --cc=ghaskins@novell.com \
    --cc=jim.houston@ccur.com \
    --cc=joe.korty@ccur.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rt-users@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=rostedt@goodmis.org \
    --cc=tglx@linutronix.de \
    --cc=williams@redhat.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