From: Tim Small <tim@buttersideup.com>
To: Eric Wheeler <bcache@lists.ewheeler.net>, linux-bcache@vger.kernel.org
Subject: Re: bcache stability patches: Now mainlined!
Date: Wed, 24 Feb 2016 08:57:16 +0000 [thread overview]
Message-ID: <56CD706C.3070400@buttersideup.com> (raw)
In-Reply-To: <alpine.LRH.2.11.1602240626110.32077@mail.ewheeler.net>
On 24/02/16 06:45, Eric Wheeler wrote:
> I would like to thank everyone involved in getting these patches
> mainlined. Bcache should now be stable on the following releases:
>
> mainline: 4.5-rc1 (and later)
> longterm: 4.1.18
> longterm: 3.18.27
>
> Please test on your favorite branch and let us know how it goes.
According to https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=779628#25
... these patches are now in the Debian testing ("Stretch") kernel
(currently 4.3.x based), and it suggests that they may also be applied
to Debian stable ("Jessie") - which is 3.16.x based in a future Debian
"point release".
Cheers,
Tim.
next prev parent reply other threads:[~2016-02-24 9:43 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-22 9:13 BCACHE stability patches Denis Bychkov
2015-12-30 3:00 ` [PULL] Re: bcache " Eric Wheeler
2015-12-30 17:59 ` Jens Axboe
2015-12-31 3:15 ` Kent Overstreet
2015-12-31 3:25 ` Jens Axboe
2015-12-31 5:18 ` Kent Overstreet
2015-12-31 21:19 ` Denis Bychkov
2016-01-01 22:36 ` Kent Overstreet
2016-01-02 1:28 ` Denis Bychkov
2016-01-02 11:50 ` Vojtech Pavlik
2016-01-02 15:48 ` Denis Bychkov
2016-01-03 0:12 ` Kent Overstreet
2016-01-08 2:02 ` Eric Wheeler
2016-02-24 6:45 ` bcache stability patches: Now mainlined! Eric Wheeler
2016-02-24 6:57 ` Stefan Priebe - Profihost AG
2016-02-24 7:34 ` Eric Wheeler
2016-02-24 8:57 ` Tim Small [this message]
2015-12-31 7:23 ` [PULL] Re: bcache stability patches Denis Bychkov
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=56CD706C.3070400@buttersideup.com \
--to=tim@buttersideup.com \
--cc=bcache@lists.ewheeler.net \
--cc=linux-bcache@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