public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Richard Weinberger <richard@nod.at>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: "linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: [GIT PULL] UBI/UBIFS fixes for 4.7-rc5
Date: Thu, 23 Jun 2016 10:21:13 +0200	[thread overview]
Message-ID: <576B9BF9.8000506@nod.at> (raw)

Linus,

The following changes since commit c0a1ecb9f4e208f4b75d88fa9669748e3fd705ab:

  gpio: make library immune to error pointers (2016-06-23 00:29:31 +0200)

are available in the git repository at:

  git://git.infradead.org/linux-ubifs.git tags/upstream-4.7-rc5

for you to fetch changes up to 4ac1c17b2044a1b4b2fbed74451947e905fc2992:

  UBIFS: Implement ->migratepage() (2016-06-23 00:29:53 +0200)

----------------------------------------------------------------
This pull requests contains fixes for two critical bugs in UBI and UBIFS:
1. Fixes the possibility of losing data upon a power cut when UBI tries
   to recover from a write error.
2. Fixes page migration on UBIFS. It turned out that the default page
   migration function is not suitable for UBIFS.

----------------------------------------------------------------
Kirill A. Shutemov (1):
      UBIFS: Implement ->migratepage()

Richard Weinberger (2):
      ubi: Make recover_peb power cut aware
      mm: Export migrate_page_move_mapping and migrate_page_copy

 drivers/mtd/ubi/eba.c | 22 +++++++++++++++-------
 fs/ubifs/file.c       | 24 ++++++++++++++++++++++++
 mm/migrate.c          |  2 ++
 3 files changed, 41 insertions(+), 7 deletions(-)

                 reply	other threads:[~2016-06-23  8: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=576B9BF9.8000506@nod.at \
    --to=richard@nod.at \
    --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