From: Andrew Morton <akpm@linux-foundation.org>
To: Nick Piggin <npiggin@suse.de>
Cc: linuxppc-dev@ozlabs.org, paulus@samba.org, jk@ozlabs.org
Subject: Re: [patch 4/4] spufs: convert nopfn to fault
Date: Wed, 14 May 2008 18:30:32 -0700 [thread overview]
Message-ID: <20080514183032.23f9e511.akpm@linux-foundation.org> (raw)
In-Reply-To: <20080515005305.GD30448@wotan.suse.de>
On Thu, 15 May 2008 02:53:05 +0200 Nick Piggin <npiggin@suse.de> wrote:
> Thanks for helping out with merging these Andrew. The problem with
> this is that these nopfn conversions won't work unless the
> BUG_ON is removed from mm/memory.c (patch 1/ that I sent you).
oh.
> So
> there is a little dependency chain here. I guess you could send
> that patch 1 upstream ASAP, and then let the subsequent non trivial
> patches filter up in their own time. I don't know, just a heads up.
OK, I'll include mm-allow-pfnmap-faults.patch in the next linuswards
batch.
prev parent reply other threads:[~2008-05-15 1:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-14 23:12 [patch 4/4] spufs: convert nopfn to fault akpm
2008-05-15 0:53 ` Nick Piggin
2008-05-15 1:30 ` Andrew Morton [this message]
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=20080514183032.23f9e511.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=jk@ozlabs.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=npiggin@suse.de \
--cc=paulus@samba.org \
/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;
as well as URLs for NNTP newsgroup(s).