From: Adrian Bunk <bunk@stusta.de>
To: Jon Maloy <jon.maloy@ericsson.com>
Cc: per.liden@ericsson.com, allan.stephens@windriver.com,
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
Date: Fri, 23 Feb 2007 19:06:12 +0100 [thread overview]
Message-ID: <20070223180612.GE12392@stusta.de> (raw)
In-Reply-To: <45B8D5E8.1090308@ericsson.com>
On Thu, Jan 25, 2007 at 04:08:08PM +0000, 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
> we'll
> get it in, one way or another.
>
> >- 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.
> >
> >
> 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.
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
next prev parent reply other threads:[~2007-02-23 18:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-24 22:58 [RFC: 2.6 patch] net/tipc/: possible cleanups Adrian Bunk
2007-01-25 16:08 ` [tipc-discussion] " Jon Maloy
2007-02-23 18:06 ` Adrian Bunk [this message]
2007-02-23 22:16 ` Christoph Hellwig
2007-02-25 0:19 ` Stephens, Allan
2007-02-25 16:14 ` Adrian Bunk
2007-02-25 18:56 ` SV: " Jon Paul Maloy
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20070223180612.GE12392@stusta.de \
--to=bunk@stusta.de \
--cc=allan.stephens@windriver.com \
--cc=jon.maloy@ericsson.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=per.liden@ericsson.com \
--cc=tipc-discussion@lists.sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.