public inbox for linux-mmc@vger.kernel.org
 help / color / mirror / Atom feed
From: James Nuss <jamesnuss@nanometrics.ca>
To: linux-mmc@vger.kernel.org
Cc: linux-kernel@vger.kernel.org
Subject: [PATCH 0/7] fix bugs in write_reliability and enh_area set commands + more extcsd parsing
Date: Tue,  9 Oct 2018 13:31:04 -0400	[thread overview]
Message-ID: <cover.1539103468.git.jamesnuss@nanometrics.ca> (raw)

[PATCH 1-3] just introduce further parsing and human-readable output of eMMC 5.0+ fields in the extcsd:
  mmc-utils: interpret OPTIMAL_*_SIZE fields in extcsd
  mmc-utils: treat FIRMWARE_VERSION as binary field instead of string
  mmc-utils: interpret DEVICE_VERSION when printing extcsd

[PATCH 4-5] are critical bug fixes for the current version. This addresses concerns previously raised in threads wrt write-reliability setting:
https://www.spinics.net/lists/linux-mmc/msg41952.html
https://www.spinics.net/lists/linux-mmc/msg43171.html

[PATCH 6] is a critical bug fix for the current version to allow setting of enhanced and extended attributes on multiple partitions.

[PATCH 7] is a version up-rev:
  mmc-utils: update version number to 0.2

James Nuss (7):
  mmc-utils: interpret OPTIMAL_*_SIZE fields in extcsd
  mmc-utils: treat FIRMWARE_VERSION as binary field instead of string
  mmc-utils: interpret DEVICE_VERSION when printing extcsd
  mmc-utils: Introduce write_reliability set_register command
  mmc-utils: remove write_reliability set command
  mmc-utils: discrete commands for enhanced and extended attribute
  mmc-utils: update version number to 0.2

 mmc.c      |  52 ++++++++++---
 mmc.h      |  14 +++-
 mmc_cmds.c | 243 ++++++++++++++++++++++++++++++++++++++++++++-----------------
 mmc_cmds.h |   6 +-
 4 files changed, 235 insertions(+), 80 deletions(-)

-- 
2.7.4


-- 
This message is intended exclusively for the individual or entity to which 
it is addressed. This communication may contain information that is 
proprietary, privileged, confidential or otherwise legally exempt from 
disclosure. If you are not the named addressee, or have been inadvertently 
and erroneously referenced in the address line, you are not authorized to 
read, print, retain, copy or disseminate this message or any part of it. If 
you have received this message in error, please notify the sender 
immediately by e-mail and delete all copies of the message.

             reply	other threads:[~2018-10-09 17:31 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-09 17:31 James Nuss [this message]
2018-10-09 17:31 ` [PATCH 1/7] mmc-utils: interpret OPTIMAL_*_SIZE fields in extcsd James Nuss
2018-10-10  8:40   ` Avri Altman
2018-10-09 17:31 ` [PATCH 2/7] mmc-utils: treat FIRMWARE_VERSION as binary field instead of string James Nuss
2018-10-10  8:43   ` Avri Altman
2018-10-10 13:52     ` James Nuss
2018-10-10 13:59       ` Avri Altman
2018-10-09 17:31 ` [PATCH 3/7] mmc-utils: interpret DEVICE_VERSION when printing extcsd James Nuss
2018-10-09 17:31 ` [PATCH 4/7] mmc-utils: Introduce write_reliability set_register command James Nuss
2018-10-09 17:31 ` [PATCH 5/7] mmc-utils: remove write_reliability set command James Nuss
2018-10-09 17:31 ` [PATCH 6/7] mmc-utils: discrete commands for enhanced and extended attribute setting James Nuss
2018-10-09 17:31 ` [PATCH 7/7] mmc-utils: update version number to 0.2 James Nuss

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=cover.1539103468.git.jamesnuss@nanometrics.ca \
    --to=jamesnuss@nanometrics.ca \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mmc@vger.kernel.org \
    /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