From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753903AbcAHCC4 (ORCPT ); Thu, 7 Jan 2016 21:02:56 -0500 Received: from mx.ewheeler.net ([71.19.153.34]:54311 "EHLO mail.ewheeler.net" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1753109AbcAHCCy (ORCPT ); Thu, 7 Jan 2016 21:02:54 -0500 Date: Thu, 7 Jan 2016 18:02:51 -0800 (PST) From: Eric Wheeler X-X-Sender: lists@mail.ewheeler.net To: Jens Axboe cc: Kent Overstreet , Eric Wheeler , Al Viro , Denis Bychkov , g2p.code@gmail.com, Jiri Kosina , Joshua Schmid , linux-bcache@vger.kernel.org, linux-kernel@vger.kernel.org, stefan.bader@canonical.com, Takashi Iwai , Vojtech Pavlik , Zheng Liu , Zheng Liu Subject: Re: [PULL] Re: bcache stability patches In-Reply-To: <5684A030.1040306@kernel.dk> Message-ID: References: <56841B8B.6070306@kernel.dk> <20151231031500.GA8265@kmo-pixel> <5684A030.1040306@kernel.dk> User-Agent: Alpine 2.11 (LRH 23 2013-08-11) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, 30 Dec 2015, Jens Axboe wrote: > On 12/30/2015 08:15 PM, Kent Overstreet wrote: > > On Wed, Dec 30, 2015 at 10:59:39AM -0700, Jens Axboe wrote: > > > Looking over these, most are really simple one-liners, and nothing sticks > > > out as being overly complicated. Kent, do you have any plans to maintain > > > the > > > in-kernel bcache? > > > > Yeah - these patches are all fine, go ahead and pull. > > Great, thanks. > > > I may start doing maintainence again at some point (but if there's someone > > willing to step up and take over and do a good job of it, I'd gladly hand > > things > > off) We use this in production internally, so I'll keep collecting patches and may ask for pulls from time to time. > As long as we have a path into mainline for stability fixes, at least that's > better than before. > > Thanks Eric for collecting these. I've reformatted some of them a bit, not > sure if that's github crappery, or if they came like that. It's pushed out > now. You're welcome. It could be github crappery, however, these were copy-pasted and cleaned up in various ways such that they merge into 3.17-rc1 and then merge forward into 4.1.15 which we build against---so who knows about formatting, whitspace, and other minor issues. I'm just glad they are on their way to 4.5 with stable@ Cc's! BTW, can someone suggest an alternate git host with less crappery? -Eric > > -- > Jens Axboe > > >