From: Andi Kleen <ak@suse.de>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: mingo@elte.hu, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] [2/5] Use 2000 offset for 32bit kernels
Date: Wed, 20 Feb 2008 11:23:23 +0100 [thread overview]
Message-ID: <200802201123.23830.ak@suse.de> (raw)
In-Reply-To: <alpine.LFD.1.00.0802201049310.7583@apollo.tec.linutronix.de>
On Wednesday 20 February 2008 11:07:02 Thomas Gleixner wrote:
> On Sat, 16 Feb 2008, Thomas Gleixner wrote:
> > On Sat, 9 Feb 2008, Andi Kleen wrote:
> > >
> > > We know it is already after 2000.
> > >
> > > This extends the effective lifetime of 32bit systems by 8 years:
> > > from 2030 to 2038.
>
> Could you please explain what magic math does the 2030 -> 2038
> extension ?
Hmm, yes on rechecking I also don't know how I got the original
conclusion.
-Andi
next prev parent reply other threads:[~2008-02-20 10:23 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-09 15:16 [PATCH] [1/5] Only do century BCD conversion when we know the RTC is BCD Andi Kleen
2008-02-09 15:16 ` [PATCH] [2/5] Use 2000 offset for 32bit kernels Andi Kleen
2008-02-16 19:24 ` Thomas Gleixner
2008-02-20 10:07 ` Thomas Gleixner
2008-02-20 10:23 ` Andi Kleen [this message]
2008-02-09 15:16 ` [PATCH] [3/5] Add warning when RTC clock reports binary Andi Kleen
2008-02-16 19:38 ` Thomas Gleixner
2008-02-09 15:17 ` [PATCH] [4/5] Fix wrong comment Andi Kleen
2008-02-09 15:17 ` [PATCH] [5/5] Enable ACPI extended century handling for 32bit too v2 Andi Kleen
2008-02-16 19:38 ` Thomas Gleixner
2008-02-11 8:30 ` [PATCH] [1/5] Only do century BCD conversion when we know the RTC is BCD Thomas Gleixner
2008-02-11 8:56 ` Andi Kleen
2008-02-11 22:08 ` Thomas Gleixner
2008-02-11 22:15 ` Andi Kleen
2008-02-12 20:36 ` Thomas Gleixner
2008-02-13 13:49 ` Andi Kleen
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=200802201123.23830.ak@suse.de \
--to=ak@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=tglx@linutronix.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.