From: Yunsheng Lin <linyunsheng@huawei.com>
To: <davem@davemloft.net>, <kuba@kernel.org>, <pabeni@redhat.com>
Cc: <netdev@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
Yunsheng Lin <linyunsheng@huawei.com>,
Alexander Duyck <alexander.duyck@gmail.com>,
Andrew Morton <akpm@linux-foundation.org>,
Linux-MM <linux-mm@kvack.org>
Subject: [PATCH net-next v1 10/10] mm: page_frag: add an entry in MAINTAINERS for page_frag
Date: Thu, 14 Nov 2024 20:16:05 +0800 [thread overview]
Message-ID: <20241114121606.3434517-11-linyunsheng@huawei.com> (raw)
In-Reply-To: <20241114121606.3434517-1-linyunsheng@huawei.com>
After this patchset, page_frag is a small subsystem/library
on its own, so add an entry in MAINTAINERS to indicate the
new subsystem/library's maintainer, maillist, status and file
lists of page_frag.
Alexander is the original author of page_frag, add him in the
MAINTAINERS too.
CC: Alexander Duyck <alexander.duyck@gmail.com>
CC: Andrew Morton <akpm@linux-foundation.org>
CC: Linux-MM <linux-mm@kvack.org>
Signed-off-by: Yunsheng Lin <linyunsheng@huawei.com>
---
MAINTAINERS | 12 ++++++++++++
1 file changed, 12 insertions(+)
diff --git a/MAINTAINERS b/MAINTAINERS
index 675bd38630b7..6b6b120a4f90 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -17473,6 +17473,18 @@ F: mm/page-writeback.c
F: mm/readahead.c
F: mm/truncate.c
+PAGE FRAG
+M: Alexander Duyck <alexander.duyck@gmail.com>
+M: Yunsheng Lin <linyunsheng@huawei.com>
+L: linux-mm@kvack.org
+L: netdev@vger.kernel.org
+S: Supported
+F: Documentation/mm/page_frags.rst
+F: include/linux/page_frag_cache.h
+F: mm/page_frag_cache.c
+F: tools/testing/selftests/mm/page_frag/
+F: tools/testing/selftests/mm/test_page_frag.sh
+
PAGE POOL
M: Jesper Dangaard Brouer <hawk@kernel.org>
M: Ilias Apalodimas <ilias.apalodimas@linaro.org>
--
2.33.0
next prev parent reply other threads:[~2024-11-14 12:23 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-14 12:15 [PATCH net-next v1 00/10] Replace page_frag with page_frag_cache (Part-2) Yunsheng Lin
2024-11-14 12:15 ` [PATCH net-next v1 01/10] mm: page_frag: some minor refactoring before adding new API Yunsheng Lin
2024-11-14 12:15 ` [PATCH net-next v1 02/10] net: rename skb_copy_to_page_nocache() helper Yunsheng Lin
2024-11-14 12:15 ` [PATCH net-next v1 03/10] mm: page_frag: update documentation for page_frag Yunsheng Lin
2024-11-14 12:15 ` [PATCH net-next v1 04/10] mm: page_frag: introduce page_frag_alloc_abort() related API Yunsheng Lin
2024-11-14 12:16 ` [PATCH net-next v1 05/10] mm: page_frag: introduce refill prepare & commit API Yunsheng Lin
2024-11-14 12:16 ` [PATCH net-next v1 06/10] mm: page_frag: introduce alloc_refill " Yunsheng Lin
2024-11-14 12:16 ` [PATCH net-next v1 07/10] mm: page_frag: introduce probe related API Yunsheng Lin
2024-11-14 12:16 ` [PATCH net-next v1 08/10] mm: page_frag: add testing for the newly added API Yunsheng Lin
2024-11-14 12:16 ` [PATCH net-next v1 09/10] net: replace page_frag with page_frag_cache Yunsheng Lin
2024-11-14 12:16 ` Yunsheng Lin [this message]
2024-12-04 11:23 ` [PATCH net-next v1 00/10] Replace page_frag with page_frag_cache (Part-2) 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=20241114121606.3434517-11-linyunsheng@huawei.com \
--to=linyunsheng@huawei.com \
--cc=akpm@linux-foundation.org \
--cc=alexander.duyck@gmail.com \
--cc=davem@davemloft.net \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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