All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Howells <dhowells@redhat.com>
To: unlisted-recipients:; (no To-header on input)
Cc: dhowells@redhat.com, Mike Frysinger <vapier@gentoo.org>,
	uclinux-dev@uclinux.org, David McCullough <davidm@snapgear.com>,
	Greg Ungerer <gerg@uclinux.org>, Paul Mundt <lethal@linux-sh.org>,
	linux-kernel@vger.kernel.org,
	uclinux-dist-devel@blackfin.uclinux.org
Subject: Re: [PATCH v2] NOMMU: implement vmap/vunmap with kmalloc
Date: Thu, 01 Apr 2010 00:07:54 +0100	[thread overview]
Message-ID: <19923.1270076874@redhat.com> (raw)
In-Reply-To: <19891.1270076813@redhat.com>

David Howells <dhowells@redhat.com> wrote:

> > how about putting this implementation into like vmap_nommu() and only 
> > rewriting vmap() to vmap_nommu() when we know it's safe ?  such as this 
> > firmware case ?
> 
> Well, I'd argue it's _not_ vmap(), so it doesn't really make sense to call it
> such.  Perhaps some better name?  Perhaps vcopy()?

How about vcoalesce()?

David

  reply	other threads:[~2010-03-31 23:08 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-06  4:25 userspace firmware loader, vmap, and nommu Mike Frysinger
2009-10-06  4:38 ` David Woodhouse
2009-10-06  4:56   ` Mike Frysinger
2009-12-21 16:44 ` [PATCH] nommu: implement vmap/vunmap with kmalloc Mike Frysinger
2010-01-07  6:49   ` [uClinux-dev] " Mike Frysinger
2010-01-16 15:57   ` David Howells
2010-03-09 16:11   ` [PATCH v2] NOMMU: " Mike Frysinger
2010-03-31 17:11     ` David Howells
2010-03-31 19:54       ` Mike Frysinger
2010-03-31 23:06         ` David Howells
2010-03-31 23:07           ` David Howells [this message]
2010-03-31 23:10             ` Mike Frysinger

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=19923.1270076874@redhat.com \
    --to=dhowells@redhat.com \
    --cc=davidm@snapgear.com \
    --cc=gerg@uclinux.org \
    --cc=lethal@linux-sh.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=uclinux-dev@uclinux.org \
    --cc=uclinux-dist-devel@blackfin.uclinux.org \
    --cc=vapier@gentoo.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 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.