linux-kernel - Re: [GIT PULL] bcache changes for 3.17

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Fri, 05 Sep 2014 09:31:06 +0200
From:	Francis Moreau <francis.moro@...il.com>
To:	Jens Axboe <axboe@...nel.dk>, Kent Overstreet <kmo@...erainc.com>
CC:	Peter Kieser <peter@...ser.ca>, linux-kernel@...r.kernel.org,
	linux-bcache@...r.kernel.org, stable <stable@...r.kernel.org>
Subject: Re: [GIT PULL] bcache changes for 3.17

On 08/10/2014 09:54 AM, Peter Kieser wrote:
> 
> On 2014-08-05 9:58 AM, Jens Axboe wrote:
>> On 08/04/2014 10:33 PM, Kent Overstreet wrote:
>>> Hey Jens, here's the pull request for 3.17 - typically late, but lots of tasty
>>> fixes in this one :)
>> Normally I'd say no, but since it's basically just fixes, I guess we can
>> pull it in. But generally, it has to be in my hands a week before this,
>> so it can simmer a bit in for-next before going in...
>>
> Are these fixes going to be backported to 3.10 or other stable releases?
> 

Could you please answer this question ?

If you don't want to maintain bcache for stable kernels (I can
understand that), can you mark it at least as unstable/experimental
stuff since it really is ?

Thanks

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/