linux-kernel - Re: [PATCH 0/4] clocksource: remove unnecessary OOM messages

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <537DE835.5010703@linaro.org>
Date:	Thu, 22 May 2014 14:06:13 +0200
From:	Daniel Lezcano <daniel.lezcano@...aro.org>
To:	Jingoo Han <jg1.han@...sung.com>
CC:	'Thomas Gleixner' <tglx@...utronix.de>,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH 0/4] clocksource: remove unnecessary OOM messages

On 04/29/2014 10:24 AM, Jingoo Han wrote:
> 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(-)

Applied to my tree for 3.16 with some slight changes due to Laurent's 
changes (kmalloc -> kzalloc).

Thanks !
   -- Daniel


-- 
  <http://www.linaro.org/> Linaro.org │ Open source software for ARM SoCs

Follow Linaro:  <http://www.facebook.com/pages/Linaro> Facebook |
<http://twitter.com/#!/linaroorg> Twitter |
<http://www.linaro.org/linaro-blog/> Blog

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/