Mail Archive Search: <+subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[PATCH\s+2\.6\]\s+vlan\s+ioctl\s+propagation\s+$rev\.2$\s*$/>

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[PATCH\s+2\.6\]\s+vlan\s+ioctl\s+propagation\s+$rev\.2$\s*$/: 12 ]

Total 12 documents matching your query.

1. [PATCH 2.6] vlan ioctl propagation (rev.2) (score: 1): Author: x>; Date: Fri, 6 Aug 2004 14:39:28 -0700; /archives/netdev/2004-08/msg00155.html (10,405 bytes)
2. Re: [PATCH 2.6] vlan ioctl propagation (rev.2) (score: 1): Author: aber@xxxxxxxxx>; Date: Sat, 7 Aug 2004 23:10:37 +0200; /archives/netdev/2004-08/msg00165.html (9,191 bytes)
3. Re: [PATCH 2.6] vlan ioctl propagation (rev.2) (score: 1): Author: x>; Date: Sun, 08 Aug 2004 14:08:36 +0930; /archives/netdev/2004-08/msg00170.html (10,091 bytes)
4. Re: [PATCH 2.6] vlan ioctl propagation (rev.2) (score: 1): Author: xxxxx>; Date: Sun, 8 Aug 2004 12:14:21 +0200; /archives/netdev/2004-08/msg00173.html (9,834 bytes)
5. Re: [PATCH 2.6] vlan ioctl propagation (rev.2) (score: 1): Author: " <mtk-lists@xxxxxxx>; Date: Mon, 9 Aug 2004 08:53:48 -0700; /archives/netdev/2004-08/msg00194.html (9,416 bytes)
6. Re: [PATCH 2.6] vlan ioctl propagation (rev.2) (score: 1): Author: xxxxxxxxx>; Date: Mon, 9 Aug 2004 16:45:27 -0700; /archives/netdev/2004-08/msg00206.html (8,307 bytes)
7. [PATCH 2.6] vlan ioctl propagation (rev.2) (score: 1): Author: Stephen Hemminger <shemminger@xxxxxxxx>; Date: Fri, 6 Aug 2004 14:39:28 -0700; Here is a redo of the patch to propagate ethtool and mii ioctl's on vlan's to the underlying real device. This time the request is copied to a new buffer, to avoid the colon name rewrite issues. Sign; /archives/netdev/2004-08/msg01046.html (10,594 bytes)
8. Re: [PATCH 2.6] vlan ioctl propagation (rev.2) (score: 1): Author: bert hubert <ahu@xxxxxxx>; Date: Sat, 7 Aug 2004 23:10:37 +0200; Is this really what we want? We also don't make virtual IPs appear as real interfaces anymore. Virtual devices are just that - virtual. -- http://www.PowerDNS.com Open source, database driven DNS Sof; /archives/netdev/2004-08/msg01056.html (9,407 bytes)
9. Re: [PATCH 2.6] vlan ioctl propagation (rev.2) (score: 1): Author: Glen Turner <glen.turner@xxxxxxxxxxxxx>; Date: Sun, 08 Aug 2004 14:08:36 +0930; Here is a redo of the patch to propagate ethtool and mii ioctl's on vlan's to the underlying real device. This time the request is copied to a new buffer, to avoid the colon name rewrite issues. Is; /archives/netdev/2004-08/msg01061.html (10,118 bytes)
10. Re: [PATCH 2.6] vlan ioctl propagation (rev.2) (score: 1): Author: bert hubert <ahu@xxxxxxx>; Date: Sun, 8 Aug 2004 12:14:21 +0200; What I'm saying is that even userspace should not offer this abstraction. Remember the past confusion over "ifconfig eth0:1 down" ? But I'm more than prepared to follow DaveM's lead here, I just want; /archives/netdev/2004-08/msg01064.html (10,096 bytes)
11. Re: [PATCH 2.6] vlan ioctl propagation (rev.2) (score: 1): Author: Stephen Hemminger <shemminger@xxxxxxxx>; Date: Mon, 9 Aug 2004 08:53:48 -0700; The problem is that the bridge code (and bonding) want to be able to send ethtool ioctl's to the device. The bridge wants it to find out the speed of the device to set the spanning tree values approp; /archives/netdev/2004-08/msg01085.html (9,659 bytes)
12. Re: [PATCH 2.6] vlan ioctl propagation (rev.2) (score: 1): Author: "David S. Miller" <davem@xxxxxxxxxx>; Date: Mon, 9 Aug 2004 16:45:27 -0700; Applied.; /archives/netdev/2004-08/msg01097.html (8,493 bytes)

Current List: 1 - 12
Page: [1]