Andrew Morton wrote:
Should we also decrease the polling interval? Perhaps only when the cable is unplugged?
Sounds like a plan. 60 seconds certainly strikes me as being very slow. OTOH, I'm not aware of the reasoning behind this choice in the first place. It might make sense for some odd setups. Since I don't even have any HW to play around with, I think I'll step down for now. -Tommy - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
- Follow-Ups:
- Re: [PATCH] 3c59x: read current link status from phy
- From: Jeff Garzik <jgarzik@pobox.com>
- Re: [PATCH] 3c59x: read current link status from phy
- References:
- Re: [PATCH] 3c59x: read current link status from phy
- From: Jeff Garzik <jgarzik@pobox.com>
- Re: [PATCH] 3c59x: read current link status from phy
- From: Bogdan Costescu <Bogdan.Costescu@iwr.uni-heidelberg.de>
- Re: [PATCH] 3c59x: read current link status from phy
- From: Tommy Christensen <tommy.christensen@tpack.net>
- Re: [PATCH] 3c59x: read current link status from phy
- From: Bogdan Costescu <Bogdan.Costescu@iwr.uni-heidelberg.de>
- Re: [PATCH] 3c59x: read current link status from phy
- From: Tommy Christensen <tommy.christensen@tpack.net>
- Re: [PATCH] 3c59x: read current link status from phy
- From: Bogdan Costescu <Bogdan.Costescu@iwr.uni-heidelberg.de>
- Re: [PATCH] 3c59x: read current link status from phy
- From: Tommy Christensen <tommy.christensen@tpack.net>
- Re: [PATCH] 3c59x: read current link status from phy
- From: Andrew Morton <akpm@osdl.org>
- Re: [PATCH] 3c59x: read current link status from phy
- Prev by Date: Re: [ckrm-tech] Re: [PATCH 0/5] SUBCPUSETS: a resource control functionality using CPUSETS
- Next by Date: RE: can't boot 2.6.13
- Previous by thread: Re: [PATCH] 3c59x: read current link status from phy
- Next by thread: Re: [PATCH] 3c59x: read current link status from phy
- Index(es):
