Mail Archive Search: <+subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[PATCH\/RFC\]\s+enabling\s+netdev\s+boot\s+options\s*$/>

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[PATCH\/RFC\]\s+enabling\s+netdev\s+boot\s+options\s*$/: 8 ]

Total 8 documents matching your query.

1. [PATCH/RFC] enabling netdev boot options (score: 1): Author: ap" <rddunlap@xxxxxxxx>; Date: Sat, 8 Nov 2003 16:04:16 -0800; I have modified 3c59x.c (for 2.4.22 and 2.6.0-test9) and eepro100 (for 2.6.0-test9 only) to check for netdev= boot options. I have verified that this change works (on 2.6.0-test9) when using an Intel; /archives/netdev/2003-11/msg00108.html (10,007 bytes)
2. Re: [PATCH/RFC] enabling netdev boot options (score: 1): Author: ap" <rddunlap@xxxxxxxx>; Date: Sat, 8 Nov 2003 16:22:48 -0800; A worthy project, thanks. It would be better to move this locking into the core net layer. Call dev_alloc_name_which_takes_rtnl_lock() here ;) This causes an rtnl_unlock() imbalance if vortex_probe1(; /archives/netdev/2003-11/msg00109.html (8,805 bytes)
3. Re: [PATCH/RFC] enabling netdev boot options (score: 1): Author: Morton <akpm@xxxxxxxx>; Date: Sat, 8 Nov 2003 17:03:42 -0800; Makes sense, but I'm wary of some drivers which do rtnl_lock() early and hold it for long times (like eepro100). Methinks that it shouldn't do that, but that's a different patch. I'll check that agai; /archives/netdev/2003-11/msg00110.html (9,053 bytes)
4. Re: [PATCH/RFC] enabling netdev boot options (score: 1): Author: ap" <rddunlap@xxxxxxxx>; Date: Sat, 8 Nov 2003 18:51:23 -0800; [snip] Yes, that's right. Updated patch is below (for 2.4.22), still using rtnl_lock() and rtnl_unlock(). I'll make a locking version of dev_alloc_name() next [for 2.6], as well as 2.6.0-test9 patch; /archives/netdev/2003-11/msg00111.html (10,138 bytes)
5. [PATCH/RFC] enabling netdev boot options (score: 1): Author: "Randy.Dunlap" <rddunlap@xxxxxxxx>; Date: Sat, 8 Nov 2003 16:04:16 -0800; I have modified 3c59x.c (for 2.4.22 and 2.6.0-test9) and eepro100 (for 2.6.0-test9 only) to check for netdev= boot options. I have verified that this change works (on 2.6.0-test9) when using an Intel; /archives/netdev/2003-11/msg00721.html (10,007 bytes)
6. Re: [PATCH/RFC] enabling netdev boot options (score: 1): Author: Andrew Morton <akpm@xxxxxxxx>; Date: Sat, 8 Nov 2003 16:22:48 -0800; A worthy project, thanks. It would be better to move this locking into the core net layer. Call dev_alloc_name_which_takes_rtnl_lock() here ;) This causes an rtnl_unlock() imbalance if vortex_probe1(; /archives/netdev/2003-11/msg00722.html (8,885 bytes)
7. Re: [PATCH/RFC] enabling netdev boot options (score: 1): Author: "Randy.Dunlap" <rddunlap@xxxxxxxx>; Date: Sat, 8 Nov 2003 17:03:42 -0800; Makes sense, but I'm wary of some drivers which do rtnl_lock() early and hold it for long times (like eepro100). Methinks that it shouldn't do that, but that's a different patch. I'll check that agai; /archives/netdev/2003-11/msg00723.html (9,165 bytes)
8. Re: [PATCH/RFC] enabling netdev boot options (score: 1): Author: "Randy.Dunlap" <rddunlap@xxxxxxxx>; Date: Sat, 8 Nov 2003 18:51:23 -0800; [snip] Yes, that's right. Updated patch is below (for 2.4.22), still using rtnl_lock() and rtnl_unlock(). I'll make a locking version of dev_alloc_name() next [for 2.6], as well as 2.6.0-test9 patch; /archives/netdev/2003-11/msg00724.html (10,250 bytes)

Current List: 1 - 8
Page: [1]