From: Artem Bityutskiy <dedekind1@gmail.com>
To: Richard Weinberger <richard@nod.at>
Cc: Greg KH <greg@kroah.com>,
"linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>,
jean-philippe francois <jp.francois@cynove.com>,
stable@vger.kernel.org
Subject: Re: Ubi patch proposition for 3.10.y
Date: Mon, 08 Sep 2014 12:47:10 +0300 [thread overview]
Message-ID: <1410169630.10764.109.camel@sauron.fi.intel.com> (raw)
In-Reply-To: <5407914B.302@nod.at>
On Thu, 2014-09-04 at 00:08 +0200, Richard Weinberger wrote:
> e8c235b UBI: init_volumes: Ignore volumes with no LEBs
> 44305eb UBI: fastmap: do not miss bit-flips
> 604b592 UBI: fix rb_tree node comparison in add_map
> 5547fec UBI: fix some use after free bugs
> fe24c6e UBI: Fix memory leak in ubi_attach_fastmap() error path
> c22301a UBI: fastmap: fix backward compatibility with image_seq
> 4b3e0a2 UBI: Call scan_all() with correct offset in error case
> f240dca UBI: Fix error path in scan_pool()
> fb10e4d UBI: fix refill_wl_user_pool()
> 8930fa5 UBI: Fix invalidate_fastmap()
The entire "fastmap" feature is classified as "experimental", why would
we need to be submit these to stable? I mean, we do not treat the
feature as bullet proof anyway yet.
--
Best Regards,
Artem Bityutskiy
next prev parent reply other threads:[~2014-09-08 9:47 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-29 12:26 Ubi patch proposition for 3.10.y jean-philippe francois
2014-09-01 21:51 ` Richard Weinberger
2014-09-01 22:02 ` Greg KH
2014-09-03 22:08 ` Richard Weinberger
2014-09-08 9:47 ` Artem Bityutskiy [this message]
2014-09-08 9:51 ` Richard Weinberger
2014-09-08 9:58 ` Artem Bityutskiy
2014-09-08 10:04 ` Willy Tarreau
2014-09-08 10:13 ` Richard Genoud
2014-09-08 10:13 ` Artem Bityutskiy
2014-09-08 10:53 ` Willy Tarreau
2014-09-08 11:03 ` jean-philippe francois
2014-09-08 10:16 ` Richard Weinberger
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=1410169630.10764.109.camel@sauron.fi.intel.com \
--to=dedekind1@gmail.com \
--cc=greg@kroah.com \
--cc=jp.francois@cynove.com \
--cc=linux-mtd@lists.infradead.org \
--cc=richard@nod.at \
--cc=stable@vger.kernel.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