| To: | Dominic Duval <dd@xxxxxxxx> |
|---|---|
| Subject: | Re: ipv4.o module |
| From: | Francois Romieu <romieu@xxxxxxxxxx> |
| Date: | Sun, 10 Mar 2002 00:00:18 +0100 |
| Cc: | netdev@xxxxxxxxxxx |
| In-reply-to: | <3C8A7965.5010703@dd.qc.ca>; from dd@dd.qc.ca on Sat, Mar 09, 2002 at 04:06:45PM -0500 |
| References: | <3C89C85D.9070505@dd.qc.ca> <20020309164131.D10704@mea-ext.zmailer.org> <3C8A7965.5010703@dd.qc.ca> |
| Sender: | owner-netdev@xxxxxxxxxxx |
| User-agent: | Mutt/1.2.5i |
Dominic Duval <dd@xxxxxxxx> : [...] > Sure, that would be the next logical steps. The current patch is more a > proof of concept than anything else. For example, something better could > be done with ipv6, in fact I'm not even sure how the ipv6 module (and > other sub-modules of ipv4) will react with all these modifications. I On a related note, could somebody elaborate on why the EXPORT_SYMBOL are done from net/netsyms.c ? -- Ueimor |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: ipv4.o module, Dominic Duval |
|---|---|
| Next by Date: | Re: ipv4.o module, Matti Aarnio |
| Previous by Thread: | Re: ipv4.o module, Dominic Duval |
| Next by Thread: | Re: ipv4.o module, Matti Aarnio |
| Indexes: | [Date] [Thread] [Top] [All Lists] |