linux-kernel - Re: [tipc-discussion] [RFC: 2.6 patch] net/tipc/: possible cleanups

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]

Message-ID: <20070223221657.GA10153@infradead.org>
Date:	Fri, 23 Feb 2007 22:16:57 +0000
From:	Christoph Hellwig <hch@...radead.org>
To:	Adrian Bunk <bunk@...sta.de>
Cc:	Jon Maloy <jon.maloy@...csson.com>, per.liden@...csson.com,
	allan.stephens@...driver.com, netdev@...r.kernel.org,
	tipc-discussion@...ts.sourceforge.net, linux-kernel@...r.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@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/