linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Robin Holt <holt@sgi.com>
Cc: Hugh Dickins <hugh@veritas.com>,
	Dave Hansen <haveblue@us.ibm.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 09:05:59 -0700	[thread overview]
Message-ID: <20051017160559.GA315@kroah.com> (raw)
In-Reply-To: <20051017155605.GB2564@lnx-holt.americas.sgi.com>

On Mon, Oct 17, 2005 at 10:56:05AM -0500, Robin Holt wrote:
> On Mon, Oct 17, 2005 at 08:20:34AM -0700, Greg KH wrote:
> > > 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?
> > 
> > The stuff in -mm is what is going to be in .15, so you have to work off
> > of that patchset if you wish to have something for .15.
> 
> Is everything in the mm/ directory from the -mm tree going into .15 or
> is there a planned subset?  What should I develop against to help ensure
> I match up with the community?

-mm is "the community" :)

But Hugh would have the best answer for this, as he knows what he will
be sending in for .15, so at the least, work off of his patches in
there.

Good luck,

greg k-h

--
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>

  reply	other threads:[~2005-10-17 16:05 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 [this message]
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
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=20051017160559.GA315@kroah.com \
    --to=greg@kroah.com \
    --cc=cotte@de.ibm.com \
    --cc=haveblue@us.ibm.com \
    --cc=hch@infradead.org \
    --cc=holt@sgi.com \
    --cc=hugh@veritas.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