From: "David S. Miller" <davem@redhat.com>
To: bunk@fs.tum.de
Cc: netdev@oss.sgi.com, linux-kernel@vger.kernel.org
Subject: Re: Chaotic structure of the net headers?
Date: Wed, 05 Mar 2003 14:39:51 -0800 (PST) [thread overview]
Message-ID: <20030305.143951.118510613.davem@redhat.com> (raw)
In-Reply-To: <20030305225441.GO20423@fs.tum.de>
From: Adrian Bunk <bunk@fs.tum.de>
Date: Wed, 5 Mar 2003 23:54:41 +0100
Two different #define's for the same thing doesn't sound like a good
idea?
Required by the ipv6 advanced sockets API I do believe.
next prev parent reply other threads:[~2003-03-05 22:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-05 22:54 Chaotic structure of the net headers? Adrian Bunk
2003-03-05 22:39 ` David S. Miller [this message]
2003-03-05 23:10 ` Rod Van Meter
2003-03-05 23:03 ` David S. Miller
2003-03-05 23:53 ` Richard Guy Briggs
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=20030305.143951.118510613.davem@redhat.com \
--to=davem@redhat.com \
--cc=bunk@fs.tum.de \
--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 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).