[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <d92aa15b453b2a53bcd0bbaa8f35e8151eaae17b.camel@intel.com>
Date: Mon, 20 May 2019 23:46:21 +0000
From: "Edgecombe, Rick P" <rick.p.edgecombe@...el.com>
To: "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"peterz@...radead.org" <peterz@...radead.org>,
"linux-mm@...ck.org" <linux-mm@...ck.org>,
"netdev@...r.kernel.org" <netdev@...r.kernel.org>,
"sparclinux@...r.kernel.org" <sparclinux@...r.kernel.org>,
"luto@...capital.net" <luto@...capital.net>
CC: "davem@...emloft.net" <davem@...emloft.net>,
"namit@...are.com" <namit@...are.com>,
"Hansen, Dave" <dave.hansen@...el.com>
Subject: Re: [PATCH v2 0/2] Fix issues with vmalloc flush flag
On Mon, 2019-05-20 at 16:38 -0700, Rick Edgecombe wrote:
> These two patches address issues with the recently added
> VM_FLUSH_RESET_PERMS vmalloc flag. It is now split into two patches,
> which
> made sense to me, but can split it further if desired.
>
Oops, this was supposed to say PATCH v3. Let me know if I should
resend.
Powered by blists - more mailing lists