| To: | krkumar@xxxxxxxxxx |
|---|---|
| Subject: | Re: [PATCH 2/2] Prefix List and O/M flags against 2.4.21 |
| From: | YOSHIFUJI Hideaki / 吉藤英明 <yoshfuji@xxxxxxxxxxxxxx> |
| Date: | Fri, 18 Jul 2003 00:47:01 +0200 (CEST) |
| Cc: | kuznet@xxxxxxxxxxxxx, davem@xxxxxxxxxx, netdev@xxxxxxxxxxx, linux-net@xxxxxxxxxxxxxxx, yoshfuji@xxxxxxxxxxxxxx |
| In-reply-to: | <3F17245D.9040806@xxxxxxxxxx> |
| Organization: | USAGI Project |
| References: | <Pine.LNX.4.44.0307171413100.1353-100000@xxxxxxxxxxxxxxxxxxxxxxxxxxx> <20030718.002209.104303756.yoshfuji@xxxxxxxxxxxxxx> <3F17245D.9040806@xxxxxxxxxx> |
| Sender: | netdev-bounce@xxxxxxxxxxx |
In article <3F17245D.9040806@xxxxxxxxxx> (at Thu, 17 Jul 2003 15:34:05 -0700), Krishna Kumar <krkumar@xxxxxxxxxx> says: > have any knowledge of using this new interface. If you prefer, I can split the > patch for prefix list vs O/M bits so that the former is accepted without any > issues. Someone else can modify the O/M to suit new needs. Does that sound OK > with you ? Yes, please split up the patch. > > At least, new RTM_xxx should not be restricted to get such flags. > > That's why I had suggested that we can use RTM_GETLNKINFO with more > information, > like RTA_IFFLAGS, and other things like stats or whatever. That can be done > easily enough and still be functionally complete. I just don't have any idea > about this new interface. > > Is this still a problem ? Hmm, I might miss something. Anyway, it seems we're reaching consensus. --yoshfuji |
| Previous by Date: | Re: [PATCH 2/2] Prefix List and O/M flags against 2.4.21, Krishna Kumar |
|---|---|
| Next by Date: | comx drivers in 2.6, Stephen Hemminger |
| Previous by Thread: | Re: [PATCH 2/2] Prefix List and O/M flags against 2.4.21, Krishna Kumar |
| Next by Thread: | Re: [PATCH 2/2] Prefix List and O/M flags against 2.5.73, Krishna Kumar |
| Indexes: | [Date] [Thread] [Top] [All Lists] |