All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: Paul Mundt <lethal@linux-sh.org>
Cc: magnus.damm@gmail.com, linux-fbdev-devel@lists.sourceforge.net,
	adaplas@gmail.com, arnd@arndb.de, linux-mm@kvack.org,
	jayakumar.lkml@gmail.com
Subject: Re: [PATCH] video: arch specific page protection support for deferred  io
Date: Thu, 25 Jun 2009 11:12:33 -0700	[thread overview]
Message-ID: <20090625111233.f6f26050.akpm@linux-foundation.org> (raw)
In-Reply-To: <20090625173806.GB25320@linux-sh.org>

On Fri, 26 Jun 2009 02:38:06 +0900
Paul Mundt <lethal@linux-sh.org> wrote:

> On Thu, Jun 25, 2009 at 12:03:59AM -0700, Andrew Morton wrote:
> > On Thu, 25 Jun 2009 15:06:24 +0900 Magnus Damm <magnus.damm@gmail.com> wrote:
> > > There are 3 levels of dependencies:
> > > 1: pgprot_noncached() patches from Arnd
> > > 2: mm: uncached vma support with writenotify
> > > 3: video: arch specfic page protection support for deferred io
> > > 
> > > 2 depends on 1 to compile, but 3 (this one) is disconnected from 2 and
> > > 1. So this patch can be merged independently.
> > 
> > OIC.  I didn't like the idea of improper runtime operation ;)
> > 
> > Still, it's messy.  If only because various trees might be running
> > untested combinations of patches.  Can we get these all into the same
> > tree?  Paul's?
> > 
> #1 is a bit tricky. cris has already merged the pgprot_noncached() patch,
> which means only m32r and xtensa are outstanding, and unfortunately
> neither one of those is very fast to pick up changes. OTOH, both of those
> do include asm-generic/pgtable.h, so the build shouldn't break in -next
> for those two if I merge #2 and #3, even if the behaviour won't be
> correct for those platforms until they merge their pgprot_noncached()
> patches (I think this is ok, since it's not changing any behaviour they
> experience today anyways).
> 
> It would be nice to have an ack from someone for #2 before merging it,
> but it's been out there long enough that people have had ample time to
> raise objections.
> 
> So I'll make this the last call for acks or nacks on #2 and #3, if none
> show up in the next couple of days, I'll fold them in to my tree and
> they'll show up in -next starting next week.

Well my head span off ages ago.  Could someone please resend all three
patches?

<hunts around and finds #2>

I don't really understand that one.  Have we heard fro Jaya recently?

--
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:[~2009-06-25 18:12 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-24 10:54 [PATCH] video: arch specific page protection support for deferred io Magnus Damm
2009-06-25  2:56 ` Andrew Morton
2009-06-25  3:09   ` Paul Mundt
2009-06-25  3:15     ` Andrew Morton
2009-06-25  6:06   ` Magnus Damm
2009-06-25  6:06     ` Magnus Damm
2009-06-25  7:03     ` Andrew Morton
2009-06-25 17:38       ` Paul Mundt
2009-06-25 18:12         ` Andrew Morton [this message]
2009-06-25 18:36           ` Jaya Kumar
2009-06-25 18:36             ` Jaya Kumar
2009-06-25 18:50             ` Paul Mundt
2009-06-26  7:50           ` Magnus Damm
2009-06-26  7:50             ` Magnus Damm
2009-06-26  5:37       ` Magnus Damm
2009-06-26  5:37         ` Magnus Damm
2009-06-25 18:06     ` Jaya Kumar
2009-06-25 18:06       ` Jaya Kumar
2009-06-25 20:57       ` Arnd Bergmann

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=20090625111233.f6f26050.akpm@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=adaplas@gmail.com \
    --cc=arnd@arndb.de \
    --cc=jayakumar.lkml@gmail.com \
    --cc=lethal@linux-sh.org \
    --cc=linux-fbdev-devel@lists.sourceforge.net \
    --cc=linux-mm@kvack.org \
    --cc=magnus.damm@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.