[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.DEB.2.10.1504091244501.11370@chino.kir.corp.google.com>
Date: Thu, 9 Apr 2015 12:46:09 -0700 (PDT)
From: David Rientjes <rientjes@...gle.com>
To: Jonathan Corbet <corbet@....net>
cc: Andrew Morton <akpm@...ux-foundation.org>,
Hugh Dickins <hughd@...gle.com>,
Davide Libenzi <davidel@...ilserver.org>,
Luiz Capitulino <lcapitulino@...hat.com>,
Shuah Khan <shuahkh@....samsung.com>,
Andrea Arcangeli <aarcange@...hat.com>,
Joern Engel <joern@...fs.org>,
Jianguo Wu <wujianguo@...wei.com>,
Eric B Munson <emunson@...mai.com>, linux-mm@...ck.org,
linux-kernel@...r.kernel.org, linux-api@...r.kernel.org,
linux-doc@...r.kernel.org
Subject: Re: [patch -mm] mm, doc: cleanup and clarify munmap behavior for
hugetlb memory fix
On Sat, 4 Apr 2015, Jonathan Corbet wrote:
> On Thu, 2 Apr 2015 15:50:15 -0700 (PDT)
> David Rientjes <rientjes@...gle.com> wrote:
>
> > Don't only specify munmap(2) behavior with respect the hugetlb memory, all
> > other syscalls get naturally aligned to the native page size of the
> > processor. Rather, pick out munmap(2) as a specific example.
>
> So I was going to apply this to the docs tree, but it doesn't even come
> close. What tree was this patch generated against?
>
Sorry, it's not intended to go through the docs tree, it's a patch to fix
mm-doc-cleanup-and-clarify-munmap-behavior-for-hugetlb-memory.patch in
-mm. It's been merged into that tree, but I would still appreciate your
ack!
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists