From: Greg KH <greg@kroah.com>
To: Peter Kieser <peter@kieser.ca>
Cc: Francis Moreau <francis.moro@gmail.com>,
Jens Axboe <axboe@kernel.dk>, Kent Overstreet <kmo@daterainc.com>,
linux-kernel@vger.kernel.org, linux-bcache@vger.kernel.org,
stable <stable@vger.kernel.org>
Subject: Re: [GIT PULL] bcache changes for 3.17
Date: Mon, 8 Sep 2014 08:27:24 -0700 [thread overview]
Message-ID: <20140908152724.GB32677@kroah.com> (raw)
In-Reply-To: <540A44A3.5060502@kieser.ca>
On Fri, Sep 05, 2014 at 04:17:55PM -0700, Peter Kieser wrote:
>
> On 2014-09-05 2:45 PM, Greg KH wrote:
> >Just because a maintainer/developer doesn't want to do anything for the
> >stable kernel releases does_NOT_ mean the code is
> >"unstable/expreimental" at all.
>
> These are more bcache-ate-my-data unstable bugs. It's standard practice to
> backport fixes that cause instability/data corruption to a 'stable' release
> (otherwise, why would it be named 'stable')?
That's fine, but it has nothing to do with what sounded like someone
wanting to go back and mark an older kernel feature as "unsupported".
greg k-h
next prev parent reply other threads:[~2014-09-08 15:32 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-05 4:33 [GIT PULL] bcache changes for 3.17 Kent Overstreet
2014-08-05 16:58 ` Jens Axboe
2014-08-10 7:54 ` Peter Kieser
2014-09-05 7:31 ` Francis Moreau
2014-09-05 14:17 ` Jens Axboe
2014-09-05 14:28 ` Vasiliy Tolstov
2014-09-05 14:30 ` Jens Axboe
2014-09-05 14:44 ` Francis Moreau
2014-09-05 21:46 ` Greg KH
2014-09-05 15:37 ` Eddie Chapman
2014-09-05 16:41 ` Peter Kieser
2014-09-05 17:03 ` Arne Wiebalck
2014-09-05 17:10 ` Jens Axboe
2014-09-05 18:33 ` Kent Overstreet
2014-09-05 18:46 ` Stefan Priebe
2015-02-05 13:40 ` Francis Moreau
2014-09-06 0:33 ` Chuck Ebbert
2014-09-05 21:45 ` Greg KH
2014-09-05 22:21 ` Jens Axboe
2014-09-08 15:26 ` Greg KH
2014-09-05 23:17 ` Peter Kieser
2014-09-08 15:27 ` Greg KH [this message]
2014-09-06 9:23 ` Francis Moreau
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=20140908152724.GB32677@kroah.com \
--to=greg@kroah.com \
--cc=axboe@kernel.dk \
--cc=francis.moro@gmail.com \
--cc=kmo@daterainc.com \
--cc=linux-bcache@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=peter@kieser.ca \
--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;
as well as URLs for NNTP newsgroup(s).