From: "Lorenzo Stoakes (ARM)" <ljs@kernel.org>
To: Hugh Dickins <hughd@google.com>
Cc: "David Hildenbrand (Arm)" <david@kernel.org>,
Alistair Popple <apopple@nvidia.com>,
Andrew Morton <akpm@linux-foundation.org>,
"Aneesh Kumar K.V" <aneesh.kumar@kernel.org>,
Baolin Wang <baolin.wang@linux.alibaba.com>,
Baoquan He <baoquan.he@linux.dev>,
Barry Song <baohua@kernel.org>,
Brendan Jackman <brendan.jackman@linux.dev>,
Byungchul Park <byungchul@sk.com>,
Chengming Zhou <chengming.zhou@linux.dev>,
Chris Li <chrisl@kernel.org>, Christoph Lameter <cl@gentwo.org>,
Dave Chinner <david@fromorbit.com>,
David Rientjes <rientjes@google.com>,
Dennis Zhou <dennis@kernel.org>, Dev Jain <dev.jain@arm.com>,
Gregory Price <gourry@gourry.net>, Hao Li <hao.li@linux.dev>,
Harry Yoo <harry@kernel.org>, Jann Horn <jannh@google.com>,
Johannes Weiner <hannes@cmpxchg.org>,
John Hubbard <jhubbard@nvidia.com>,
Joshua Hahn <joshua.hahnjy@gmail.com>,
Kairui Song <kasong@tencent.com>,
Kemeng Shi <shikemeng@huaweicloud.com>,
Kiryl Shutsemau <kas@kernel.org>,
Lance Yang <lance.yang@linux.dev>,
"Liam R. Howlett" <liam@infradead.org>,
Matthew Brost <matthew.brost@intel.com>,
Miaohe Lin <linmiaohe@huawei.com>,
Michal Hocko <mhocko@kernel.org>,
Mike Rapoport <rppt@kernel.org>,
Muchun Song <muchun.song@linux.dev>,
Naoya Horiguchi <nao.horiguchi@gmail.com>,
Nhat Pham <nphamcs@gmail.com>, Nick Piggin <npiggin@gmail.com>,
Nico Pache <nico.pache@linux.dev>,
Oscar Salvador <osalvador@suse.de>,
Pedro Falcato <pfalcato@suse.de>, Peter Xu <peterx@redhat.com>,
Peter Zijlstra <peterz@infradead.org>,
Qi Zheng <qi.zheng@linux.dev>, Rakie Kim <rakie.kim@sk.com>,
Rik van Riel <riel@surriel.com>,
Roman Gushchin <roman.gushchin@linux.dev>,
Ryan Roberts <ryan.roberts@arm.com>,
Shakeel Butt <shakeel.butt@linux.dev>,
Suren Baghdasaryan <surenb@google.com>,
Tejun Heo <tj@kernel.org>, Uladzislau Rezki <urezki@gmail.com>,
Usama Arif <usama.arif@linux.dev>,
Vlastimil Babka <vbabka@kernel.org>,
Will Deacon <will@kernel.org>, Xu Xin <xu.xin@linux.dev>,
Ying Huang <ying.huang@linux.alibaba.com>,
Youngjun Park <youngjun.park@lge.com>, Zi Yan <ziy@nvidia.com>,
Jason Gunthorpe <jgg@ziepe.ca>,
Manfred Spraul <manfred@colorfullife.com>,
Christian Brauner <brauner@kernel.org>,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-mm@kvack.org
Subject: Re: [PATCH 2/7] MAINTAINERS: TMPFS (SHMEM FILESYSTEM) updates
Date: Tue, 3 Nov 2026 08:45:22 +0000 [thread overview]
Message-ID: <aume40GKpYIoqEkN@gremlin> (raw)
In-Reply-To: <b04d8d01-b42d-d948-b7b8-c360f8ec6002@google.com>
On Tue, Nov 03, 2026 at 12:27:22AM -0800, Hugh Dickins wrote:
> Okay: but do keep in mind that tmpfs is a filesystem, and often the
> FS folks make small adjustments to it, which usually go unconflictingly
> through Christian Brauner's tree. That generally works well, so please
> let's keep on working in that way (just once I remember holding off
> intended MM changes to shmem.c for a release, while FS were busy there).
One thing that's useful is keeping certain files in multiple sections at
once - we do this already for some mm/fs boundary stuff and it works well.
That way you can make sure the right people are cc'd on it but not restrict
fs's ability to do what they need also.
--
Cheers, Lorenzo
next prev parent reply other threads:[~2026-11-03 8:45 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-30 21:34 [PATCH 0/7] MAINTAINERS: MM updates David Hildenbrand (Arm)
2026-10-30 21:34 ` [PATCH 1/7] MAINTAINERS: mention for-next branch in MEMORY MANAGEMENT - MEMORY MAP David Hildenbrand (Arm)
2026-10-31 0:40 ` Muchun Song
2026-10-31 8:38 ` Lorenzo Stoakes (ARM)
2026-11-01 17:11 ` Harry Yoo
2026-10-30 21:34 ` [PATCH 2/7] MAINTAINERS: TMPFS (SHMEM FILESYSTEM) updates David Hildenbrand (Arm)
2026-10-31 8:42 ` Lorenzo Stoakes (ARM)
2026-11-01 17:14 ` Harry Yoo
2026-11-02 2:01 ` Baolin Wang
2026-11-03 8:27 ` Hugh Dickins
2026-11-03 8:45 ` Lorenzo Stoakes (ARM) [this message]
2026-11-03 15:10 ` Andrew Morton
2026-11-03 16:23 ` David Hildenbrand (Arm)
2026-11-03 18:07 ` Hugh Dickins
2026-10-30 21:34 ` [PATCH 3/7] MAINTAINERS: add Zi Yan as co-maintainer for MEMORY MANAGEMENT - THP David Hildenbrand (Arm)
2026-10-30 22:00 ` Zi Yan
2026-10-30 23:33 ` Barry Song
2026-10-31 0:39 ` Muchun Song
2026-10-31 4:01 ` Lance Yang
2026-10-31 5:43 ` Dev Jain
2026-10-31 8:36 ` Lorenzo Stoakes (ARM)
2026-11-01 17:16 ` Harry Yoo
2026-11-02 2:04 ` Baolin Wang
2026-10-30 21:34 ` [PATCH 4/7] MAINTAINERS: sort entries in MM sections David Hildenbrand (Arm)
2026-10-31 9:08 ` Lorenzo Stoakes (ARM)
2026-10-31 9:25 ` David Hildenbrand (Arm)
2026-11-01 17:19 ` Harry Yoo
2026-10-30 21:34 ` [PATCH 5/7] MAINTAINERS: add missing files to MM component sections David Hildenbrand (Arm)
2026-10-31 0:42 ` Muchun Song
2026-10-31 9:23 ` Lorenzo Stoakes (ARM)
2026-10-31 9:26 ` David Hildenbrand (Arm)
2026-10-30 21:34 ` [PATCH 6/7] MAINTAINERS: rename and move MEMORY HOT(UN)PLUG David Hildenbrand (Arm)
2026-10-31 0:43 ` Muchun Song
2026-10-31 9:24 ` Lorenzo Stoakes (ARM)
2026-10-30 21:34 ` [PATCH 7/7] MAINTAINERS: route more MM changes through mm/core.git David Hildenbrand (Arm)
2026-10-31 10:51 ` Lorenzo Stoakes (ARM)
2026-10-30 22:02 ` [PATCH 0/7] MAINTAINERS: MM updates Zi Yan
2026-10-30 23:48 ` SJ Park
2026-10-31 7:49 ` Qi Zheng
2026-10-31 8:30 ` Mike Rapoport
2026-11-01 10:37 ` Vlastimil Babka (SUSE)
2026-11-01 13:33 ` David Hildenbrand (Arm)
2026-11-01 20:30 ` Andrew Morton
2026-11-01 20:55 ` SJ Park
2026-11-02 6:47 ` David Hildenbrand (Arm)
2026-11-02 7:11 ` Andrew Morton
2026-11-02 8:07 ` David Hildenbrand (Arm)
2026-11-02 11:17 ` Lorenzo Stoakes (ARM)
2026-11-02 12:32 ` David Hildenbrand (Arm)
2026-11-02 12:33 ` Lorenzo Stoakes (ARM)
2026-11-01 20:47 ` Shakeel Butt
2026-11-02 11:20 ` Kiryl Shutsemau
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=aume40GKpYIoqEkN@gremlin \
--to=ljs@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=aneesh.kumar@kernel.org \
--cc=apopple@nvidia.com \
--cc=baohua@kernel.org \
--cc=baolin.wang@linux.alibaba.com \
--cc=baoquan.he@linux.dev \
--cc=brauner@kernel.org \
--cc=brendan.jackman@linux.dev \
--cc=byungchul@sk.com \
--cc=chengming.zhou@linux.dev \
--cc=chrisl@kernel.org \
--cc=cl@gentwo.org \
--cc=david@fromorbit.com \
--cc=david@kernel.org \
--cc=dennis@kernel.org \
--cc=dev.jain@arm.com \
--cc=gourry@gourry.net \
--cc=hannes@cmpxchg.org \
--cc=hao.li@linux.dev \
--cc=harry@kernel.org \
--cc=hughd@google.com \
--cc=jannh@google.com \
--cc=jgg@ziepe.ca \
--cc=jhubbard@nvidia.com \
--cc=joshua.hahnjy@gmail.com \
--cc=kas@kernel.org \
--cc=kasong@tencent.com \
--cc=lance.yang@linux.dev \
--cc=liam@infradead.org \
--cc=linmiaohe@huawei.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=manfred@colorfullife.com \
--cc=matthew.brost@intel.com \
--cc=mhocko@kernel.org \
--cc=muchun.song@linux.dev \
--cc=nao.horiguchi@gmail.com \
--cc=nico.pache@linux.dev \
--cc=nphamcs@gmail.com \
--cc=npiggin@gmail.com \
--cc=osalvador@suse.de \
--cc=peterx@redhat.com \
--cc=peterz@infradead.org \
--cc=pfalcato@suse.de \
--cc=qi.zheng@linux.dev \
--cc=rakie.kim@sk.com \
--cc=riel@surriel.com \
--cc=rientjes@google.com \
--cc=roman.gushchin@linux.dev \
--cc=rppt@kernel.org \
--cc=ryan.roberts@arm.com \
--cc=shakeel.butt@linux.dev \
--cc=shikemeng@huaweicloud.com \
--cc=surenb@google.com \
--cc=tj@kernel.org \
--cc=urezki@gmail.com \
--cc=usama.arif@linux.dev \
--cc=vbabka@kernel.org \
--cc=will@kernel.org \
--cc=xu.xin@linux.dev \
--cc=ying.huang@linux.alibaba.com \
--cc=youngjun.park@lge.com \
--cc=ziy@nvidia.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 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.