From: Jeff Dike <jdike@addtoit.com>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: linux-kernel@vger.kernel.org,
"Christopher S. Aker" <caker@theshore.net>,
user-mode-linux-devel@lists.sourceforge.net
Subject: Re: [uml-devel] Re: non-scalar ktime addition and subtraction broken
Date: Fri, 2 Jun 2006 11:19:16 -0400 [thread overview]
Message-ID: <20060602151916.GC4708@ccure.user-mode-linux.org> (raw)
In-Reply-To: <1149231262.20582.119.camel@localhost.localdomain>
On Fri, Jun 02, 2006 at 08:54:22AM +0200, Thomas Gleixner wrote:
> NAK. ktime_t is defined that ist must be normalized the same way as
> timespecs. The nsec part must be >= 0 and < NSEC_PER_SEC. Fix the part
> which is feeding non normalized values.
Aha, that would be me, initializing wall_to_monotonic incorrectly. Thanks
for the clue.
Jeff
next prev parent reply other threads:[~2006-06-02 15:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-02 3:08 non-scalar ktime addition and subtraction broken Jeff Dike
2006-06-02 6:54 ` Thomas Gleixner
2006-06-02 15:19 ` Jeff Dike [this message]
2006-06-02 18:28 ` [uml-devel] " Blaisorblade
2006-06-02 21:34 ` Jeff Dike
2006-06-04 15:04 ` Blaisorblade
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=20060602151916.GC4708@ccure.user-mode-linux.org \
--to=jdike@addtoit.com \
--cc=caker@theshore.net \
--cc=linux-kernel@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=user-mode-linux-devel@lists.sourceforge.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