From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: "Toralf Förster" <toralf.foerster@gmx.de>, linux-scsi@vger.kernel.org
Cc: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: small diff in reported GiB size of an SSD
Date: Mon, 29 Feb 2016 07:49:07 -0800 [thread overview]
Message-ID: <1456760947.2390.9.camel@HansenPartnership.com> (raw)
In-Reply-To: <56D44840.5080405@gmx.de>
On Mon, 2016-02-29 at 13:31 +0000, Toralf Förster wrote:
> I'm just curious about this diff in dmesg output between 4.3.2 and
> 4.3.3 at a 64 bit Gentoo hardened system:
>
> $ diff dmesg-4.4.[23]-hardened | grep logical
> < sd 0:0:0:0: [sda] 468862128 512-byte logical blocks: (240 GB/223
> GiB)
> > sd 0:0:0:0: [sda] 468862128 512-byte logical blocks: (240 GB/224
> > GiB)
>
commit 564b026fbd0d28e9f70fb3831293d2922bb7855b
Author: James Bottomley <JBottomley@Odin.com>
Date: Wed Jan 20 14:58:29 2016 -0800
string_helpers: fix precision loss for some inputs
James
next prev parent reply other threads:[~2016-02-29 15:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-29 13:31 small diff in reported GiB size of an SSD Toralf Förster
2016-02-29 15:49 ` James Bottomley [this message]
2016-02-29 15:53 ` Toralf Förster
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=1456760947.2390.9.camel@HansenPartnership.com \
--to=james.bottomley@hansenpartnership.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=toralf.foerster@gmx.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