public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Brian Norris <computersforpeace@gmail.com>
To: Ezequiel Garcia <ezequiel.garcia@free-electrons.com>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	linux-mtd@lists.infradead.org, Pekon Gupta <pekon@ti.com>
Subject: Re: [PATCH v3 0/3] mtd: Add sysfs entries and account BBT blocks properly
Date: Tue, 8 Jul 2014 18:43:07 -0700	[thread overview]
Message-ID: <20140709014307.GF7537@ld-irv-0074> (raw)
In-Reply-To: <1403618152-4515-1-git-send-email-ezequiel.garcia@free-electrons.com>

On Tue, Jun 24, 2014 at 10:55:49AM -0300, Ezequiel Garcia wrote:
> Here's a new round of the patchset to add sysfs entries for the ECC stats
> struct fields. See the discussion around previous version for context:
> 
> http://lists.infradead.org/pipermail/linux-mtd/2014-March/052804.html
> 
> Changes from v2:
> 
>   * As suggested by Pekon Gupta, use "ecc_failures" instead of
>     "uncorrectable_errors".
> 
>   * Added documentation for the new sysfs ABI as requested by Greg KH.
> 
> Changes from v1:
> 
>   * As agreed I've added a sysfs file per field to replace the ecc_stats
>     sysfs file. The current proposal follows the "one file per value" sysfs
>     rule, adding the following device attributes:
>     - corrected_bits (ecc_stats.corrected)
>     - uncorrectable_errors (ecc_stats.failed)
>     - bad_blocks (ecc_stats.badblocks)
>     - bbt_blocks (ecc_stats.bbtblocks)
> 
>   * Following Brian's request, added small wrapper nand_block_isreserved()
>     that checks if the NAND has a bad block table before querying the number
>     of reserved blocks.
> 
>   * Finally, this new series drops patch: "nand: Account the blocks used by
>     the BBT in the ecc_stats". It's not yet clear how to best deal with the
>     current inconsistencies in MTD master and partition handling.
> 
> The first patch adds the sysfs entries. The rest of the patches fixes the
> bbtblock accounting and allows to keep track of the reserved blocks correctly.
> 
> This is a very old issue, probably around since the dawn of time,
> and nobody seemed to care much about it. However, with the introduction of
> the sysfs access, it's easier to access this stats and easier to
> see the issue.

Pushed to l2-mtd.git, with the small tweaks I noted for patch 1. Thanks!

Brian

      parent reply	other threads:[~2014-07-09  1:43 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-24 13:55 [PATCH v3 0/3] mtd: Add sysfs entries and account BBT blocks properly Ezequiel Garcia
2014-06-24 13:55 ` [PATCH v3 1/3] mtd: Add sysfs attributes to expose the ECC stats fields Ezequiel Garcia
2014-07-09  1:36   ` Brian Norris
2014-06-24 13:55 ` [PATCH v3 2/3] mtd: Introduce mtd_block_isreserved() Ezequiel Garcia
2014-06-24 13:55 ` [PATCH v3 3/3] mtd: Account for BBT blocks when a partition is being allocated Ezequiel Garcia
2014-07-01 10:32 ` [PATCH v3 0/3] mtd: Add sysfs entries and account BBT blocks properly Gupta, Pekon
2014-07-09  1:43 ` Brian Norris [this message]

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=20140709014307.GF7537@ld-irv-0074 \
    --to=computersforpeace@gmail.com \
    --cc=ezequiel.garcia@free-electrons.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-mtd@lists.infradead.org \
    --cc=pekon@ti.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