LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Jon Paul Maloy <jon.maloy@donjonn.com>
To: netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: SV: Re: [tipc-discussion] [RFC: 2.6 patch] net/tipc/: possible cleanups
Date: Sun, 25 Feb 2007 19:56:26 +0100 (CET) [thread overview]
Message-ID: <812945.13617.qm@web710.biz.mail.mud.yahoo.com> (raw)
In-Reply-To: <20070225161411.GX12392@stusta.de>
--- Adrian Bunk <bunk@stusta.de> 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 anything about, would be both happy and
proud to contribute code to the main tree. One I know
about,who has developed a very interesting "reliable
bond interface" based on this API, doesn't regard his
code to be up to the kernel coding standards yet,
although I am trying to encourage him. Another one
thinks his function is just too specialized to be of
any common interest.
In the future, I would be also be very interested in
seeing a cross-node netlink implementation, carried
over TIPC, using this API. (Unfortunately, I don't
dare to commit to this myself right now, there is too
much left to be done in TIPC.)
So, as you see, keeping the exported symbols would be
a definite advantage, as current and future developers
would not have to patch the kernel to do their work.
Regards
///jon
prev parent reply other threads:[~2007-02-25 18:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-24 22:58 Adrian Bunk
2007-01-25 16:08 ` [tipc-discussion] " Jon Maloy
2007-02-23 18:06 ` Adrian Bunk
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 ` Jon Paul Maloy [this message]
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=812945.13617.qm@web710.biz.mail.mud.yahoo.com \
--to=jon.maloy@donjonn.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--subject='SV: Re: [tipc-discussion] [RFC: 2.6 patch] net/tipc/: possible cleanups' \
/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
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).