From: "David S. Miller" <davem@redhat.com>
To: acme@conectiva.com.br
Cc: netdev@oss.sgi.com
Subject: Re: [PATCH] take2: new module infrastructure for net_proto_family
Date: Sat, 19 Apr 2003 18:41:22 -0700 (PDT) [thread overview]
Message-ID: <20030419.184122.74731778.davem@redhat.com> (raw)
In-Reply-To: <20030419233408.GG6251@conectiva.com.br>
From: Arnaldo Carvalho de Melo <acme@conectiva.com.br>
Date: Sat, 19 Apr 2003 20:34:08 -0300
Please consider pulling from:
bk://kernel.bkbits.net/acme/net-2.5
It has your suggestions implemented.
Pulled, thanks.
Note that, eventually we'll need to handle the struct sock side of
this equation. Consider that struct sock's can exist long after the
user struct socket is closed (TCP is the best example), yet they
reference internals to the protocol module (via sk and skb
callbacks, hash table linkage, etc.).
We can deal with this later, let's merge your stuff in first.
next prev parent reply other threads:[~2003-04-20 1:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-19 23:34 [PATCH] take2: new module infrastructure for net_proto_family Arnaldo Carvalho de Melo
2003-04-20 1:41 ` David S. Miller [this message]
2003-04-20 16:02 ` Arnaldo Carvalho de Melo
2003-04-20 16:10 ` Arnaldo Carvalho de Melo
2003-04-20 19:41 ` 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=20030419.184122.74731778.davem@redhat.com \
--to=davem@redhat.com \
--cc=acme@conectiva.com.br \
--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).