From: "Edgecombe, Rick P" <rick.p.edgecombe@intel.com>
To: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"peterz@infradead.org" <peterz@infradead.org>,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"sparclinux@vger.kernel.org" <sparclinux@vger.kernel.org>,
"luto@amacapital.net" <luto@amacapital.net>
Cc: "davem@davemloft.net" <davem@davemloft.net>,
"namit@vmware.com" <namit@vmware.com>,
"Hansen, Dave" <dave.hansen@intel.com>
Subject: Re: [PATCH v2 0/2] Fix issues with vmalloc flush flag
Date: Mon, 20 May 2019 23:46:21 +0000 [thread overview]
Message-ID: <d92aa15b453b2a53bcd0bbaa8f35e8151eaae17b.camel@intel.com> (raw)
In-Reply-To: <20190520233841.17194-1-rick.p.edgecombe@intel.com>
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.
WARNING: multiple messages have this Message-ID (diff)
From: "Edgecombe, Rick P" <rick.p.edgecombe@intel.com>
To: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"peterz@infradead.org" <peterz@infradead.org>,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"sparclinux@vger.kernel.org" <sparclinux@vger.kernel.org>,
"luto@amacapital.net" <luto@amacapital.net>
Cc: "davem@davemloft.net" <davem@davemloft.net>,
"namit@vmware.com" <namit@vmware.com>,
"Hansen, Dave" <dave.hansen@intel.com>
Subject: Re: [PATCH v2 0/2] Fix issues with vmalloc flush flag
Date: Mon, 20 May 2019 23:46:21 +0000 [thread overview]
Message-ID: <d92aa15b453b2a53bcd0bbaa8f35e8151eaae17b.camel@intel.com> (raw)
In-Reply-To: <20190520233841.17194-1-rick.p.edgecombe@intel.com>
T24gTW9uLCAyMDE5LTA1LTIwIGF0IDE2OjM4IC0wNzAwLCBSaWNrIEVkZ2Vjb21iZSB3cm90ZToN
Cj4gVGhlc2UgdHdvIHBhdGNoZXMgYWRkcmVzcyBpc3N1ZXMgd2l0aCB0aGUgcmVjZW50bHkgYWRk
ZWQNCj4gVk1fRkxVU0hfUkVTRVRfUEVSTVMgdm1hbGxvYyBmbGFnLiBJdCBpcyBub3cgc3BsaXQg
aW50byB0d28gcGF0Y2hlcywNCj4gd2hpY2gNCj4gbWFkZSBzZW5zZSB0byBtZSwgYnV0IGNhbiBz
cGxpdCBpdCBmdXJ0aGVyIGlmIGRlc2lyZWQuDQo+IA0KT29wcywgdGhpcyB3YXMgc3VwcG9zZWQg
dG8gc2F5IFBBVENIIHYzLiBMZXQgbWUga25vdyBpZiBJIHNob3VsZA0KcmVzZW5kLg0K
next prev parent reply other threads:[~2019-05-20 23:46 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-20 23:38 [PATCH v2 0/2] Fix issues with vmalloc flush flag Rick Edgecombe
2019-05-20 23:38 ` Rick Edgecombe
2019-05-20 23:38 ` [PATCH v2 1/2] vmalloc: Fix calculation of direct map addr range Rick Edgecombe
2019-05-20 23:38 ` Rick Edgecombe
2019-05-20 23:38 ` [PATCH v2 2/2] vmalloc: Remove work as from vfree path Rick Edgecombe
2019-05-20 23:38 ` Rick Edgecombe
2019-05-21 16:17 ` Andy Lutomirski
2019-05-21 16:17 ` Andy Lutomirski
2019-05-21 16:17 ` Andy Lutomirski
2019-05-21 16:51 ` Edgecombe, Rick P
2019-05-21 16:51 ` Edgecombe, Rick P
2019-05-21 17:00 ` Andy Lutomirski
2019-05-21 17:00 ` Andy Lutomirski
2019-05-21 17:00 ` Andy Lutomirski
2019-05-21 19:47 ` Edgecombe, Rick P
2019-05-21 19:47 ` Edgecombe, Rick P
2019-05-20 23:46 ` Edgecombe, Rick P [this message]
2019-05-20 23:46 ` [PATCH v2 0/2] Fix issues with vmalloc flush flag Edgecombe, Rick P
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=d92aa15b453b2a53bcd0bbaa8f35e8151eaae17b.camel@intel.com \
--to=rick.p.edgecombe@intel.com \
--cc=dave.hansen@intel.com \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=luto@amacapital.net \
--cc=namit@vmware.com \
--cc=netdev@vger.kernel.org \
--cc=peterz@infradead.org \
--cc=sparclinux@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.