| To: | "David S. Miller" <davem@xxxxxxxxxxxxx> |
|---|---|
| Subject: | Re: [TCP] Modular IPv6 support in tcpdiag |
| From: | Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx> |
| Date: | Thu, 4 Nov 2004 07:43:21 +1100 |
| Cc: | netdev@xxxxxxxxxxx |
| In-reply-to: | <20041103122941.71a5b440.davem@xxxxxxxxxxxxx> |
| References: | <20041103094451.GA20220@xxxxxxxxxxxxxxxxxxx> <20041103122050.50f6f556.davem@xxxxxxxxxxxxx> <20041103203414.GB25279@xxxxxxxxxxxxxxxxxxx> <20041103122941.71a5b440.davem@xxxxxxxxxxxxx> |
| Sender: | netdev-bounce@xxxxxxxxxxx |
| User-agent: | Mutt/1.5.6+20040722i |
On Wed, Nov 03, 2004 at 12:29:41PM -0800, David S. Miller wrote: > > > If I used that then it'll break when TCPDIAG is built-in and > > IPv6 is built as a module. > > I see, you need the ipv6 tcp socket lookup symbols... hmmm. Well it really should be turned into a plugin system. However, since any effort to do that might as well be spent doing a generic socket info interface, I thought that we should just patch up tcp_diag and mark it as obsolete once we have a new interface. Cheers, -- Visit Openswan at http://www.openswan.org/ Email: Herbert Xu ~{PmV>HI~} <herbert@xxxxxxxxxxxxxxxxxxx> Home Page: http://gondor.apana.org.au/~herbert/ PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: [TCP] Modular IPv6 support in tcpdiag, David S. Miller |
|---|---|
| Next by Date: | Re: [TCP] Modular IPv6 support in tcpdiag, David S. Miller |
| Previous by Thread: | Re: [TCP] Modular IPv6 support in tcpdiag, David S. Miller |
| Next by Thread: | Re: [TCP] Modular IPv6 support in tcpdiag, David S. Miller |
| Indexes: | [Date] [Thread] [Top] [All Lists] |