linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: John Hubbard <jhubbard@nvidia.com>
To: Lorenzo Stoakes <lorenzo.stoakes@oracle.com>,
	Andrew Morton <akpm@linux-foundation.org>
Cc: David Hildenbrand <david@redhat.com>,
	Jason Gunthorpe <jgg@nvidia.com>, Peter Xu <peterx@redhat.com>,
	linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] MAINTAINERS: add missing test files to mm gup section
Date: Mon, 16 Jun 2025 19:31:05 -0700	[thread overview]
Message-ID: <72fe8b97-6bbb-4744-ae14-a4ecdf74e573@nvidia.com> (raw)
In-Reply-To: <20250616200844.560225-1-lorenzo.stoakes@oracle.com>

On 6/16/25 1:08 PM, Lorenzo Stoakes wrote:
> We previously overlooked GUP test files that sensibly should belong to the
> GUP section, include them now.
> 
> Signed-off-by: Lorenzo Stoakes <lorenzo.stoakes@oracle.com>
> ---
>  MAINTAINERS | 4 ++++
>  1 file changed, 4 insertions(+)
> 
> diff --git a/MAINTAINERS b/MAINTAINERS
> index 4523a6409186..96407b87d1aa 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -15795,6 +15795,10 @@ S:	Maintained
>  W:	http://www.linux-mm.org
>  T:	git git://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm
>  F:	mm/gup.c
> +F:	mm/gup_test.c
> +F:	mm/gup_test.h
> +F:	tools/testing/selftests/mm/gup_longterm.c
> +F:	tools/testing/selftests/mm/gup_test.c
>

Yes, these are all in use. Looks good.

  
>  MEMORY MANAGEMENT - KSM (Kernel Samepage Merging)
>  M:	Andrew Morton <akpm@linux-foundation.org>


Reviewed-by: John Hubbard <jhubbard@nvidia.com>

thanks,
-- 
John Hubbard



      parent reply	other threads:[~2025-06-17  2:31 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-16 20:08 Lorenzo Stoakes
2025-06-16 20:24 ` David Hildenbrand
2025-06-17  2:31 ` John Hubbard [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=72fe8b97-6bbb-4744-ae14-a4ecdf74e573@nvidia.com \
    --to=jhubbard@nvidia.com \
    --cc=akpm@linux-foundation.org \
    --cc=david@redhat.com \
    --cc=jgg@nvidia.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=lorenzo.stoakes@oracle.com \
    --cc=peterx@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