From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: James Bottomley <James.Bottomley@hansenpartnership.com>,
Matt Fleming <matt@codeblueprint.co.uk>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, "H . Peter Anvin" <hpa@zytor.com>,
linux-efi@vger.kernel.org,
Rasmus Villemoes <linux@rasmusvillemoes.dk>,
Andrew Morton <akpm@linux-foundation.org>,
"linux-kernel @ vger . kernel . org"
<linux-kernel@vger.kernel.org>
Cc: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Subject: [PATCH v3 0/4] x86/efi: use binary units when printing
Date: Sat, 23 Jan 2016 16:55:09 +0200 [thread overview]
Message-ID: <1453560913-134672-1-git-send-email-andriy.shevchenko@linux.intel.com> (raw)
The patch series exports the arrays of binary and decimal units as it's
described by IEC.
First user of it is EFI code which would print sizes and other values using
binary prefix.
James, is this now okay to you?
Matt, I suppose we need to update the stuff in your tree.
Since v2:
- address James comment (don't nail array size)
- fix a title and commit message for patch 3 to be in align with the change
Andy Shevchenko (3):
lib/string_helpers: export string_units_{2,10} for others
lib/string_helpers: fix indentation in few places
x86/efi: Use proper units in efi_find_mirror()
Robert Elliott (1):
x86/efi: print size in binary units in efi_print_memmap
arch/x86/platform/efi/efi.c | 27 ++++++++++++++++++---------
include/linux/string_helpers.h | 3 +++
lib/string_helpers.c | 26 ++++++++++++++------------
3 files changed, 35 insertions(+), 21 deletions(-)
--
2.7.0.rc3
next reply other threads:[~2016-01-23 14:55 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-23 14:55 Andy Shevchenko [this message]
2016-01-23 14:55 ` [PATCH v3 1/4] lib/string_helpers: export string_units_{2,10} for others Andy Shevchenko
2016-01-23 16:14 ` James Bottomley
2016-01-23 16:58 ` Andy Shevchenko
2016-01-23 14:55 ` [PATCH v3 2/4] lib/string_helpers: fix indentation in few places Andy Shevchenko
2016-01-23 14:55 ` [PATCH v3 3/4] x86/efi: print size in binary units in efi_print_memmap Andy Shevchenko
2016-01-23 16:44 ` James Bottomley
2016-01-23 17:18 ` Andy Shevchenko
2016-01-23 18:03 ` James Bottomley
2016-01-25 8:31 ` Andy Shevchenko
2016-01-25 15:25 ` James Bottomley
2016-01-23 18:12 ` James Bottomley
2016-01-23 20:29 ` One Thousand Gnomes
2016-01-23 20:43 ` H. Peter Anvin
2016-01-25 18:02 ` Elliott, Robert (Persistent Memory)
2016-01-25 18:56 ` James Bottomley
2016-01-25 19:28 ` Andy Shevchenko
2016-01-25 19:45 ` James Bottomley
2016-01-25 20:01 ` Andy Shevchenko
2016-01-25 20:18 ` James Bottomley
2016-01-25 20:37 ` Elliott, Robert (Persistent Memory)
2016-01-26 11:50 ` Matt Fleming
2016-01-26 11:59 ` Andy Shevchenko
2016-01-28 9:29 ` Matt Fleming
2016-01-28 11:15 ` Andy Shevchenko
2016-01-25 20:44 ` James Bottomley
2016-01-23 14:55 ` [PATCH v3 4/4] x86/efi: Use proper units in efi_find_mirror() Andy Shevchenko
2016-01-23 16:34 ` [PATCH v3 0/4] x86/efi: use binary units when printing James Bottomley
2016-01-23 17:20 ` Andy Shevchenko
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=1453560913-134672-1-git-send-email-andriy.shevchenko@linux.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=James.Bottomley@hansenpartnership.com \
--cc=akpm@linux-foundation.org \
--cc=hpa@zytor.com \
--cc=linux-efi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@rasmusvillemoes.dk \
--cc=matt@codeblueprint.co.uk \
--cc=mingo@redhat.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).