* Andrew Morton <[email protected]> wrote: > Well OK. But vdso-print-fatal-signals.patch is designated > not-for-mainline anyway. btw., why? It's very, very useful to distro, early-boot-userspace and glibc development. The only add-on change should be to not print SIGKILL events. Otherwise it's very much a keeper. Hm? Ingo - 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 1/2] limit print_fatal_signal() rate (was: [RFC] log out-of-virtual-memory events)
- From: Ingo Molnar <[email protected]>
- Re: [PATCH 1/2] limit print_fatal_signal() rate
- From: Andrea Righi <[email protected]>
- Re: [PATCH 1/2] limit print_fatal_signal() rate (was: [RFC] log out-of-virtual-memory events)
- From: Andrew Morton <[email protected]>
- Re: [PATCH 1/2] limit print_fatal_signal() rate (was: [RFC] log out-of-virtual-memory events)
- References:
- Re: [RFC] log out-of-virtual-memory events
- From: Bernd Eckenfels <[email protected]>
- [PATCH 1/2] limit print_fatal_signal() rate (was: [RFC] log out-of-virtual-memory events)
- From: Andrea Righi <[email protected]>
- Re: [PATCH 1/2] limit print_fatal_signal() rate (was: [RFC] log out-of-virtual-memory events)
- From: Andrew Morton <[email protected]>
- Re: [RFC] log out-of-virtual-memory events
- Prev by Date: Re: [PATCH 1/1] hotplug cpu: migrate a task within its cpuset
- Next by Date: Re: RSS controller v2 Test results (lmbench )
- Previous by thread: Re: [PATCH 1/2] limit print_fatal_signal() rate
- Next by thread: Re: [PATCH 1/2] limit print_fatal_signal() rate (was: [RFC] log out-of-virtual-memory events)
- Index(es):
 |