mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: Rich Felker <dalias@libc.org>
Cc: linux-kernel@vger.kernel.org, Michal Hocko <mhocko@suse.com>,
	Greg Ungerer <gerg@uclinux.org>,
	Geert Uytterhoeven <geert@linux-m68k.org>,
	Yoshinori Sato <ysato@users.sourceforge.jp>
Subject: Re: [PATCH] tmpfs: fix VM_MAYSHARE mappings for NOMMU
Date: Mon, 25 Apr 2016 19:40:51 -0700	[thread overview]
Message-ID: <20160425194051.48148f1a69bdc14ecdcce2fb@linux-foundation.org> (raw)
In-Reply-To: <20160426004744.GI21636@brightrain.aerifal.cx>

On Mon, 25 Apr 2016 20:47:45 -0400 Rich Felker <dalias@libc.org> wrote:

> On Mon, Apr 25, 2016 at 08:41:24PM -0400, Rich Felker wrote:
> > On Mon, Apr 25, 2016 at 05:09:09PM -0700, Andrew Morton wrote:
> > > On Fri, 22 Apr 2016 18:19:44 -0400 Rich Felker <dalias@libc.org> wrote:
> > > 
> > > > Subject: [PATCH] tmpfs: fix VM_MAYSHARE mappings for NOMMU
> > > 
> > > I take it that "ramfs" was intended here.
> > 
> > They're two names for the same thing; I'm not sure which should be
> > preferred.
> 
> Or maybe not... the relationship seems more complex, at least
> hisorically, but the ramfs code here is what seems to provide the
> backing for tmpfs (and maybe more?). Sorry for the quick and imprecise
> reply.

I am a simple soul.

Subject: tmpfs/ramfs: fix VM_MAYSHARE mappings for NOMMU

      reply	other threads:[~2016-04-26  2:40 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-22 22:19 Rich Felker
2016-04-26  0:09 ` Andrew Morton
2016-04-26  0:41   ` Rich Felker
2016-04-26  0:47     ` Rich Felker
2016-04-26  2:40       ` 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=20160425194051.48148f1a69bdc14ecdcce2fb@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=dalias@libc.org \
    --cc=geert@linux-m68k.org \
    --cc=gerg@uclinux.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mhocko@suse.com \
    --cc=ysato@users.sourceforge.jp \
    /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®