From: Ingo Molnar <mingo@elte.hu>
To: "Pallipadi, Venkatesh" <venkatesh.pallipadi@intel.com>,
Andrew Morton <akpm@linux-foundation.org>,
Nick Piggin <npiggin@suse.de>, Hugh Dickins <hugh@veritas.com>
Cc: "hpa@zytor.com" <hpa@zytor.com>,
"tglx@linutronix.de" <tglx@linutronix.de>,
linux-kernel@vger.kernel.org
Subject: Re: [patch 0/7] x86 PAT: v2 - track pfnmap mappings with remap_pfn_range and vm_insert_pfn
Date: Tue, 16 Dec 2008 20:51:54 +0100 [thread overview]
Message-ID: <20081216195154.GB4501@elte.hu> (raw)
In-Reply-To: <7E82351C108FA840AB1866AC776AEC464338C11E@orsmsx505.amr.corp.intel.com>
* Pallipadi, Venkatesh <venkatesh.pallipadi@intel.com> wrote:
> Ingo,
>
> Haven't seen any comments on the patches here. Can you push these
> patches along to tip.
while the main focus of the changes are x86, they touch the MM
non-trivially too:
include/linux/mm.h | 9 +++++++++
mm/memory.c | 7 +++----
2 files changed, 12 insertions(+), 4 deletions(-)
mm/memory.c | 2 ++
1 file changed, 2 insertions(+)
include/linux/mm.h | 3 +++
mm/memory.c | 43 +++++++++++++++++++++++++++++++++++++++++++
2 files changed, 46 insertions(+)
include/linux/mm.h | 6 +++++
mm/memory.c | 54 ++++++++++++++++++++++++++++++++++++++++++++++++++++-
2 files changed, 59 insertions(+), 1 deletion(-)
So when you sent this a month ago i asked the MM folks whether they have
any problems with these patches. Acks (or objections) from Andrew, Nick or
Hugh would be nice to have.
Ingo
next prev parent reply other threads:[~2008-12-16 19:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20081126002157.475142000@intel.com>
2008-12-15 21:50 ` Pallipadi, Venkatesh
2008-12-16 19:51 ` Ingo Molnar [this message]
2008-12-16 22:05 ` Nick Piggin
2008-12-16 22:07 ` Ingo Molnar
2008-12-17 8:19 ` Nick Piggin
2008-12-18 14:31 ` Ingo Molnar
2008-12-18 17:16 ` Pallipadi, Venkatesh
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=20081216195154.GB4501@elte.hu \
--to=mingo@elte.hu \
--cc=akpm@linux-foundation.org \
--cc=hpa@zytor.com \
--cc=hugh@veritas.com \
--cc=linux-kernel@vger.kernel.org \
--cc=npiggin@suse.de \
--cc=tglx@linutronix.de \
--cc=venkatesh.pallipadi@intel.com \
/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
all inboxes | Powered by JetHome®