From: Philip Craig <philipc@snapgear.com>
To: "David S. Miller" <davem@davemloft.net>
Cc: bunk@stusta.de, netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [RFC: 2.6 patch] net/netlink/: possible cleanups
Date: Wed, 19 Apr 2006 10:02:08 +1000 [thread overview]
Message-ID: <44457E00.1030504@snapgear.com> (raw)
In-Reply-To: <20060413.132603.94193712.davem@davemloft.net>
On 04/14/2006 06:26 AM, David S. Miller wrote:
> These interfaces were added so that new users of netlink could
> write their code more easily.
>
> Unused does not equate to "comment out or delete".
Does a GENETLINK Kconfig option make sense (possibly dependant on
EMBEDDED)? I'm unsure whether these interfaces are going to be used
in core networking code that can't be disabled anyway.
prev parent reply other threads:[~2006-04-19 0:02 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-13 16:27 [RFC: 2.6 patch] net/netlink/: possible cleanups Adrian Bunk
2006-04-13 20:26 ` David S. Miller
2006-04-14 10:32 ` Adrian Bunk
2006-04-14 10:56 ` Evgeniy Polyakov
2006-04-18 14:19 ` Adrian Bunk
2006-04-18 18:48 ` Alan Cox
2006-04-18 19:09 ` Adrian Bunk
2006-04-19 0:02 ` Philip Craig [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=44457E00.1030504@snapgear.com \
--to=philipc@snapgear.com \
--cc=bunk@stusta.de \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
/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 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).