From: SJ Park <sj@kernel.org>
To: "Lorenzo Stoakes (ARM)" <ljs@kernel.org>
Cc: SJ Park <sj@kernel.org>, Arnd Bergmann <arnd@arndb.de>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Andrew Morton <akpm@linux-foundation.org>,
David Hildenbrand <david@kernel.org>,
"Liam R. Howlett" <liam@infradead.org>,
Vlastimil Babka <vbabka@kernel.org>,
Mike Rapoport <rppt@kernel.org>,
Suren Baghdasaryan <surenb@google.com>,
Michal Hocko <mhocko@suse.com>, Jann Horn <jannh@google.com>,
Pedro Falcato <pfalcato@suse.de>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] MAINTAINERS: add drivers/char/mem.c to mm misc, memory mapping sections
Date: Wed, 12 Aug 2026 17:08:43 -0700 [thread overview]
Message-ID: <20260813000843.128434-1-sj@kernel.org> (raw)
In-Reply-To: <20260812-add-drivers-mem-to-mm-maintainers-v1-1-6218b861f4c8@kernel.org>
On Wed, 12 Aug 2026 08:43:31 +0100 "Lorenzo Stoakes (ARM)" <ljs@kernel.org> wrote:
> This file is a 'special' driver that implements /dev/zero and /dev/mem
> among other things.
>
> As such it makes sense for mm to be cc'd on mails and to have some say in
> how things are changed there, so add it to the mm misc section.
>
> Uniquely, it provides the 'old way' of obtaining an anonymous mapping -
> MAP_PRIVATE of /dev/zero - so is directly tied to memory mapping, therefore
> also add it to the memory mapping section.
Makes sense.
>
> scripts/get_maintainer.pl copes perfectly fine with files in multiple
> sections so everything should work correctly.
>
> Signed-off-by: Lorenzo Stoakes (ARM) <ljs@kernel.org>
Acked-by: SJ Park <sj@kernel.org>
Thanks,
SJ
[...]
next prev parent reply other threads:[~2026-08-13 0:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-12 7:43 [PATCH] MAINTAINERS: add drivers/char/mem.c to mm misc, memory mapping sections Lorenzo Stoakes (ARM)
2026-08-12 11:34 ` David Hildenbrand (Arm)
2026-08-12 13:29 ` Mike Rapoport
2026-08-13 0:08 ` SJ Park [this message]
2026-08-13 3:15 ` Anshuman Khandual
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=20260813000843.128434-1-sj@kernel.org \
--to=sj@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=arnd@arndb.de \
--cc=david@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=jannh@google.com \
--cc=liam@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=ljs@kernel.org \
--cc=mhocko@suse.com \
--cc=pfalcato@suse.de \
--cc=rppt@kernel.org \
--cc=surenb@google.com \
--cc=vbabka@kernel.org \
/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.