From: Lorenzo Stoakes <ljs@kernel.org>
To: Usama Arif <usama.arif@linux.dev>
Cc: Andrew Morton <akpm@linux-foundation.org>,
apopple@nvidia.com, baohua@kernel.org,
baolin.wang@linux.alibaba.com, byungchul@sk.com,
david@kernel.org, dev.jain@arm.com, gourry@gourry.net,
jannh@google.com, joshua.hahnjy@gmail.com, lance.yang@linux.dev,
liam@infradead.org, linux-kernel@vger.kernel.org,
linux-mm@kvack.org, matthew.brost@intel.com, npache@redhat.com,
rakie.kim@sk.com, ryan.roberts@arm.com, vbabka@kernel.org,
ying.huang@linux.alibaba.com, ziy@nvidia.com,
shakeel.butt@linux.dev, hannes@cmpxchg.org,
Balbir Singh <balbirs@nvidia.com>
Subject: Re: [PATCH 0/3] mm: handle device-private PMDs in walk callbacks
Date: Wed, 8 Jul 2026 09:23:36 +0100 [thread overview]
Message-ID: <ak4It9Hm8S01Nun9@lucifer> (raw)
In-Reply-To: <fde1372f-5d80-4a1b-8bbb-11441db9f55d@linux.dev>
On Tue, Jul 07, 2026 at 03:12:11PM +0100, Usama Arif wrote:
> I think maybe we should modify get_maintainers.pl so that if there is
> a "Fixes" in commit message, than the author of that commit is also
> in the output from that script?
>
I thought it did that already, but it's forbidden perl magic that I dare not
look at so who knows :P
Wasn't nagging per se about that (for once :P), often people who'd be good to cc-
get missed anyway even doing all the right things, so just wanted to make sure
Balbir was aware, also so we can make sure there's no other device private PMD
stuff lurking! :)
Cheers, Lorenzo
next prev parent reply other threads:[~2026-07-08 8:23 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-07 13:45 [PATCH 0/3] mm: handle device-private PMDs in walk callbacks Usama Arif
2026-07-07 13:45 ` [PATCH 1/3] mm/mempolicy: skip device-private PMDs when queueing folios Usama Arif
2026-07-07 20:33 ` Zi Yan
2026-07-08 10:54 ` Usama Arif
2026-07-08 15:25 ` Zi Yan
2026-07-07 23:49 ` Balbir Singh
2026-07-07 13:45 ` [PATCH 2/3] mm/madvise: skip device-private PMDs in cold and pageout walks Usama Arif
2026-07-07 20:41 ` Zi Yan
2026-07-07 23:27 ` Balbir Singh
2026-07-07 13:45 ` [PATCH 3/3] mm/huge_memory: skip device-private PMDs in madvise_free_huge_pmd Usama Arif
2026-07-07 20:44 ` Zi Yan
2026-07-07 23:26 ` Balbir Singh
2026-07-07 14:01 ` [PATCH 0/3] mm: handle device-private PMDs in walk callbacks Lorenzo Stoakes
2026-07-07 14:12 ` Usama Arif
2026-07-08 8:23 ` Lorenzo Stoakes [this message]
2026-07-08 8:40 ` Balbir Singh
2026-07-07 15:30 ` Zi Yan
2026-07-07 22:57 ` Balbir Singh
2026-07-08 8:38 ` Lorenzo Stoakes
2026-07-07 19:19 ` Joshua Hahn
2026-07-08 12:22 ` Usama Arif
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=ak4It9Hm8S01Nun9@lucifer \
--to=ljs@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=apopple@nvidia.com \
--cc=balbirs@nvidia.com \
--cc=baohua@kernel.org \
--cc=baolin.wang@linux.alibaba.com \
--cc=byungchul@sk.com \
--cc=david@kernel.org \
--cc=dev.jain@arm.com \
--cc=gourry@gourry.net \
--cc=hannes@cmpxchg.org \
--cc=jannh@google.com \
--cc=joshua.hahnjy@gmail.com \
--cc=lance.yang@linux.dev \
--cc=liam@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=matthew.brost@intel.com \
--cc=npache@redhat.com \
--cc=rakie.kim@sk.com \
--cc=ryan.roberts@arm.com \
--cc=shakeel.butt@linux.dev \
--cc=usama.arif@linux.dev \
--cc=vbabka@kernel.org \
--cc=ying.huang@linux.alibaba.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox