From: "H. Peter Anvin" <hpa@zytor.com>
To: Chris Snook <csnook@redhat.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Avoid overflows in kernel/time.c
Date: Thu, 29 Nov 2007 19:04:36 -0800 [thread overview]
Message-ID: <474F7DC4.8000607@zytor.com> (raw)
In-Reply-To: <474F6E7A.3090705@redhat.com>
Chris Snook wrote:
> H. Peter Anvin wrote:
>> NOTE: This patch uses a bc(1) script to compute the appropriate
>> constants.
>
> Perhaps dc would be more appropriate? That's included in busybox.
>
Perhaps it would, but I think there is more variability between dc
implementations -- consider if the busybox version is broken, for eample.
Either way, how many people compile their kernels in a busybox environment?
Anyway, I don't think compiling bc is hard on anything which has a C
compiler.
-hpa
next prev parent reply other threads:[~2007-11-30 3:05 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-30 0:19 [PATCH] Avoid overflows in kernel/time.c H. Peter Anvin
2007-11-30 1:54 ` Andrew Morton
2007-11-30 3:01 ` H. Peter Anvin
2007-11-30 3:27 ` [PATCH] Documentation/Changes -> Documentation/Requirements H. Peter Anvin
2007-11-30 3:32 ` [PATCH] Documentation/Changes -> Documentation/Requirements (resend without truncated comment text) H. Peter Anvin
2007-11-30 7:16 ` Jarek Poplawski
2007-11-30 17:40 ` H. Peter Anvin
2007-11-30 17:47 ` [PATCH] Documentation/Changes -> Documentation/Requirements H. Peter Anvin
2007-11-30 18:09 ` Robert P. J. Day
2007-11-30 18:20 ` H. Peter Anvin
2007-11-30 1:59 ` [PATCH] Avoid overflows in kernel/time.c Chris Snook
2007-11-30 3:04 ` H. Peter Anvin [this message]
2007-11-30 3:40 ` Arjan van de Ven
2007-11-30 3:54 ` H. Peter Anvin
2007-12-02 18:37 ` Pavel Machek
2007-12-03 14:53 ` Jan Engelhardt
2007-12-10 16:37 ` H. Peter Anvin
2007-12-01 0:33 ` Adrian Bunk
2007-12-01 4:19 ` H. Peter Anvin
2007-12-01 13:20 ` Alan Cox
2007-12-01 13:33 ` Alan Cox
2007-12-02 1:53 ` H. Peter Anvin
2007-12-07 0:22 ` Jeremy Fitzhardinge
2007-12-04 11:29 ` Andrew Morton
2007-12-10 16:46 ` H. Peter Anvin
2007-12-10 18:59 ` H. Peter Anvin
2007-12-10 22:04 ` Andrew Morton
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=474F7DC4.8000607@zytor.com \
--to=hpa@zytor.com \
--cc=akpm@linux-foundation.org \
--cc=csnook@redhat.com \
--cc=linux-kernel@vger.kernel.org \
/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.