Re: [PATCH 2/3] Adjust Netpoll timeout logic

Michael Frank wrote: Current Netpoll init does not trust carrier detected right upon bringing the NIC up and waits for a delay before allowing boot to continue. The delay varied with the kernel version: 10 seconds in 2.6.11 3 seconds in 2.6.12 4 seconds in 2.6.13 and later Any signifi

[PATCH 3/3] Netconsole buffering

Kernel messages are often assembled from numerical and text fragments. Sending fragments via UDP often produces one line per fragment on the other end. Example: Pseudo code: printk "a message: " ... printk "%d, " 1234 ...   

[PATCH 2/3] Adjust Netpoll timeout logic

Current Netpoll init does not trust carrier detected right upon bringing  the NIC up and waits for a delay before allowing boot to continue. The delay varied with the kernel version:  10 seconds in 2.6.11    3 seconds in 2.6.12    4 seconds in 2.6.13 and later Any significant delay is undesired

[PATCH 1/3] Netconsole cleanups

Some cleanups in preparation of further work. Signed-off-by: Michael Frank <[EMAIL PROTECTED]> ---  drivers/net/netconsole.c |   46 -  net/core/netpoll.c       |  127 +--  2 files changed, 91 insertions(+), 82 deletions(-) Patch file:

Test

Sorry for the noise - To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html

Setting ipv6 route flags

OK, This time without typos. Hi, I realized that in net/ipv6/route.c in the inet6_rtm_new_route() function the call to inet6_rtm_to_rtmsg() does not take into account the user supplied flags. This way it seems to be not possible to set the RTF_DEFAULT flag of a default route (dest address being "