Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <1529618574.29548.207.camel@intel.com>
Date: Thu, 21 Jun 2018 22:02:39 +0000
From: "Edgecombe, Rick P" <rick.p.edgecombe@...el.com>
To: "willy@...radead.org" <willy@...radead.org>
CC: "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>, "Van De
 Ven, Arjan" <arjan.van.de.ven@...el.com>, "tglx@...utronix.de"
	<tglx@...utronix.de>, "linux-mm@...ck.org" <linux-mm@...ck.org>,
	"x86@...nel.org" <x86@...nel.org>, "Accardi, Kristen C"
	<kristen.c.accardi@...el.com>, "hpa@...or.com" <hpa@...or.com>,
	"mingo@...hat.com" <mingo@...hat.com>, "kernel-hardening@...ts.openwall.com"
	<kernel-hardening@...ts.openwall.com>, "Hansen, Dave" <dave.hansen@...el.com>
Subject: Re: [PATCH 1/3] vmalloc: Add __vmalloc_node_try_addr function

On Wed, 2018-06-20 at 15:26 -0700, Matthew Wilcox wrote:
> Not needed:
> 
> void warn_alloc(gfp_t gfp_mask, nodemask_t *nodemask, const char
> *fmt, ...)
> {
> ...
>         if ((gfp_mask & __GFP_NOWARN) || !__ratelimit(&nopage_rs))
>                 return;
> 
Yes, thanks!

Powered by blists - more mailing lists

Confused about mailing lists and their use? Read about mailing lists on Wikipedia and check out these guidelines on proper formatting of your messages.