From: Timur Tabi <timur@freescale.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] allow print_size to print large numbers on 32-bit systems
Date: Mon, 12 Apr 2010 13:30:54 -0500 [thread overview]
Message-ID: <4BC366DE.1000808@freescale.com> (raw)
In-Reply-To: <4BC364F1.1030008@freescale.com>
Scott Wood wrote:
> It's used often enough (including many places in U-Boot already), and
> there's typically enough context, that I don't think too many would be
> confused.
I guess my objection that I think the whole idea is stupid doesn't count for much? I'll do it if Wolfgang insists, but I honestly believe that there was no confusion and that the introduction of KiB and its ilk just makes things worse, not better. No one is going to compare memory sizes in kilobytes with distances in kilometers and get confused.
--
Timur Tabi
Linux kernel developer at Freescale
next prev parent reply other threads:[~2010-04-12 18:30 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-30 23:02 [U-Boot] [PATCH] [v3] fix print_size printing fractional gigabyte numbers on 32-bit platforms Timur Tabi
2010-03-30 23:02 ` [U-Boot] [PATCH] allow print_size to print large numbers on 32-bit systems Timur Tabi
2010-04-09 20:22 ` Wolfgang Denk
2010-04-09 20:27 ` Timur Tabi
2010-04-09 20:40 ` Wolfgang Denk
2010-04-12 16:12 ` Timur Tabi
2010-04-12 16:16 ` Nick Thompson
2010-04-12 16:21 ` Timur Tabi
2010-04-12 16:27 ` Nick Thompson
2010-04-12 18:02 ` Wolfgang Denk
2010-04-12 17:59 ` Wolfgang Denk
2010-04-12 18:03 ` Timur Tabi
2010-04-12 18:20 ` Wolfgang Denk
2010-04-12 18:22 ` Scott Wood
2010-04-12 18:30 ` Timur Tabi [this message]
2010-04-12 18:50 ` Wolfgang Denk
2010-04-12 19:10 ` Timur Tabi
2010-04-12 19:26 ` Scott Wood
2010-04-09 20:10 ` [U-Boot] [PATCH] [v3] fix print_size printing fractional gigabyte numbers on 32-bit platforms Wolfgang Denk
2010-04-12 16:04 ` Timur Tabi
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=4BC366DE.1000808@freescale.com \
--to=timur@freescale.com \
--cc=u-boot@lists.denx.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox