From: Hugh Dickins <hugh@veritas.com>
To: Robin Holt <holt@sgi.com>
Cc: Andrew Morton <akpm@osdl.org>, Dave Hansen <haveblue@us.ibm.com>,
Greg KH <greg@kroah.com>, ia64 list <linux-ia64@vger.kernel.org>,
linux-mm <linux-mm@kvack.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
hch@infradead.org, jgarzik@pobox.com,
William Lee Irwin III <wli@holomorphy.com>,
Nick Piggin <nickpiggin@yahoo.com.au>,
Carsten Otte <cotte@de.ibm.com>,
Jack Steiner <steiner@americas.sgi.com>
Subject: Re: [Patch 2/3] Export get_one_pte_map.
Date: Mon, 17 Oct 2005 16:59:20 +0100 (BST) [thread overview]
Message-ID: <Pine.LNX.4.61.0510171644220.4773@goblin.wat.veritas.com> (raw)
In-Reply-To: <20051017151430.GA2564@lnx-holt.americas.sgi.com>
On Mon, 17 Oct 2005, Robin Holt wrote:
>
> I am currently getting pressure from my management to get something
> checked into the tree for 2.6.15.
I'm sorry to hear that, but it's not a kernel development priority.
And since I'm nearing completion of a task which we expect to satisfy
what SGI's been asking for almost a year, which I had been obstructing,
I'm disinclined to drop it now in order to help meet their latest fancy.
> Would it be reasonable to ask
> that the current patch be included and then I work up another patch
> which introduces a ->nopfn type change for the -mm tree?
I'm definitely not in charge here, and cannot answer that. But I
think it's unlikely, unless Linus and Andrew are pretty sure that
what you have now is really the way they want to go in the long term.
You will, as ever, be entitled to apply your patch on top of 2.6.15
(but it may not apply without some changes).
Repeating a technical question (sorry, that now seems off-topic!):
what do you expect to happen with PROT_WRITE, MAP_PRIVATE?
Hugh
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2005-10-17 15:59 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-14 19:21 [Patch 0/3] SGI Altix and ia64 special memory support Robin Holt
2005-10-14 19:21 ` [Patch 1/3] Add a NOPAGE_FAULTED flag Robin Holt
2005-10-14 19:22 ` [Patch 2/3] Export get_one_pte_map Robin Holt
2005-10-14 21:30 ` Greg KH
2005-10-17 11:31 ` Robin Holt
2005-10-17 11:36 ` Christoph Hellwig
2005-10-17 11:39 ` Robin Holt
2005-10-17 11:41 ` Dave Hansen
2005-10-17 11:47 ` Robin Holt
2005-10-17 12:33 ` Hugh Dickins
2005-10-17 15:14 ` Robin Holt
2005-10-17 15:20 ` Greg KH
2005-10-17 15:56 ` Robin Holt
2005-10-17 16:05 ` Greg KH
2005-10-17 16:09 ` Dave Hansen
2005-10-17 16:14 ` Hugh Dickins
2005-10-17 20:53 ` Andrew Morton
2005-10-18 8:48 ` Carsten Otte
2005-10-17 15:59 ` Hugh Dickins [this message]
2005-10-17 20:25 ` Robin Holt
2005-10-17 20:59 ` Hugh Dickins
2005-10-18 23:28 ` William Lee Irwin III
2005-10-14 19:22 ` [Patch 3/3] Special Memory (mspec) driver Robin Holt
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=Pine.LNX.4.61.0510171644220.4773@goblin.wat.veritas.com \
--to=hugh@veritas.com \
--cc=akpm@osdl.org \
--cc=cotte@de.ibm.com \
--cc=greg@kroah.com \
--cc=haveblue@us.ibm.com \
--cc=hch@infradead.org \
--cc=holt@sgi.com \
--cc=jgarzik@pobox.com \
--cc=linux-ia64@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=nickpiggin@yahoo.com.au \
--cc=steiner@americas.sgi.com \
--cc=wli@holomorphy.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