Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1760720AbbBITtI (ORCPT ); Mon, 9 Feb 2015 14:49:08 -0500 Received: from 251.110.2.81.in-addr.arpa ([81.2.110.251]:36871 "EHLO lxorguk.ukuu.org.uk" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1759779AbbBITtG (ORCPT ); Mon, 9 Feb 2015 14:49:06 -0500 Date: Mon, 9 Feb 2015 19:48:13 +0000 From: One Thousand Gnomes To: Tilman Schmidt Cc: Bas Peters , Karsten Keil , Paul Bolle , Joe Perches , Sergei Shtylyov , "isdn@linux-pingi.de" , Julia Lawall , David Miller , netdev@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: Kill I4L? Message-ID: <20150209194813.180e54ae@lxorguk.ukuu.org.uk> In-Reply-To: <54D891C0.2010303@imap.cc> References: <1423328797-17865-1-git-send-email-baspeters93@gmail.com> <1423328797-17865-3-git-send-email-baspeters93@gmail.com> <54D650BF.5000400@cogentembedded.com> <1423336761.2933.7.camel@perches.com> <1423341800.2246.68.camel@x220> <54D7BD4A.4090101@imap.cc> <54D7F87E.4050506@linux-pingi.de> <54D891C0.2010303@imap.cc> Organization: Intel Corporation X-Mailer: Claws Mail 3.11.1 (GTK+ 2.24.25; x86_64-redhat-linux-gnu) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1397 Lines: 32 > The reason is the maintenance load it produces. There's a continuous, > annoying trickle of patch proposals, discussions, conflicts with > development in other, still actively maintained areas of the kernel, > and so on. The present discussion being a point in case. > > > Does it hurt anyone to leave the code in there, despite it barely > > being used? > > Yes it does. Not much, but the pain is increasing over the years. > Every time someone tries to touch that code there's the problem > that no one can actually answer for it, much less test anything. The same has been happening with a lot of other code. For i2o I've followed the pattern a few other drivers have used. I sent GregKH a patch to move it into staging, and if nobody steps up then it will vanish in a few releases. > > We're not talking about a particularly huge driver here, either. > > But one that's particularly difficult to maintain, without > providing any noticeable benefit in return. I'm also not sure a pretty, polished and untested driver is actually better than someone who needs it going back to an old tree and a known working driver to forward port. Alan -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/