From: Andrew Morton <akpm@linux-foundation.org>
To: Yunsheng Lin <linyunsheng@huawei.com>
Cc: <davem@davemloft.net>, <kuba@kernel.org>, <pabeni@redhat.com>,
<netdev@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
David Howells <dhowells@redhat.com>,
Alexander Duyck <alexander.duyck@gmail.com>,
Eric Dumazet <edumazet@google.com>, Shuah Khan <shuah@kernel.org>,
<linux-mm@kvack.org>, <linux-kselftest@vger.kernel.org>
Subject: Re: [PATCH net-next v13 02/14] mm: move the page fragment allocator from page_alloc into its own file
Date: Wed, 14 Aug 2024 13:22:39 -0700 [thread overview]
Message-ID: <20240814132239.1c536ef60431216f21932696@linux-foundation.org> (raw)
In-Reply-To: <20240808123714.462740-3-linyunsheng@huawei.com>
On Thu, 8 Aug 2024 20:37:02 +0800 Yunsheng Lin <linyunsheng@huawei.com> wrote:
> Inspired by [1], move the page fragment allocator from page_alloc
> into its own c file and header file, as we are about to make more
> change for it to replace another page_frag implementation in
> sock.c
Acked-by: Andrew Morton <akpm@linux-foundation.org>
This presently has no conflicts with mm.git.
next prev parent reply other threads:[~2024-08-14 20:22 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240808123714.462740-1-linyunsheng@huawei.com>
[not found] ` <20240808123714.462740-2-linyunsheng@huawei.com>
2024-08-09 11:08 ` [PATCH net-next v13 01/14] mm: page_frag: add a test module for page_frag Muhammad Usama Anjum
2024-08-09 12:29 ` Yunsheng Lin
[not found] ` <20240808123714.462740-3-linyunsheng@huawei.com>
2024-08-14 15:33 ` [PATCH net-next v13 02/14] mm: move the page fragment allocator from page_alloc into its own file Alexander H Duyck
2024-08-14 20:22 ` Andrew Morton [this message]
[not found] ` <20240808123714.462740-5-linyunsheng@huawei.com>
2024-08-14 15:49 ` [PATCH net-next v13 04/14] mm: page_frag: add '_va' suffix to page_frag API Alexander H Duyck
2024-08-15 2:59 ` Yunsheng Lin
2024-08-15 15:00 ` Alexander Duyck
2024-08-16 11:55 ` Yunsheng Lin
2024-08-19 15:54 ` Alexander Duyck
2024-08-20 13:07 ` Yunsheng Lin
2024-08-20 16:02 ` Alexander Duyck
2024-08-21 12:30 ` Yunsheng Lin
[not found] ` <20240808123714.462740-8-linyunsheng@huawei.com>
2024-08-14 16:13 ` [PATCH net-next v13 07/14] mm: page_frag: reuse existing space for 'size' and 'pfmemalloc' Alexander H Duyck
2024-08-15 3:10 ` Yunsheng Lin
2024-08-15 15:03 ` Alexander Duyck
2024-08-16 11:55 ` Yunsheng Lin
2024-08-19 16:00 ` Alexander Duyck
[not found] ` <20240808123714.462740-9-linyunsheng@huawei.com>
2024-08-14 17:54 ` [PATCH net-next v13 08/14] mm: page_frag: some minor refactoring before adding new API Alexander H Duyck
2024-08-15 3:04 ` Yunsheng Lin
2024-08-15 15:09 ` Alexander Duyck
2024-08-16 11:58 ` Yunsheng Lin
[not found] ` <20240808123714.462740-12-linyunsheng@huawei.com>
2024-08-14 21:00 ` [PATCH net-next v13 11/14] mm: page_frag: introduce prepare/probe/commit API Alexander H Duyck
2024-08-15 3:05 ` Yunsheng Lin
2024-08-15 15:25 ` Alexander Duyck
2024-08-16 12:01 ` Yunsheng Lin
2024-08-19 15:52 ` Alexander Duyck
2024-08-20 13:08 ` Yunsheng Lin
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=20240814132239.1c536ef60431216f21932696@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=alexander.duyck@gmail.com \
--cc=davem@davemloft.net \
--cc=dhowells@redhat.com \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linyunsheng@huawei.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=shuah@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox