From: Lorenzo Stoakes <lorenzo.stoakes@oracle.com>
To: Yu Zhao <yuzhao@google.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Jeff Xu <jeffxu@chromium.org>,
"Liam R . Howlett" <Liam.Howlett@oracle.com>,
Vlastimil Babka <vbabka@suse.cz>, Jann Horn <jannh@google.com>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org,
David Hildenbrand <david@redhat.com>
Subject: Re: [PATCH] MAINTAINERS: update MEMORY MAPPING section
Date: Fri, 13 Dec 2024 09:23:54 +0000 [thread overview]
Message-ID: <4da9eeb4-c097-4b36-8c76-207a3d2f2c40@lucifer.local> (raw)
In-Reply-To: <cb5eea98-2515-4b06-8f65-515842e1081b@lucifer.local>
On Fri, Dec 13, 2024 at 09:17:57AM +0000, Lorenzo Stoakes wrote:
> However as Vlastimil points out - we can't separate out mseal.c here, not
> reasonably. And it is so clearly strictly an mmap/vma bit of logic that it
> really ought to be included here to ensure that we who maintain the overall
> vma work can ensure everything works together - it doesn't make sense to.
^ it doesn't make sense _NOT_ to :P a silly typo because I've not had coffee yet...
next prev parent reply other threads:[~2024-12-13 9:24 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-11 10:53 Lorenzo Stoakes
2024-12-11 18:36 ` Jeff Xu
2024-12-11 18:57 ` Lorenzo Stoakes
2024-12-13 5:50 ` Yu Zhao
2024-12-13 8:25 ` Vlastimil Babka
2024-12-13 9:00 ` Yu Zhao
2024-12-13 9:10 ` Vlastimil Babka
2024-12-13 9:17 ` Lorenzo Stoakes
2024-12-13 9:23 ` Lorenzo Stoakes [this message]
2024-12-13 9:36 ` Yu Zhao
2024-12-13 15:05 ` Jeff Xu
2024-12-13 15:19 ` Lorenzo Stoakes
2024-12-12 8:09 ` Vlastimil Babka
2024-12-12 14:40 ` David Hildenbrand
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=4da9eeb4-c097-4b36-8c76-207a3d2f2c40@lucifer.local \
--to=lorenzo.stoakes@oracle.com \
--cc=Liam.Howlett@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=david@redhat.com \
--cc=jannh@google.com \
--cc=jeffxu@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=vbabka@suse.cz \
--cc=yuzhao@google.com \
/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®