Mail Archive Search: <+subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[PATCH\]\s+network\s+device\s+renaming\s+sysfs\s+fix\s*$/>

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[PATCH\]\s+network\s+device\s+renaming\s+sysfs\s+fix\s*$/: 16 ]

Total 16 documents matching your query.

1. [PATCH] network device renaming sysfs fix (score: 1): Author: m@xxxxxxxxxx>; Date: Fri, 15 Aug 2003 14:15:14 +0300; HTML encoded emails on this list. It makes you look like a bozo. :-); /archives/netdev/2003-08/msg00405.html (8,826 bytes)
2. RE: [PATCH] network device renaming sysfs fix (score: 1): Author: iller" <davem@xxxxxxxxxx>; Date: Fri, 15 Aug 2003 14:36:27 +0300; Later I'll also look into fixing the same issue with sysctl. -- linu; /archives/netdev/2003-08/msg00406.html (9,128 bytes)
3. Re: [PATCH] network device renaming sysfs fix (score: 1): Author: ler" <davem@xxxxxxxxxx>; Date: Fri, 15 Aug 2003 14:45:07 +0300; ing, and it sounds odd each driver should handle this on it's own. --; /archives/netdev/2003-08/msg00407.html (9,682 bytes)
4. Re: [PATCH] network device renaming sysfs fix (score: 1): Author: ik" <shmulik.hen@xxxxxxxxx>; Date: Fri, 15 Aug 2003 09:37:24 -0700; arches. Creating the search tree can be a little more involved, and I; /archives/netdev/2003-08/msg00409.html (10,473 bytes)
5. Re: [PATCH] network device renaming sysfs fix (score: 1): Author: a-x@xxxxxxx>; Date: Fri, 15 Aug 2003 19:50:48 +0300; really need the debug message? Why return an error if you already com; /archives/netdev/2003-08/msg00410.html (9,219 bytes)
6. Re: [PATCH] network device renaming sysfs fix (score: 1): Author: artin <kyle@xxxxxxxxxx>; Date: Fri, 15 Aug 2003 11:09:34 -0700; y given the limitations of using the private ESP id space, since ther; /archives/netdev/2003-08/msg00415.html (9,486 bytes)
7. Re: [PATCH] network device renaming sysfs fix (score: 1): Author: t@xxxxxxxxxxxxxxxxxx>; Date: Sat, 16 Aug 2003 07:40:14 -0700; eanup change, it is necessary.; /archives/netdev/2003-08/msg00434.html (8,618 bytes)
8. Re: [PATCH] network device renaming sysfs fix (score: 1): Author: xxxxxxxxxxxxxxxxx>; Date: Sun, 17 Aug 2003 10:13:07 +0300; , how best to proceed, and that's why I too; /archives/netdev/2003-08/msg00449.html (9,431 bytes)
9. [PATCH] network device renaming sysfs fix (score: 1): Author: Dan Aloni <da-x@xxxxxxx>; Date: Fri, 15 Aug 2003 14:15:14 +0300; (repost, now will hopefully reach the mailing list) I believe this is a better approach for fixing the sysfs renaming discrepancy. Later I'll also look into fixing the same issue with sysctl. -- linu; /archives/netdev/2003-08/msg01377.html (8,826 bytes)
10. RE: [PATCH] network device renaming sysfs fix (score: 1): Author: "Hen, Shmulik" <shmulik.hen@xxxxxxxxx>; Date: Fri, 15 Aug 2003 14:36:27 +0300; In general, it a similar thing applicable for proc fs too ? We just had to fix something like that in bonding, and it sounds odd each driver should handle this on it's own. --; /archives/netdev/2003-08/msg01378.html (9,143 bytes)
11. Re: [PATCH] network device renaming sysfs fix (score: 1): Author: Dan Aloni <da-x@xxxxxxx>; Date: Fri, 15 Aug 2003 14:45:07 +0300; It is more complicated. procfs's interface to sysctl is optional - thus sysctl's interfaces hide procfs from you. Fixing this require changes in sysctl itself, and most probably also in the networkin; /archives/netdev/2003-08/msg01379.html (9,793 bytes)
12. Re: [PATCH] network device renaming sysfs fix (score: 1): Author: Stephen Hemminger <shemminger@xxxxxxxx>; Date: Fri, 15 Aug 2003 09:37:24 -0700; Yes, this is a better fix because it won't break when unregister and free are split into seperate steps (coming soon). But, do we really need the debug message? Why return an error if you already com; /archives/netdev/2003-08/msg01381.html (10,531 bytes)
13. Re: [PATCH] network device renaming sysfs fix (score: 1): Author: Dan Aloni <da-x@xxxxxxx>; Date: Fri, 15 Aug 2003 19:50:48 +0300; Agreed. [patch] -- Dan Aloni da-x@xxxxxxx; /archives/netdev/2003-08/msg01382.html (9,332 bytes)
14. Re: [PATCH] network device renaming sysfs fix (score: 1): Author: Mark Huth <mhuth@xxxxxxxxxx>; Date: Fri, 15 Aug 2003 11:09:34 -0700; Agreed. We had not yet found the class_device_rename. Hopefully, this is no longer in HTML format. By all means, help not to look like a bozo :-) - a tall order, I realize. Mark Huth (repost, now wil; /archives/netdev/2003-08/msg01387.html (9,587 bytes)
15. Re: [PATCH] network device renaming sysfs fix (score: 1): Author: "David S. Miller" <davem@xxxxxxxxxx>; Date: Sat, 16 Aug 2003 07:40:14 -0700; Patch applied, thanks everyone. Can't the device name also change via netlink messages? If so, do we handle that case properly?; /archives/netdev/2003-08/msg01406.html (8,731 bytes)
16. Re: [PATCH] network device renaming sysfs fix (score: 1): Author: Dan Aloni <da-x@xxxxxxx>; Date: Sun, 17 Aug 2003 10:13:07 +0300; No it can't, AFAIK. You might be confusing between netlink and notifier calls (which allow ipv4 to update the names of aliases when the device name changes). BTW, it is possible to add notifier handl; /archives/netdev/2003-08/msg01421.html (9,576 bytes)

Current List: 1 - 16
Page: [1]