From: Max Krasnyansky <maxk@qualcomm.com>
To: hadi@cyberus.ca
Cc: Chris Wright <chrisw@osdl.org>,
"David S. Miller" <davem@davemloft.net>,
netdev@oss.sgi.com
Subject: Re: [PATCH] remove unused netlink NL_EMULATE_DEV code
Date: Mon, 21 Mar 2005 10:26:11 -0800 [thread overview]
Message-ID: <423F11C3.2020803@qualcomm.com> (raw)
In-Reply-To: <1111196899.1264.118.camel@jzny.localdomain>
jamal wrote:
> 1
> On Fri, 2005-03-18 at 20:02, Chris Wright wrote:
>
>
>>I'd prefer that too. What about the netlink_dev implementation itself?
>>Should it be marked obsolete?
>>
>
> It should die - pieces of it have already been slowly disapearing.
Totally agree. Even for Ethertap it was easy to use Netlink sockets directly.
Max
next prev parent reply other threads:[~2005-03-21 18:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-18 23:36 [PATCH] remove unused netlink NL_EMULATE_DEV code Chris Wright
2005-03-19 0:09 ` Max Krasnyansky
2005-03-19 1:02 ` Chris Wright
2005-03-19 1:48 ` jamal
2005-03-21 18:26 ` Max Krasnyansky [this message]
2005-03-23 3:22 ` David S. Miller
-- strict thread matches above, loose matches on Subject: below --
2005-02-12 3:55 Chris Wright
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=423F11C3.2020803@qualcomm.com \
--to=maxk@qualcomm.com \
--cc=chrisw@osdl.org \
--cc=davem@davemloft.net \
--cc=hadi@cyberus.ca \
--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 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).