[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <20160425194051.48148f1a69bdc14ecdcce2fb@linux-foundation.org>
Date: Mon, 25 Apr 2016 19:40:51 -0700
From: Andrew Morton <akpm@...ux-foundation.org>
To: Rich Felker <dalias@...c.org>
Cc: linux-kernel@...r.kernel.org, Michal Hocko <mhocko@...e.com>,
Greg Ungerer <gerg@...inux.org>,
Geert Uytterhoeven <geert@...ux-m68k.org>,
Yoshinori Sato <ysato@...rs.sourceforge.jp>
Subject: Re: [PATCH] tmpfs: fix VM_MAYSHARE mappings for NOMMU
On Mon, 25 Apr 2016 20:47:45 -0400 Rich Felker <dalias@...c.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@...c.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
Powered by blists - more mailing lists