From: Willy Tarreau <w@1wt.eu>
To: Artem Bityutskiy <dedekind1@gmail.com>
Cc: richard@nod.at,
"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, 8 Sep 2014 12:53:59 +0200 [thread overview]
Message-ID: <20140908105359.GB28903@1wt.eu> (raw)
In-Reply-To: <1410171221.10764.132.camel@sauron.fi.intel.com>
On Mon, Sep 08, 2014 at 01:13:41PM +0300, Artem Bityutskiy wrote:
> Well, adding stable tags is does not come for free. Whey you add a
> stable tag, you need to make sure it applies to the older kernel, and
> you need to also pick the possible dependencies. You need test it with
> older kernel.
>
> While in general what you say makes sense, for this specific "fastmap"
> case the maintainers (me and Richard) did not think the overhead is
> worth the benefits.
I understand and am not pressuring anyone to do the backport. Sometimes if
something appears to be clearly broken, for example to the point where data
corruption may result from the use of any feature, a patch to disable the
feature or make it depend on CONFIG_BROKEN might be good as well to warn
users they must not use it because it's too broken.
Regards,
Willy
next prev parent reply other threads:[~2014-09-08 10:54 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
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 [this message]
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=20140908105359.GB28903@1wt.eu \
--to=w@1wt.eu \
--cc=dedekind1@gmail.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