From: "Austin S. Hemmelgarn" <ahferroin7@gmail.com>
To: dsterba@suse.cz, Dmitry Katsubo <dma_k@mail.ru>,
linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: Spare volumes and hot auto-replacement feature
Date: Fri, 6 May 2016 07:19:44 -0400 [thread overview]
Message-ID: <97c465c2-b2de-eb70-708b-6aa88569e156@gmail.com> (raw)
In-Reply-To: <20160506090822.GB29353@twin.jikos.cz>
On 2016-05-06 05:08, David Sterba wrote:
> On Thu, May 05, 2016 at 07:23:11AM -0400, Austin S. Hemmelgarn wrote:
>> On 2016-05-04 19:18, Dmitry Katsubo wrote:
>>> Dear btrfs community,
>>>
>>> I am interested in spare volumes and hot auto-replacement feature [1]. I have a couple of questions:
>>>
>>> * Which kernel version this feature will be included?
>> Probably 4.7. I would not suggest using it in production for at least a
>> few cycles though (probably 4.9).
>
> I wonder what are the grounds of the prediction, 4.7 is pretty much done
> regarding new features. And given the number of other features that are
> considered for merge I don't know an ETA. I haven't looked at the
> patches yet (but don't know about others).
>
I was under the impression that you had pulled them into your for-next
branch, and forgot that that would mean probably mean 4.8 at the
earliest, although looking at your tree now, I notice that the only
patch from the series there is the first one which fixes a lockdep
warning, and looking again at the ML is the only one you said you added.
So, taken altogether, the prediction was largely predicated on me being
significantly absent-minded.
next prev parent reply other threads:[~2016-05-06 11:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-04 23:18 Spare volumes and hot auto-replacement feature Dmitry Katsubo
2016-05-05 11:23 ` Austin S. Hemmelgarn
2016-05-06 9:08 ` David Sterba
2016-05-06 11:19 ` Austin S. Hemmelgarn [this message]
2016-05-05 15:35 ` Anand Jain
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=97c465c2-b2de-eb70-708b-6aa88569e156@gmail.com \
--to=ahferroin7@gmail.com \
--cc=dma_k@mail.ru \
--cc=dsterba@suse.cz \
--cc=linux-btrfs@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).