The site-specific OOM messages are unnecessary, because they
duplicate the MM subsystem generic OOM message. For example,
k.alloc and v.alloc failures use dump_stack().
Jingoo Han (4):
clocksource: em_sti: remove unnecessary OOM messages
clocksource: sh_cmt: remove unnecessary OOM messages
clocksource: sh_mtu2: remove unnecessary OOM messages
clocksource: sh_tmu: remove unnecessary OOM messages
---
drivers/clocksource/em_sti.c | 4 +---
drivers/clocksource/sh_cmt.c | 4 +---
drivers/clocksource/sh_mtu2.c | 4 +---
drivers/clocksource/sh_tmu.c | 4 +---
4 files changed, 4 insertions(+), 12 deletions(-)
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
