From: Joe Perches <joe@perches.com>
To: davem@nuts.ninka.net, linux-net@vger.kernel.org, netdev@oss.sgi.com
Subject: comment on [NET]: Delete support for old-style protocols, no longer necessary.
Date: Tue, 07 Oct 2003 11:37:09 -0700 [thread overview]
Message-ID: <1065551829.2340.9.camel@localhost.localdomain> (raw)
How about
netdevice.h
struct sock;
struct packet_type {
unsigned short type; /* This is really htons(ether_type). */
struct net_device *dev; /* NULL is wildcarded here */
int (*func) (struct sk_buff *, struct net_device *,
struct packet_type *);
- void *af_packet_priv;
+ struct sock *sk; /* appropriate comment: socket copy? */
struct list_head list;
};
and s/af_packet_priv/sk/g in the rest of the files?
next reply other threads:[~2003-10-07 18:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-07 18:37 Joe Perches [this message]
2003-10-07 18:52 ` comment on [NET]: Delete support for old-style protocols, no longer necessary David S. Miller
2003-10-07 23:33 ` Joe Perches
2003-10-08 0:22 ` Dan Kegel
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=1065551829.2340.9.camel@localhost.localdomain \
--to=joe@perches.com \
--cc=davem@nuts.ninka.net \
--cc=linux-net@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).