| To: | Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx> |
|---|---|
| Subject: | Re: [Openswan Users] Invalid argument NULL |
| From: | "David S. Miller" <davem@xxxxxxxxxx> |
| Date: | Sun, 15 Aug 2004 19:53:13 -0700 |
| Cc: | jiva@xxxxxxxxxxx, users@xxxxxxxxxxxxxxxxxx, dev@xxxxxxxxxxxxxxxxxx, kuznet@xxxxxxxxxxxxx, netdev@xxxxxxxxxxx |
| In-reply-to: | <20040815112548.GA2864@xxxxxxxxxxxxxxxxxxx> |
| References: | <BD428BAA.4BBE%jiva@xxxxxxxxxxx> <E1BwINn-0000ZX-00@xxxxxxxxxxxxxxxxxxxxxxxx> <20040815112548.GA2864@xxxxxxxxxxxxxxxxxxx> |
| Sender: | netdev-bounce@xxxxxxxxxxx |
On Sun, 15 Aug 2004 21:25:48 +1000 Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx> wrote: > In any case, here is a really ugly patch to fill in those values for > xfrm_user. Please let me know of any clean-ups or better ways of doing > this. I've applied this for now. There is a lot of duplication around the xfrm structures of this kind of information. Thanks. |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: [Panic] 2.6.8 and ingress scheduling, David S. Miller |
|---|---|
| Next by Date: | Re: [ESP] Only one algorithm is required, David S. Miller |
| Previous by Thread: | Re: [Openswan Users] Invalid argument NULL, Herbert Xu |
| Next by Thread: | Re: [Openswan Users] Invalid argument NULL, Herbert Xu |
| Indexes: | [Date] [Thread] [Top] [All Lists] |