From: Wei Yang <richard.weiyang@gmail.com>
To: David Hildenbrand <david@redhat.com>
Cc: Wei Yang <richard.weiyang@gmail.com>,
akpm@linux-foundation.org, lorenzo.stoakes@oracle.com,
ziy@nvidia.com, baolin.wang@linux.alibaba.com,
Liam.Howlett@oracle.com, npache@redhat.com, ryan.roberts@arm.com,
dev.jain@arm.com, baohua@kernel.org, lance.yang@linux.dev,
xu.xin16@zte.com.cn, chengming.zhou@linux.dev,
linux-mm@kvack.org, kirill@shutemov.name, raghavendra.kt@amd.com
Subject: Re: [Patch mm-stable-fixup 0/2] mm_slot: fix the usage of mm_slot_entry()
Date: Wed, 1 Oct 2025 08:39:19 +0000 [thread overview]
Message-ID: <20251001083919.nuxs7jtv2rgyz4ud@master> (raw)
In-Reply-To: <f1218a6d-b1ec-460f-afbe-3f88f3cc44ea@redhat.com>
On Wed, Oct 01, 2025 at 10:34:52AM +0200, David Hildenbrand wrote:
>On 01.10.25 03:06, Wei Yang wrote:
>> This is the fixup based on mm-stable.
>>
>> The base commit:
>>
>> mm: swap: check for stable address space before operating on the VMA
>>
>> The reviewed version is at [1].
>
>I'm confused: why "fixup"?
>
>Usually fixups are applied on top of other patches (to be squashed in).
>
Andrew mention he has merged v2 into mm-stable and ask for a fixup.
Not sure I misunderstand the process.
>--
>Cheers
>
>David / dhildenb
--
Wei Yang
Help you, Help me
next prev parent reply other threads:[~2025-10-01 8:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-01 1:06 Wei Yang
2025-10-01 1:06 ` [Patch mm-stable-fixup 1/2] mm/ksm: don't call mm_slot_entry() when the slot is NULL Wei Yang
2025-10-01 1:06 ` [Patch mm-stable-fixup 2/2] mm/khugepaged: remove definition of struct khugepaged_mm_slot Wei Yang
2025-10-01 8:34 ` [Patch mm-stable-fixup 0/2] mm_slot: fix the usage of mm_slot_entry() David Hildenbrand
2025-10-01 8:39 ` Wei Yang [this message]
2025-10-01 8:45 ` David Hildenbrand
2025-10-01 8:48 ` Wei Yang
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=20251001083919.nuxs7jtv2rgyz4ud@master \
--to=richard.weiyang@gmail.com \
--cc=Liam.Howlett@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=baohua@kernel.org \
--cc=baolin.wang@linux.alibaba.com \
--cc=chengming.zhou@linux.dev \
--cc=david@redhat.com \
--cc=dev.jain@arm.com \
--cc=kirill@shutemov.name \
--cc=lance.yang@linux.dev \
--cc=linux-mm@kvack.org \
--cc=lorenzo.stoakes@oracle.com \
--cc=npache@redhat.com \
--cc=raghavendra.kt@amd.com \
--cc=ryan.roberts@arm.com \
--cc=xu.xin16@zte.com.cn \
--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