linux-kernel - Re: [RFC PATCH] checkpatch: Attempt to find unnecessary 'out of memory' 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] [thread-next>] [day] [month] [year] [list]

Date:	Sat, 14 Jun 2014 01:30:15 -0700
From:	Joe Perches <joe@...ches.com>
To:	Julia Lawall <julia.lawall@...6.fr>
Cc:	Dan Carpenter <dan.carpenter@...cle.com>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Andy Whitcroft <apw@...dowen.org>,
	LKML <linux-kernel@...r.kernel.org>, benoit.taine@...6.fr
Subject: Re: [RFC PATCH] checkpatch: Attempt to find unnecessary 'out of
 memory' messages

On Sat, 2014-06-14 at 09:40 +0200, Julia Lawall wrote:
> With a semantic patch that searches for the various calls and then a 
> string containing the letters "emory", I get removals of the messages 
> below.  Do any of these messages look useful?  For example, some are 
> generated with specific functions, such as IRDA_ERROR or BT_ERR.  If none 
> of the messages look useful, should just one big patch go to trivial, or 
> should the patches go to the individual maintainers?
> 
> julia

Hi Julia.

There was no attachment or "below" for your email.

I expect that these should go first to individual
maintainers, then after that and a kernel release
later, then to trivial.


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