linux-mmc.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Avri Altman <Avri.Altman@wdc.com>
To: Patrick Oppenlander <patrick.oppenlander@gmail.com>,
	"linux-mmc@vger.kernel.org" <linux-mmc@vger.kernel.org>
Subject: RE: mmc-utils mmc tool reports incorrect cache size
Date: Thu, 13 Feb 2020 07:35:13 +0000	[thread overview]
Message-ID: <MN2PR04MB6991B0F4431E56BA0C64927AFC1A0@MN2PR04MB6991.namprd04.prod.outlook.com> (raw)
In-Reply-To: <CAEg67GnNdOBgq=gVH9fDTwT0-KM5+3g8Do5ZnW+y6Q0AY_302A@mail.gmail.com>

Patrick hi,
Yes, it is helpful, but you need to submit your patch in a way it can be reviewed.
Maybe you can look in https://www.kernel.org/doc/html/v5.5/process/5.Posting.html?highlight=submit%20patches#
For more info.

Thanks,
Avri

> -----Original Message-----
> From: linux-mmc-owner@vger.kernel.org <linux-mmc-
> owner@vger.kernel.org> On Behalf Of Patrick Oppenlander
> Sent: Wednesday, February 12, 2020 11:35 PM
> To: linux-mmc@vger.kernel.org
> Subject: mmc-utils mmc tool reports incorrect cache size
> 
> CAUTION: This email originated from outside of Western Digital. Do not click
> on links or open attachments unless you recognize the sender and know that
> the content is safe.
> 
> 
> Hi,
> 
> I recently noticed that 'mmc' reports cache size incorrectly. The unit
> in the extended CSD is kilobits rather than kilobytes, so for a
> display unit of 'KiB' it needs to be scaled appropriately.
> Alternatively the unit could change to Kibit, but I think that's less
> helpful.
> 
> I've attached a patch which fixes the issue & includes references to
> the relevant parts of the JEDEC standard.
> 
> Hope someone finds this helpful,
> 
> Patrick

  reply	other threads:[~2020-02-13  7:35 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-12 21:34 mmc-utils mmc tool reports incorrect cache size Patrick Oppenlander
2020-02-13  7:35 ` Avri Altman [this message]
2020-02-13 22:14   ` Patrick Oppenlander

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=MN2PR04MB6991B0F4431E56BA0C64927AFC1A0@MN2PR04MB6991.namprd04.prod.outlook.com \
    --to=avri.altman@wdc.com \
    --cc=linux-mmc@vger.kernel.org \
    --cc=patrick.oppenlander@gmail.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;
as well as URLs for NNTP newsgroup(s).