From: Jeff Dike <jdike@addtoit.com>
To: "Christopher S. Aker" <caker@theshore.net>
Cc: user-mode-linux-devel@lists.sourceforge.net
Subject: [uml-devel] Re: uml-patch-2.6.3-rc2-1, RTC, CPU > 2.1 Ghz
Date: Fri, 13 Feb 2004 23:00:52 -0500 [thread overview]
Message-ID: <20040214040052.GB5007@ccure.user-mode-linux.org> (raw)
In-Reply-To: <008201c3f29d$30a1e750$0201a8c0@hawk>
On Fri, Feb 13, 2004 at 07:52:20PM -0600, Christopher S. Aker wrote:
> Looking at uml-patch-2.6.3-rc2-1, I noticed it needs the RTC fix (mhz to unsigned
> long long) for CPUs > 2.1Ghz This is just a friendly reminder to make sure that
> change makes it into your 2.6 tree (looks good on 2.4)..
Right. Generic fixes (2.4 and 2.6) usually start off in my 2.4 tree, then
get migrated into my 2.6 tree when I get around to it.
Jeff
-------------------------------------------------------
SF.Net is sponsored by: Speed Start Your Linux Apps Now.
Build and deploy apps & Web services for Linux with
a free DVD software kit from IBM. Click Now!
http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel
prev parent reply other threads:[~2004-02-14 3:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-12 6:46 [uml-devel] [inkblot@movealong.org: Bug#224215: incorrect /proc timestamp] Matt Zimmerman
2004-02-14 0:43 ` Jeff Dike
2004-02-14 1:52 ` [uml-devel] uml-patch-2.6.3-rc2-1, RTC, CPU > 2.1 Ghz Christopher S. Aker
2004-02-14 4:00 ` Jeff Dike [this message]
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=20040214040052.GB5007@ccure.user-mode-linux.org \
--to=jdike@addtoit.com \
--cc=caker@theshore.net \
--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