public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Artem Bityutskiy <dedekind1@gmail.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-mtd <linux-mtd@lists.infradead.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: [GIT PULL] UBI fixes for 3.16-rc6
Date: Fri, 18 Jul 2014 14:21:11 +0300	[thread overview]
Message-ID: <1405682471.28207.1.camel@sauron.fi.intel.com> (raw)

Hi Linus,

please, pull a couple of UBI fixes.

The following changes since commit a497c3ba1d97fc69c1e78e7b96435ba8c2cb42ee:

  Linux 3.16-rc2 (2014-06-21 19:02:54 -1000)

are available in the git repository at:

  git://git.infradead.org/linux-ubifs.git tags/upstream-3.16-rc6

for you to fetch changes up to 44305ebde243a7cce2c592cc89afe5041d8bf884:

  UBI: fastmap: do not miss bit-flips (2014-07-16 08:32:00 +0300)

----------------------------------------------------------------
Two UBI fastmap-related fixes for v3.16:

1. Fix UBI fastmap support which we broke in 3.16-rc1 by reversing the
   volumes RB-tree sorting criteria.
2. Make sure that we scrub all PEBs where we see bit-flips - we were missing
   some of them when the fastmap feature was enabled.

----------------------------------------------------------------
Brian Norris (1):
      UBI: fastmap: do not miss bit-flips

Heiko Schocher (1):
      UBI: fix the volumes tree sorting criteria

 drivers/mtd/ubi/fastmap.c | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

-- 
Best Regards,
Artem Bityutskiy

                 reply	other threads:[~2014-07-18 11:21 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=1405682471.28207.1.camel@sauron.fi.intel.com \
    --to=dedekind1@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mtd@lists.infradead.org \
    --cc=torvalds@linux-foundation.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