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 changes for 3.13-rc1
Date: Tue, 12 Nov 2013 14:33:17 +0200 [thread overview]
Message-ID: <1384259597.15824.136.camel@sauron.fi.intel.com> (raw)
Hi Linus,
The following changes since commit b36f4be3de1b123d8601de062e7dbfc904f305fb:
Linux 3.11-rc6 (2013-08-18 14:36:53 -0700)
are available in the git repository at:
git://git.infradead.org/linux-ubi.git tags/upstream-3.13-rc1
for you to fetch changes up to ae0d146955665411a6d4cea5e0893429cfc52807:
UBI: Add some asserts to ubi_attach_fastmap() (2013-10-03 19:42:51 +0300)
----------------------------------------------------------------
A bunch of fixes for the fastmap feature, which is still new and rather
experimental. It looks like it starts getting more users. No significant
changes for the "classical" non-fastmap UBI.
----------------------------------------------------------------
Richard Genoud (2):
UBI: fastmap: fix backward compatibility with image_seq
UBI: simplify image sequence test
Richard Weinberger (7):
UBI: Fix PEB leak in wear_leveling_worker()
UBI: Fix invalidate_fastmap()
UBI: fix refill_wl_user_pool()
UBI: Fix error path in scan_pool()
UBI: Call scan_all() with correct offset in error case
UBI: Fix memory leak in ubi_attach_fastmap() error path
UBI: Add some asserts to ubi_attach_fastmap()
drivers/mtd/ubi/attach.c | 11 ++++++-----
drivers/mtd/ubi/fastmap.c | 46 ++++++++++++++++++++++++++++++++++++++--------
drivers/mtd/ubi/wl.c | 7 +++----
3 files changed, 47 insertions(+), 17 deletions(-)
--
Best Regards,
Artem Bityutskiy
next reply other threads:[~2013-11-12 12:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-12 12:33 Artem Bityutskiy [this message]
-- strict thread matches above, loose matches on Subject: below --
2013-11-12 12:33 [GIT PULL] UBI changes for 3.13-rc1 Artem Bityutskiy
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=1384259597.15824.136.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;
as well as URLs for NNTP newsgroup(s).