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] UBIFS changes for 3.14-rc1
Date: Thu, 30 Jan 2014 14:46:17 +0200 [thread overview]
Message-ID: <1391085977.28238.32.camel@sauron.fi.intel.com> (raw)
Hi Linus,
The following changes since commit 802eee95bde72fd0cd0f3a5b2098375a487d1eda:
Linux 3.13-rc6 (2013-12-29 16:01:33 -0800)
are available in the git repository at:
git://git.infradead.org/linux-ubifs.git tags/upstream-3.14-rc1
for you to fetch changes up to 2c7ca5cc3624e05a5235f70039adce30725972d6:
UBI: avoid program operation on NOR flash after erasure interrupted (2014-01-09 18:25:38 +0200)
----------------------------------------------------------------
* Improve the NOR erasure quirk - now it tries to do as little writes as
possible, because the eraseblock may be in an "unstable" state and write
operation sometimes causes NOR chip lock-ups.
* Both UBI and UBIFS changes are now maintainer in one single tree, because the
amount of changes dropped significantly.
----------------------------------------------------------------
Artem Bityutskiy (1):
MAINTAINERS: keep UBI and UBIFS stuff in the same tree
Julia Lawall (1):
UBI: fix error return code
Qi Wang 王起 (qiwang) (1):
UBI: avoid program operation on NOR flash after erasure interrupted
MAINTAINERS | 2 +-
drivers/mtd/ubi/attach.c | 4 +++-
drivers/mtd/ubi/build.c | 4 +++-
drivers/mtd/ubi/io.c | 54 ++++++++++++++++++++++--------------------------------
4 files changed, 29 insertions(+), 35 deletions(-)
--
Best Regards,
Artem Bityutskiy
reply other threads:[~2014-01-30 12:46 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=1391085977.28238.32.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
all inboxes | Powered by JetHome®