--- Adrian Bunk <[EMAIL PROTECTED]> skrev:
> It can be re-added at any time when an in-kernel
> user comes.
>
> But the most interesting question is:
> Why is noone interested in getting his TIPC using
> drivers merged?
>
I don't think lack of interest is the issue here. The
users I know anythi
On Sat, Feb 24, 2007 at 04:19:19PM -0800, Stephens, Allan wrote:
>...
> 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
[EMAIL PROTECTED]; Stephens, Allan;
> netdev@vger.kernel.org;
> [EMAIL PROTECTED]; 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:
> > > >M
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
>
On Thu, Jan 25, 2007 at 04:08:08PM +, Jon Maloy wrote:
> Adrian Bunk wrote:
>
> >This patch contains the following possible cleanups:
> >- make needlessly global functions static
> >- #if 0 unused functions
> >
> >
> Thanks. I think most of those were due for our next release, anyway. But
>
Adrian Bunk wrote:
This patch contains the following possible cleanups:
- make needlessly global functions static
- #if 0 unused functions
Thanks. I think most of those were due for our next release, anyway. But
we'll
get it in, one way or another.
- remove all EXPORT_SYMBOL's
My impress
This patch contains the following possible cleanups:
- make needlessly global functions static
- #if 0 unused functions
- remove all EXPORT_SYMBOL's
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.
If thi
