linux-kernel - Re: [PATCH 0/8] mtd: 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>] [day] [month] [year] [list]

Message-ID: <20140211185013.GH18440@ld-irv-0074>
Date:	Tue, 11 Feb 2014 10:50:13 -0800
From:	Brian Norris <computersforpeace@...il.com>
To:	Jingoo Han <jg1.han@...sung.com>
Cc:	'David Woodhouse' <dwmw2@...radead.org>,
	linux-mtd@...ts.infradead.org,
	Linux Kernel <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 0/8] mtd: Remove unnecessary OOM messages

On Thu, Feb 06, 2014 at 03:07:19PM +0900, 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 (8):
>       mtd: devices: elm: Remove unnecessary OOM messages
>       mtd: spear_smi: Remove unnecessary OOM messages
>       mtd: pmc551: Remove unnecessary OOM messages
>       mtd: plat-ram: Remove unnecessary OOM messages
>       mtd: lpddr: Remove unnecessary OOM messages
>       mtd: onenand: Remove unnecessary OOM messages
>       mtd: cfi: Remove unnecessary OOM messages
>       mtd: gen_probe: Remove unnecessary OOM messages

Pushed all 8 to l2-mtd.git. Thanks.

Have you ever considered using a tool like coccinelle to do this sort of
work? You send so many of these boilerplate patch series, I would think
it would help everyone to just get them out of the way with scripted
assistance. And you could then more easily catch new introductions if
they slip through the review process.

Brian
--
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/