| To: | Stefan Rompf <srompf@xxxxxx> |
|---|---|
| Subject: | Re: Patch resubmission: RFC2863 operstatus for 2.5.50 |
| From: | Jeff Garzik <jgarzik@xxxxxxxxx> |
| Date: | Tue, 03 Dec 2002 19:52:57 -0500 |
| Cc: | "David S. Miller" <davem@xxxxxxxxxx>, netdev@xxxxxxxxxxx |
| In-reply-to: | <3DED2EA9.D812C881@xxxxxx> |
| References: | <3DE33D6D.25B9C9B4@xxxxxx> <20021126.021546.91313706.davem@xxxxxxxxxx> <3DED2EA9.D812C881@xxxxxx> |
| Sender: | netdev-bounce@xxxxxxxxxxx |
| User-agent: | Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.2) Gecko/20021126 |
Pardon my dumb question, but what parts of RFC2863 require kernel
additions over and above your link state patch?
Your second patch I am less enthusiastic about than the first... :(I wonder if userspace cannot figure out ifOperStatus from existing data we make available?
Jeff
|
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: Patch: Backport of link state notification to 2.4.20, Jeff Garzik |
|---|---|
| Next by Date: | tcp flows hash function, SVR Anand |
| Previous by Thread: | Re: Patch resubmission: RFC2863 operstatus for 2.5.50, Stefan Rompf |
| Next by Thread: | Re: Patch resubmission: RFC2863 operstatus for 2.5.50, Stefan Rompf |
| Indexes: | [Date] [Thread] [Top] [All Lists] |