On Wed, 20 Jun 2007, Alexander Gabert wrote: > > this patch adds the function drivers/char/random.c:get_random_long() It's totally whitespace-damaged, and I wonder why the "int" vs "long" is so important. Also, what are the performance implications for execve? Linus - 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/
- References:
- AT_ENTROPY1 and AT_ENTROPY2 values for include/linux/auxvec.h
- From: Alexander Gabert <[email protected]>
- Re: AT_ENTROPY1 and AT_ENTROPY2 values for include/linux/auxvec.h
- From: Arjan van de Ven <[email protected]>
- Re: AT_ENTROPY1 and AT_ENTROPY2 values for include/linux/auxvec.h
- From: Alexander Gabert <[email protected]>
- Re: AT_ENTROPY1 and AT_ENTROPY2 values for include/linux/auxvec.h
- From: Arjan van de Ven <[email protected]>
- Re: AT_ENTROPY1 and AT_ENTROPY2 values for include/linux/auxvec.h
- From: Alexander Gabert <[email protected]>
- [PATCH] get_random_long() and AT_ENTROPY for auxv, kernel 2.6.21.5
- From: Alexander Gabert <[email protected]>
- AT_ENTROPY1 and AT_ENTROPY2 values for include/linux/auxvec.h
- Prev by Date: Re: JIT emulator needs
- Next by Date: Re: [PATCH] remove usage of memmem from scripts/kallsyms.c
- Previous by thread: Re: [PATCH] get_random_long() and AT_ENTROPY for auxv, kernel 2.6.21.5
- Next by thread: Re: [PATCH] get_random_long() and AT_ENTROPY for auxv, kernel 2.6.21.5
- Index(es):
 |