From: Dave Hansen <dave.hansen@intel.com>
To: Andrew Morton <akpm@linux-foundation.org>,
Naoya Horiguchi <n-horiguchi@ah.jp.nec.com>
Cc: jwboyer@fedoraproject.org, Sasha Levin <sasha.levin@oracle.com>,
torvalds@linux-foundation.org, linux-kernel@vger.kernel.org
Subject: Re: pte_present check on hugetlb_entry fix for 3.15?
Date: Fri, 06 Jun 2014 13:11:00 -0700 [thread overview]
Message-ID: <53922054.6020108@intel.com> (raw)
In-Reply-To: <20140606115919.df17197c7182a0f7ed59c3a9@linux-foundation.org>
On 06/06/2014 11:59 AM, Andrew Morton wrote:
> On Fri, 6 Jun 2014 14:46:37 -0400 Naoya Horiguchi <n-horiguchi@ah.jp.nec.com> wrote:
>> On Fri, Jun 06, 2014 at 01:36:54PM -0400, Josh Boyer wrote:
>>> Hi Naoya,
>>>
>>> I noticed that your
>>> mm-add-pte_present-check-on-existing-hugetlb_entry-callbacks.patch in
>>> Andrew's -mm tree has been queued for a while and has a CC to stable on
>>> it. Is that something that should get into 3.15?
>>
>> I'm not sure. I guess Andrew will decide this in a few days.
>
> I was planning on doing so but then Dave popped up with an alternative
> which rather blew a hole in things.
This one patch is independent from what I was posting. I don't think my
patch would have had any effect on the behavior this one is fixing.
IOW, don't hold it up for my (or my patches) benefit.
next prev parent reply other threads:[~2014-06-06 20:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-06 17:36 pte_present check on hugetlb_entry fix for 3.15? Josh Boyer
[not found] ` <53920c95.685a8c0a.2111.ffffe52fSMTPIN_ADDED_BROKEN@mx.google.com>
2014-06-06 18:59 ` Andrew Morton
2014-06-06 20:11 ` Dave Hansen [this message]
2014-06-06 20:19 ` Andrew Morton
[not found] ` <1402080393-n2hosalz@n-horiguchi@ah.jp.nec.com>
2014-06-06 20:15 ` Sasha Levin
2014-06-06 20:28 ` Linus Torvalds
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=53922054.6020108@intel.com \
--to=dave.hansen@intel.com \
--cc=akpm@linux-foundation.org \
--cc=jwboyer@fedoraproject.org \
--cc=linux-kernel@vger.kernel.org \
--cc=n-horiguchi@ah.jp.nec.com \
--cc=sasha.levin@oracle.com \
--cc=torvalds@linux-foundation.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox