From: "David Hildenbrand (Arm)" <david@kernel.org>
To: Ackerley Tng <ackerleytng@google.com>,
Andrew Morton <akpm@linux-foundation.org>,
mm-commits@vger.kernel.org, willy@infradead.org,
vbabka@kernel.org, seanjc@google.com, hughd@google.com,
fuad.tabba@linux.dev, binbin.wu@linux.intel.com
Subject: Re: [merged mm-hotfixes-stable] mm-folio-export_symbol_for_kvmlru_cache_drain_for_folio.patch removed from -mm tree
Date: Wed, 9 Sep 2026 17:28:14 +0200 [thread overview]
Message-ID: <8ff3e681-b377-4b32-95f5-31a5cc1dc2f5@kernel.org> (raw)
In-Reply-To: <CAEvNRgFToiH0H0CfYTUoct3JgWksHOJY7ramUX_PK2k_NQajZA@mail.gmail.com>
On 9/9/26 17:08, Ackerley Tng wrote:
> Andrew Morton <akpm@linux-foundation.org> writes:
>
>>
>> [...snip...]
>>
>> This patch was dropped because it was merged into the mm-hotfixes-stable branch
>> of git://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm
>>
>>
>> [...snip...]
>>
>> --- a/mm/folio.c~mm-folio-export_symbol_for_kvmlru_cache_drain_for_folio
>> +++ a/mm/folio.c
>> @@ -33,6 +33,7 @@
>> #include <linux/page_idle.h>
>> #include <linux/local_lock.h>
>> #include <linux/buffer_head.h>
>> +#include <linux/kvm_types.h>
>>
>> #include "internal.h"
>> #include "page_alloc.h"
>> @@ -926,6 +927,7 @@ void lru_cache_drain_for_folio(const str
>> *drained = LRU_CACHE_DRAINED_ALL;
>> }
>> }
>> +EXPORT_SYMBOL_FOR_KVM(lru_cache_drain_for_folio);
>>
>>
>> [...snip...]
>>
>
> Thanks all!
>
> Would like to check on branch management for mm-hotfixes-stable: Does
> this patch being on mm-hotfixes-stable now (7.3-rc2) mean that this will
> make it to 7.3-rc3?
Unless it gets yanked last minute, which is unlikely given that it is in -stable :)
--
Cheers,
David
prev parent reply other threads:[~2026-09-09 15:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-09 6:28 [merged mm-hotfixes-stable] mm-folio-export_symbol_for_kvmlru_cache_drain_for_folio.patch removed from -mm tree Andrew Morton
2026-09-09 15:08 ` Ackerley Tng
2026-09-09 15:28 ` David Hildenbrand (Arm) [this message]
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=8ff3e681-b377-4b32-95f5-31a5cc1dc2f5@kernel.org \
--to=david@kernel.org \
--cc=ackerleytng@google.com \
--cc=akpm@linux-foundation.org \
--cc=binbin.wu@linux.intel.com \
--cc=fuad.tabba@linux.dev \
--cc=hughd@google.com \
--cc=mm-commits@vger.kernel.org \
--cc=seanjc@google.com \
--cc=vbabka@kernel.org \
--cc=willy@infradead.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.