From: Mike Rapoport <rppt@kernel.org>
To: David Hildenbrand <david@redhat.com>
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org,
Andrew Morton <akpm@linux-foundation.org>,
Michal Hocko <mhocko@suse.com>,
Oscar Salvador <osalvador@suse.de>,
Jason Gunthorpe <jgg@ziepe.ca>, Peter Xu <peterx@redhat.com>,
Shuah Khan <shuah@kernel.org>,
linux-kselftest@vger.kernel.org
Subject: Re: [PATCH resend v2 3/5] MAINTAINERS: add tools/testing/selftests/vm/ to MEMORY MANAGEMENT
Date: Tue, 11 May 2021 12:47:45 +0300 [thread overview]
Message-ID: <YJpSwfKo4PSb14U6@kernel.org> (raw)
In-Reply-To: <20210511081534.3507-4-david@redhat.com>
On Tue, May 11, 2021 at 10:15:32AM +0200, David Hildenbrand wrote:
> MEMORY MANAGEMENT seems to be a good fit.
>
> Cc: Andrew Morton <akpm@linux-foundation.org>
> Cc: Michal Hocko <mhocko@suse.com>
> Cc: Oscar Salvador <osalvador@suse.de>
> Cc: Jason Gunthorpe <jgg@ziepe.ca>
> Cc: Peter Xu <peterx@redhat.com>
> Cc: Shuah Khan <shuah@kernel.org>
> Cc: linux-kselftest@vger.kernel.org
> Signed-off-by: David Hildenbrand <david@redhat.com>
Acked-by: Mike Rapoport <rppt@linux.ibm.com>
> ---
> MAINTAINERS | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/MAINTAINERS b/MAINTAINERS
> index 9450e052f1b1..cd267d218e08 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -11566,6 +11566,7 @@ F: include/linux/mm.h
> F: include/linux/mmzone.h
> F: include/linux/vmalloc.h
> F: mm/
> +F: tools/testing/selftests/vm/
>
> MEMORY TECHNOLOGY DEVICES (MTD)
> M: Miquel Raynal <miquel.raynal@bootlin.com>
> --
> 2.30.2
>
>
--
Sincerely yours,
Mike.
next prev parent reply other threads:[~2021-05-11 9:47 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-11 8:15 [PATCH resend v2 0/5] mm/madvise: introduce MADV_POPULATE_(READ|WRITE) to prefault page tables David Hildenbrand
2021-05-11 8:15 ` [PATCH resend v2 1/5] mm: make variable names for populate_vma_page_range() consistent David Hildenbrand
2021-05-11 9:54 ` Oscar Salvador
2021-05-11 9:56 ` Oscar Salvador
2021-05-11 8:15 ` [PATCH resend v2 2/5] mm/madvise: introduce MADV_POPULATE_(READ|WRITE) to prefault page tables David Hildenbrand
2021-05-11 8:15 ` David Hildenbrand
2021-05-18 10:07 ` Michal Hocko
2021-05-18 10:07 ` Michal Hocko
2021-05-18 10:32 ` David Hildenbrand
2021-05-18 10:32 ` David Hildenbrand
2021-05-18 11:17 ` Michal Hocko
2021-05-18 11:17 ` Michal Hocko
2021-05-18 12:03 ` David Hildenbrand
2021-05-18 12:03 ` David Hildenbrand
2021-05-20 13:44 ` Michal Hocko
2021-05-20 13:44 ` Michal Hocko
2021-05-21 8:48 ` David Hildenbrand
2021-05-21 8:48 ` David Hildenbrand
2021-05-11 8:15 ` [PATCH resend v2 3/5] MAINTAINERS: add tools/testing/selftests/vm/ to MEMORY MANAGEMENT David Hildenbrand
2021-05-11 9:47 ` Mike Rapoport [this message]
2021-05-11 8:15 ` [PATCH resend v2 4/5] selftests/vm: add protection_keys_32 / protection_keys_64 to gitignore David Hildenbrand
2021-05-11 8:15 ` [PATCH resend v2 5/5] selftests/vm: add test for MADV_POPULATE_(READ|WRITE) David Hildenbrand
2021-05-11 8:15 ` David Hildenbrand
2021-06-08 16:00 ` [PATCH] madvise.2: Document MADV_POPULATE_READ and MADV_POPULATE_WRITE David Hildenbrand
2021-06-08 16:00 ` David Hildenbrand
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=YJpSwfKo4PSb14U6@kernel.org \
--to=rppt@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=david@redhat.com \
--cc=jgg@ziepe.ca \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@suse.com \
--cc=osalvador@suse.de \
--cc=peterx@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 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.