mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Nick Piggin <npiggin@suse.de>
To: Jes Sorensen <jes@sgi.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Cliff Wickman <cpw@sgi.com>,
	airlied@linux.ie, benh@kernel.crashing.org,
	michael@ellerman.id.au, jk@ozlabs.org,
	Cedric Le Goater <clg@fr.ibm.com>
Subject: Re: [rfc][patch] reimplement nopfn callers with fault
Date: Sat, 12 Jan 2008 10:34:36 +0100	[thread overview]
Message-ID: <20080112093436.GB25048@wotan.suse.de> (raw)
In-Reply-To: <47877FCA.8050707@sgi.com>

On Fri, Jan 11, 2008 at 03:40:10PM +0100, Jes Sorensen wrote:
> Nick Piggin wrote:
> >Hi guys,
> >
> >I'd like to finally remove nopfn from the tree. So I would really like to 
> >get
> >this patch into -mm soon (or broken out patches into appropriate trees).
> >
> >Anyway, I don't have a good way to compile mspec or cell changes very 
> >easily.
> >Hopefully if there are any silly typos, they will be easier to fix. More 
> >problematic
> >is actually testing the things; I'm not even sure I'm covering all bases 
> >with
> >drm testing.
> >
> >So, if I could trouble you for a quick review and/or test at some time.... 
> >the
> >patch is against latest -mm.
> 
> Nick,
> 
> Is this supposed to apply to the latest Linus tree? I applied it here
> and the mspec driver lights up in beautiful fireworks :-( I'll give the
> -mm tree a try next.

Hi Jes,

(reply to all this time).

It is the BUG_ON(vma->vm_flags & VM_PFNMAP); at the start of __do_fault, by
the looks. That should be simply removed. Sorry about that.

Thanks,
Nick

  reply	other threads:[~2008-01-12  9:34 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-08 11:32 Nick Piggin
2008-01-11 14:40 ` Jes Sorensen
2008-01-12  9:34   ` Nick Piggin [this message]
2008-01-14  9:14     ` Jes Sorensen
2008-01-16  9:03       ` Nick Piggin

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=20080112093436.GB25048@wotan.suse.de \
    --to=npiggin@suse.de \
    --cc=airlied@linux.ie \
    --cc=benh@kernel.crashing.org \
    --cc=clg@fr.ibm.com \
    --cc=cpw@sgi.com \
    --cc=jes@sgi.com \
    --cc=jk@ozlabs.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=michael@ellerman.id.au \
    /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
all inboxes | Powered by JetHome®