From: Anuradha Ratnaweera <anuradha@gnu.org>
To: Tim Schmielau <tim@physik3.uni-rostock.de>
Cc: Linus Torvalds <torvalds@transmeta.com>, linux-kernel@vger.kernel.org
Subject: Re: [patch] enable uptime display > 497 days on 32 bit
Date: Thu, 22 Nov 2001 12:48:08 +0600 [thread overview]
Message-ID: <20011122124808.A3561@bee.lk> (raw)
In-Reply-To: <Pine.LNX.4.30.0111212104070.24469-100000@gans.physik3.uni-rostock.de>
In-Reply-To: <Pine.LNX.4.30.0111212104070.24469-100000@gans.physik3.uni-rostock.de>; from tim@physik3.uni-rostock.de on Wed, Nov 21, 2001 at 10:23:07PM +0100
On Wed, Nov 21, 2001 at 10:23:07PM +0100, Tim Schmielau wrote:
>
> This patch makes 32 bit boxes export correct uptime to userland after
> jiffies wraparound...
Great patch! Was wondering why no linux boxes turned up on the "longest
uptime" lists at netcraft.com.
Anuradha
--
Debian GNU/Linux (kernel 2.4.13)
Good leaders being scarce, following yourself is allowed.
prev parent reply other threads:[~2001-11-22 6:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-21 21:23 [patch] enable uptime display > 497 days on 32 bit Tim Schmielau
2001-11-21 21:39 ` [patch] config option to debug jiffies wraps Tim Schmielau
2001-11-22 6:48 ` Anuradha Ratnaweera [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=20011122124808.A3561@bee.lk \
--to=anuradha@gnu.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tim@physik3.uni-rostock.de \
--cc=torvalds@transmeta.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