Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752322AbXBYFTb (ORCPT ); Sun, 25 Feb 2007 00:19:31 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1752325AbXBYFTb (ORCPT ); Sun, 25 Feb 2007 00:19:31 -0500 Received: from mail.windriver.com ([147.11.1.11]:51471 "EHLO mail.wrs.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752321AbXBYFTa convert rfc822-to-8bit (ORCPT ); Sun, 25 Feb 2007 00:19:30 -0500 X-Greylist: delayed 17928 seconds by postgrey-1.27 at vger.kernel.org; Sun, 25 Feb 2007 00:19:30 EST X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 8BIT Subject: RE: [tipc-discussion] [RFC: 2.6 patch] net/tipc/: possible cleanups Date: Sat, 24 Feb 2007 16:19:19 -0800 Message-ID: In-Reply-To: <20070223221657.GA10153@infradead.org> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [tipc-discussion] [RFC: 2.6 patch] net/tipc/: possible cleanups Thread-Index: AcdXmI2qMW4z360DQZSpR0zL3RAwJgA19cwg From: "Stephens, Allan" To: "Christoph Hellwig" , "Adrian Bunk" Cc: "Jon Maloy" , , , , X-OriginalArrivalTime: 25 Feb 2007 00:19:20.0566 (UTC) FILETIME=[98289160:01C75872] Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2129 Lines: 57 Just to clarify an apparent misunderstanding that has snuck into this thread: 1) There are quite a few people/groups out there who are using TIPC's socket API, so the protocol as a whole is being used and should remain in the kernel. 2) There are portions of TIPC's native API which are intended for use by driver programmers, but which are not being used by any code that is currently in the kernel. While removing these API's from TIPC will only impact these "freeloaders", it has the potential to discourage future programmers who *do* want to contribute their work to the kernel by removing API's that are apparently necessary/useful when doing coding of this sort. Regards, Al > -----Original Message----- > From: Christoph Hellwig [mailto:hch@infradead.org] > Sent: Friday, February 23, 2007 5:17 PM > To: Adrian Bunk > Cc: Jon Maloy; per.liden@ericsson.com; Stephens, Allan; > netdev@vger.kernel.org; > tipc-discussion@lists.sourceforge.net; linux-kernel@vger.kernel.org > Subject: Re: [tipc-discussion] [RFC: 2.6 patch] net/tipc/: > possible cleanups > > On Fri, Feb 23, 2007 at 07:06:12PM +0100, Adrian Bunk wrote: > > > >My impression is that most of this might have users that are not > > > >yet submitted for inclusion in the kernel - one year > after TIPC was merged. > > > > > > > > > > > Not quite. The exported symbols belong to a public API > for driver > > >programmers. > > > We know about several users of this API, and there will > be more, but > > >I don't think any of them are aspiring to have their code be > > >included in the kernel. > > >... > > > > Why not? > > > > The goal is to get as many drivers as possible included in > the kernel. > > If we don't have any planned in-tree users for tipc we should > simply drop tipc from the kernel entirely. No point to make > our maintaince work harder for out of tree freeloaders. > - 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/