Netdev Archive mirror
 help / color / mirror / Atom feed
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>
Subject: [RFC v4 13/13] mm: page_frag: add a entry in MAINTAINERS for page_frag
Date: Wed, 15 May 2024 21:09:32 +0800	[thread overview]
Message-ID: <20240515130932.18842-14-linyunsheng@huawei.com> (raw)
In-Reply-To: <20240515130932.18842-1-linyunsheng@huawei.com>

After this patchset, page_frag is a small subsystem/library
on its own, so add a entry in MAINTAINERS for to indicate
the new subsystem/library's maintainer, maillist, status and
file lists of page_frag.

Alexander is the orginal author of page_frag, add him in the
MAINTAINERS too.

CC: Alexander Duyck <alexander.duyck@gmail.com>
Signed-off-by: Yunsheng Lin <linyunsheng@huawei.com>
---
 MAINTAINERS | 11 +++++++++++
 1 file changed, 11 insertions(+)

diff --git a/MAINTAINERS b/MAINTAINERS
index c4c6ffbc6d10..998c5e868dd8 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -16709,6 +16709,17 @@ 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:	mm/page_frag_test.c
+
 PAGE POOL
 M:	Jesper Dangaard Brouer <hawk@kernel.org>
 M:	Ilias Apalodimas <ilias.apalodimas@linaro.org>
-- 
2.33.0


      parent reply	other threads:[~2024-05-15 13:13 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-15 13:09 [RFC v4 00/13] First try to replace page_frag with page_frag_cache Yunsheng Lin
2024-05-15 13:09 ` [RFC v4 01/13] mm: page_frag: add a test module for page_frag Yunsheng Lin
2024-05-15 13:09 ` [RFC v4 02/13] xtensa: remove the get_order() implementation Yunsheng Lin
2024-05-15 13:09 ` [RFC v4 03/13] mm: page_frag: use free_unref_page() to free page fragment Yunsheng Lin
2024-05-15 13:09 ` [RFC v4 04/13] mm: move the page fragment allocator from page_alloc into its own file Yunsheng Lin
2024-05-15 13:09 ` [RFC v4 05/13] mm: page_frag: use initial zero offset for page_frag_alloc_align() Yunsheng Lin
2024-05-15 13:09 ` [RFC v4 06/13] mm: page_frag: add '_va' suffix to page_frag API Yunsheng Lin
2024-05-15 13:09 ` [RFC v4 07/13] mm: page_frag: avoid caller accessing 'page_frag_cache' directly Yunsheng Lin
2024-05-15 13:09 ` [RFC v4 08/13] mm: page_frag: reuse existing space for 'size' and 'pfmemalloc' Yunsheng Lin
2024-05-15 13:09 ` [RFC v4 09/13] net: introduce the skb_copy_to_va_nocache() helper Yunsheng Lin
2024-05-15 13:09 ` [RFC v4 10/13] mm: page_frag: introduce prepare/probe/commit API Yunsheng Lin
2024-05-15 13:09 ` [RFC v4 11/13] net: replace page_frag with page_frag_cache Yunsheng Lin
2024-05-21 18:31   ` Mat Martineau
2024-05-15 13:09 ` [RFC v4 12/13] mm: page_frag: update documentation for page_frag Yunsheng Lin
2024-05-15 13:09 ` Yunsheng Lin [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=20240515130932.18842-14-linyunsheng@huawei.com \
    --to=linyunsheng@huawei.com \
    --cc=alexander.duyck@gmail.com \
    --cc=davem@davemloft.net \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).