From: Eddie Chapman <eddie@ehuk.net>
To: Jens Axboe <axboe@kernel.dk>,
Francis Moreau <francis.moro@gmail.com>,
Kent Overstreet <kmo@daterainc.com>
Cc: Peter Kieser <peter@kieser.ca>,
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: Fri, 05 Sep 2014 16:37:32 +0100 [thread overview]
Message-ID: <5409D8BC.7030003@ehuk.net> (raw)
In-Reply-To: <5409C5FC.6020406@kernel.dk>
On 05/09/14 15:17, Jens Axboe wrote:
> (from oldest to newest). And that's just from 3.16 to 3.17-rc3, going
> all the way back to 3.10 would be a lot of work. If there's anyone that
> cares about bcache on stable kernels (and actually use it), now would be
> a good time to pipe up.
Just "piping up" as I care about bcache and actually use it in
production on 3.10! Shame I don't have the knowledge to try and backport
these though :-)
Eddie
next prev parent reply other threads:[~2014-09-05 15:37 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20140805043346.GF541@moria.home.lan>
[not found] ` <53E10D48.1010700@kernel.dk>
[not found] ` <53E7251B.3080305@kieser.ca>
2014-09-05 7:31 ` [GIT PULL] bcache changes for 3.17 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 [this message]
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
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=5409D8BC.7030003@ehuk.net \
--to=eddie@ehuk.net \
--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).