From: hpa@zytor.com
To: Ethan Sommer <e5ten.arch@gmail.com>
Cc: Jonathan Corbet <corbet@lwn.net>,
Federico Vaga <federico.vaga@vaga.pv.it>,
"Chang S. Bae" <chang.seok.bae@intel.com>,
Andrew Morton <akpm@linux-foundation.org>,
Arnd Bergmann <arnd@arndb.de>,
Masahiro Yamada <yamada.masahiro@socionext.com>,
Kieran Bingham <kieran.bingham@ideasonboard.com>,
Ingo Molnar <mingo@kernel.org>, Borislav Petkov <bp@suse.de>,
Mark Rutland <mark.rutland@arm.com>,
John Stultz <john.stultz@linaro.org>,
Kees Cook <keescook@chromium.org>,
Corey Minyard <cminyard@mvista.com>,
Thomas Gleixner <tglx@linutronix.de>,
linux-doc@vger.kernel.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v3] replace timeconst bc script with an sh script
Date: Sun, 03 Nov 2019 19:03:36 -0800 [thread overview]
Message-ID: <EC20169B-26FF-4AC0-AABE-B6FFB0B3AA40@zytor.com> (raw)
In-Reply-To: <CAMEGPiqq1aoVNgezkx5DdQO7Jm2NL+pZzzY-N0AoU=+s470LcQ@mail.gmail.com>
On November 3, 2019 3:57:06 PM PST, Ethan Sommer <e5ten.arch@gmail.com> wrote:
>> The point isn't to make it work *now*, but getting it to *stay* work.
>Since the only thing that can change to affect the outcome of the
>script
>or program is the value of CONFIG_HZ, isn't knowing that it works
>within
>a range of any reasonable values to set CONFIG_HZ to enough to know
>that
>it will stay working? I just tested again using the bc script and my C
>program, and this time I tested every possible value up to 100000, and
>they both still matched output. It doesn't seem like there's something
>that would cause the C program to stop working in the future due to
>precision issues.
No, it's not. Because some time we are going to want to change the way the constants we need, or use them for something else, and be so on.
--
Sent from my Android device with K-9 Mail. Please excuse my brevity.
prev parent reply other threads:[~2019-11-04 3:04 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-20 6:22 [PATCH] " Ethan Sommer
2019-06-20 7:23 ` Kieran Bingham
2019-06-20 8:11 ` [PATCH v2] " Ethan Sommer
2019-06-20 8:25 ` Borislav Petkov
2019-06-20 8:43 ` Ethan Sommer
[not found] ` <CAMEGPiqk5TU=z2_wvMfPuihVc5zOLRrTSVCpLA23k0r-hmAzmg@mail.gmail.com>
2019-06-20 8:45 ` Borislav Petkov
2019-10-29 21:02 ` [PATCH v3] " Ethan Sommer
2019-10-30 11:37 ` Kieran Bingham
2019-10-30 16:26 ` Ethan Sommer
2019-11-02 20:54 ` hpa
2019-11-03 21:56 ` Ethan Sommer
2019-11-03 22:00 ` hpa
2019-11-03 23:57 ` Ethan Sommer
2019-11-04 3:03 ` hpa [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=EC20169B-26FF-4AC0-AABE-B6FFB0B3AA40@zytor.com \
--to=hpa@zytor.com \
--cc=akpm@linux-foundation.org \
--cc=arnd@arndb.de \
--cc=bp@suse.de \
--cc=chang.seok.bae@intel.com \
--cc=cminyard@mvista.com \
--cc=corbet@lwn.net \
--cc=e5ten.arch@gmail.com \
--cc=federico.vaga@vaga.pv.it \
--cc=john.stultz@linaro.org \
--cc=keescook@chromium.org \
--cc=kieran.bingham@ideasonboard.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mingo@kernel.org \
--cc=tglx@linutronix.de \
--cc=yamada.masahiro@socionext.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
all inboxes | Powered by JetHome®