linux-mtd.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Brian Norris <computersforpeace@gmail.com>
To: "Rafał Miłecki" <zajec5@gmail.com>
Cc: linux-mtd@lists.infradead.org, Hauke Mehrtens <hauke@hauke-m.de>
Subject: Re: [PATCH] mtd: bcm47xxpart: don't fail because of bit-flips
Date: Sat, 23 Jan 2016 14:45:24 -0800	[thread overview]
Message-ID: <20160123224524.GF24744@localhost> (raw)
In-Reply-To: <1449397898-28703-1-git-send-email-zajec5@gmail.com>

On Sun, Dec 06, 2015 at 11:31:38AM +0100, Rafał Miłecki wrote:
> Bit-flip errors may occur on NAND flashes and are harmless. Handle them
> gracefully as read content is still reliable and can be parsed.
> 
> Signed-off-by: Rafał Miłecki <zajec5@gmail.com>

Pushed to l2-mtd.git/next

      reply	other threads:[~2016-01-23 22:45 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-06 10:31 [PATCH] mtd: bcm47xxpart: don't fail because of bit-flips Rafał Miłecki
2016-01-23 22:45 ` 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=20160123224524.GF24744@localhost \
    --to=computersforpeace@gmail.com \
    --cc=hauke@hauke-m.de \
    --cc=linux-mtd@lists.infradead.org \
    --cc=zajec5@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).