From: "David S. Miller" <davem@redhat.com>
To: hadi@shell.cyberus.ca
Cc: etsh_cucu@yahoo.com, david-b@pacbell.net, rddunlap@osdl.org,
linux-net@vger.kernel.org, netdev@oss.sgi.com
Subject: Re: netlink tester program
Date: Mon, 09 Jun 2003 10:16:15 -0700 (PDT) [thread overview]
Message-ID: <20030609.101615.133898193.davem@redhat.com> (raw)
In-Reply-To: <20030608212033.Y33230@shell.cyberus.ca>
From: Jamal Hadi <hadi@shell.cyberus.ca>
Date: Sun, 8 Jun 2003 21:35:09 -0400 (EDT)
Netlink2 draft is work in progress. The draft tends to lag reality.
I believe what you refer to has been fixed. Refer to the slides at:
http://www.zurich.ibm.com/~rha/netlink2.pdf
...
Consider netlink2 as a distributed netlink.
Beautiful, if you're going to allow this protocol to go over the wire,
you have to choose a network byte order and swap in/out of it.
Should be fun :)
Unfortunately I see no mention of this issue in the slides, should I
be scared?
next prev parent reply other threads:[~2003-06-09 17:16 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-30 16:00 netlink tester program Randy.Dunlap
2003-05-31 0:11 ` David S. Miller
2003-05-31 3:22 ` Randy.Dunlap
2003-05-31 6:42 ` David S. Miller
2003-05-31 12:09 ` Andi Kleen
2003-06-02 17:07 ` Randy.Dunlap
2003-06-02 21:04 ` Randy.Dunlap
2003-06-02 21:56 ` David S. Miller
2003-06-03 1:56 ` David Brownell
2003-06-03 2:02 ` David S. Miller
2003-06-03 3:34 ` David Brownell
2003-06-03 3:38 ` David S. Miller
2003-06-03 3:49 ` Randy.Dunlap
2003-06-03 3:51 ` David S. Miller
2003-06-03 7:57 ` Hisham Kotry
2003-06-09 1:35 ` Jamal Hadi
2003-06-09 14:37 ` Mr. James W. Laferriere
2003-06-09 17:16 ` David S. Miller [this message]
2003-06-03 2:33 ` John S. Denker
2003-06-03 2:38 ` David S. Miller
2003-06-03 3:20 ` John S. Denker
2003-06-03 3:22 ` David S. Miller
2003-06-03 3:41 ` John S. Denker
2003-06-03 3:46 ` David S. Miller
2003-06-03 3:54 ` Randy.Dunlap
2003-06-03 3:54 ` David S. Miller
2003-06-03 3:37 ` David Brownell
2003-06-03 3:32 ` Randy.Dunlap
2003-06-03 3:35 ` David S. Miller
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=20030609.101615.133898193.davem@redhat.com \
--to=davem@redhat.com \
--cc=david-b@pacbell.net \
--cc=etsh_cucu@yahoo.com \
--cc=hadi@shell.cyberus.ca \
--cc=linux-net@vger.kernel.org \
--cc=netdev@oss.sgi.com \
--cc=rddunlap@osdl.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 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.