| To: | Thomas Graf <tgraf@xxxxxxx> |
|---|---|
| Subject: | Re: [PATCH 1/3] [RTNETLINK] Fix RTM_MAX to represent the maximum valid message type |
| From: | "David S. Miller" <davem@xxxxxxxxxxxxx> |
| Date: | Tue, 3 May 2005 15:27:04 -0700 |
| Cc: | netdev@xxxxxxxxxxx |
| In-reply-to: | <20050503222003.GQ577@xxxxxxxxxxxxxx> |
| References: | <20050430195058.GC577@xxxxxxxxxxxxxx> <20050503142740.345925ea.davem@xxxxxxxxxxxxx> <20050503222003.GQ577@xxxxxxxxxxxxxx> |
| Sender: | netdev-bounce@xxxxxxxxxxx |
On Wed, 4 May 2005 00:20:03 +0200 Thomas Graf <tgraf@xxxxxxx> wrote: > * David S. Miller <20050503142740.345925ea.davem@xxxxxxxxxxxxx> 2005-05-03 > 14:27 > > Excellent observation. The fact that we encode the "modifies state" > > in the low bits of the RTM_* numbers has always been a source of > > obscure bugs and hard to track down errors. > > > > Patch applied, thanks. > > Do you want 2.4 backports for all patches or just the xfrm > off-by-one fix? Congratulations if you can find xfrm in the vanilla 2.4.x tree :-) |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: [PATCH] net: Disable queueing when carrier is lost (take 2), Tommy Christensen |
|---|---|
| Next by Date: | Re: Fw: [Bug 4554] New: /proc/net/route missing info for 127.0.0.1/8, Patrick McHardy |
| Previous by Thread: | Re: [PATCH 1/3] [RTNETLINK] Fix RTM_MAX to represent the maximum valid message type, Thomas Graf |
| Next by Thread: | Re: [PATCH 1/3] [RTNETLINK] Fix RTM_MAX to represent the maximum valid message type, Thomas Graf |
| Indexes: | [Date] [Thread] [Top] [All Lists] |