YOSHIFUJI Hideaki / 吉藤英明 <[email protected]> writes: > Would you explain why it does not work properly > for those cases? Mostly no appropriate strategy routine was setup to report the data to the caller of sys_sysctl. Eric - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] 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 04/10] sysctl: Fix neighbour table sysctls.
- From: YOSHIFUJI Hideaki / 吉藤英明 <[email protected]>
- Re: [PATCH 04/10] sysctl: Fix neighbour table sysctls.
- References:
- [PATCH 04/10] sysctl: Fix neighbour table sysctls.
- From: [email protected] (Eric W. Biederman)
- Re: [PATCH 04/10] sysctl: Fix neighbour table sysctls.
- From: YOSHIFUJI Hideaki / 吉藤英明 <[email protected]>
- Re: [PATCH 04/10] sysctl: Fix neighbour table sysctls.
- From: David Miller <[email protected]>
- Re: [PATCH 04/10] sysctl: Fix neighbour table sysctls.
- From: YOSHIFUJI Hideaki / 吉藤英明 <[email protected]>
- [PATCH 04/10] sysctl: Fix neighbour table sysctls.
- Prev by Date: Re: 2.6.23-rc2-mm1: rcutorture xtime usage
- Next by Date: Re: [PATCH 04/10] sysctl: Fix neighbour table sysctls.
- Previous by thread: Re: [PATCH 04/10] sysctl: Fix neighbour table sysctls.
- Next by thread: Re: [PATCH 04/10] sysctl: Fix neighbour table sysctls.
- Index(es):
 |