From: "David S. Miller" <davem@davemloft.net>
To: hadi@cyberus.ca
Cc: bunk@stusta.de, alan@redhat.com, kuznet@ms2.inr.ac.ru,
netdev@oss.sgi.com, linux-kernel@vger.kernel.org
Subject: Re: [2.6 patch] net/netlink/af_netlink.c: possible cleanups
Date: Mon, 27 Dec 2004 19:08:16 -0800 [thread overview]
Message-ID: <20041227190816.1d166ba2.davem@davemloft.net> (raw)
In-Reply-To: <1103119623.1077.71.camel@jzny.localdomain>
On 15 Dec 2004 09:07:03 -0500
jamal <hadi@cyberus.ca> wrote:
> I think this should be left alone for now; what we need to do is
> deprecate NETLINK_DEV incase someone is still using it.
> Else we could get rid of it totaly including what Adrian is deleting
> below. Any users of NETLINK_DEV? Maybe deleting the feature will get
> someone whining? ;->
While I agree we should probably just kill NETLINK_DEV now
and don't look back, I have applied Adrian's patch for
the time being.
prev parent reply other threads:[~2004-12-28 3:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-15 0:46 [2.6 patch] net/netlink/af_netlink.c: possible cleanups Adrian Bunk
2004-12-15 14:07 ` jamal
2004-12-28 3:08 ` David S. Miller [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=20041227190816.1d166ba2.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=alan@redhat.com \
--cc=bunk@stusta.de \
--cc=hadi@cyberus.ca \
--cc=kuznet@ms2.inr.ac.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@oss.sgi.com \
/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.