linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@osdl.org>
To: Hugh Dickins <hugh@veritas.com>
Cc: holt@sgi.com, greg@kroah.com, haveblue@us.ibm.com,
	linux-ia64@vger.kernel.org, linux-mm@kvack.org,
	linux-kernel@vger.kernel.org, hch@infradead.org,
	jgarzik@pobox.com, wli@holomorphy.com, nickpiggin@yahoo.com.au,
	cotte@de.ibm.com, steiner@americas.sgi.com
Subject: Re: [Patch 2/3] Export get_one_pte_map.
Date: Mon, 17 Oct 2005 13:53:14 -0700	[thread overview]
Message-ID: <20051017135314.3a59fb17.akpm@osdl.org> (raw)
In-Reply-To: <Pine.LNX.4.61.0510171700150.4934@goblin.wat.veritas.com>

Hugh Dickins <hugh@veritas.com> wrote:
>
> On Mon, 17 Oct 2005, Robin Holt wrote:
> > On Mon, Oct 17, 2005 at 08:20:34AM -0700, Greg KH wrote:
> > > 
> > > 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.
> 
> The stuff in -mm is a best guess at what's going to be in 2.6.15,
> but it's far from exact and certain.
> 
> > 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?
> 
> That's a question for Andrew (added to CC in case he's not receiving
> enough copies of this mail ;-), and it's too soon to tell - changes
> which have only just been exposed in 2.6.14-rc4-mm1 are not yet
> mature enough for a judgement.
> 
> I've still got stuff to come, to make full sense of what's already in:
> if I were Andrew, given the faster releases we're going for now, I'd
> currently be in some doubt about whether to push that for 2.6.15.

Ther are nearly 100 mm patches in -mm.  I need to do a round of discussion
with the originators to work out what's suitable for 2.6.15.  For "Hugh
stuff" I'm thinking maybe the first batch
(mm-hugetlb-truncation-fixes.patch to mm-m68k-kill-stram-swap.patch) and
not the second batch.  But we need to think about it.

> Perhaps he'll be more comfortable with yours, feel it's the right
> way to go, and want to put it ahead of what's presently in -mm.
> Or perhaps not.

The mspec driver?  That work should be based on the mm patches in rc4-mm1,
I guess.  Its impact on core mm is small, so we should be able to get it
into 2.6.15.

--
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 20:53 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 [this message]
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=20051017135314.3a59fb17.akpm@osdl.org \
    --to=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=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