From: Joe Perches <joe@perches.com>
To: Ralph Campbell <rcampbell@nvidia.com>,
linux-rdma@vger.kernel.org, linux-mm@kvack.org,
linux-kselftest@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: Jerome Glisse <jglisse@redhat.com>,
John Hubbard <jhubbard@nvidia.com>,
Christoph Hellwig <hch@lst.de>,
Jason Gunthorpe <jgg@mellanox.com>,
Andrew Morton <akpm@linux-foundation.org>,
Shuah Khan <shuah@kernel.org>
Subject: Re: [PATCH v9 3/3] MAINTAINERS: add HMM selftests
Date: Fri, 17 Apr 2020 17:59:03 -0700 [thread overview]
Message-ID: <13a8e8efd56d00945e375760f7f065fb020287a1.camel@perches.com> (raw)
In-Reply-To: <20200417235458.13462-4-rcampbell@nvidia.com>
On Fri, 2020-04-17 at 16:54 -0700, Ralph Campbell wrote:
> Add files for HMM selftests.
>
> Signed-off-by: Ralph Campbell <rcampbell@nvidia.com>
> ---
> MAINTAINERS | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/MAINTAINERS b/MAINTAINERS
> index e64e5db31497..072921b7bae2 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -7729,6 +7729,9 @@ S: Maintained
> F: Documentation/vm/hmm.rst
> F: include/linux/hmm*
> F: mm/hmm*
> +F: include/uapi/linux/test_hmm*
> +F: lib/test_hmm*
> +F: tools/testing/selftests/vm/*hmm*
file patterns in alphabetic order please:
F Documentation/vm/hmm.rst
F: include/linux/hmm*
F: include/uapi/linux/test_hmm*
F: lib/test_hmm*
F: mm/hmm*
F: tools/testing/selftests/vm/*hmm*
next prev parent reply other threads:[~2020-04-18 1:01 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-17 23:54 [PATCH v9 0/3] mm/hmm/test: add self tests for HMM Ralph Campbell
2020-04-17 23:54 ` [PATCH v9 1/3] mm/hmm/test: add selftest driver " Ralph Campbell
2020-04-17 23:54 ` [PATCH v9 2/3] mm/hmm/test: add selftests " Ralph Campbell
2020-04-17 23:54 ` [PATCH v9 3/3] MAINTAINERS: add HMM selftests Ralph Campbell
2020-04-18 0:59 ` Joe Perches [this message]
2020-04-18 1:13 ` Andrew Morton
2020-04-18 1:17 ` Joe Perches
2020-04-20 18:38 ` Ralph Campbell
2020-04-18 6:06 ` Leon Romanovsky
2020-04-20 18:39 ` Ralph Campbell
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=13a8e8efd56d00945e375760f7f065fb020287a1.camel@perches.com \
--to=joe@perches.com \
--cc=akpm@linux-foundation.org \
--cc=hch@lst.de \
--cc=jgg@mellanox.com \
--cc=jglisse@redhat.com \
--cc=jhubbard@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-rdma@vger.kernel.org \
--cc=rcampbell@nvidia.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