All the mail mirrored from lore.kernel.org
 help / color / mirror / Atom feed
From: Jason Gunthorpe <jgg@nvidia.com>
To: David Hildenbrand <david@redhat.com>
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org,
	Andrew Morton <akpm@linux-foundation.org>,
	Mike Rapoport <rppt@kernel.org>,
	John Hubbard <jhubbard@nvidia.com>, Peter Xu <peterx@redhat.com>,
	linux-arm-kernel@lists.infradead.org, loongarch@lists.linux.dev,
	linux-mips@vger.kernel.org, linuxppc-dev@lists.ozlabs.org,
	linux-s390@vger.kernel.org, linux-sh@vger.kernel.org,
	linux-perf-users@vger.kernel.org, linux-fsdevel@vger.kernel.org,
	linux-riscv@lists.infradead.org, x86@kernel.org
Subject: Re: [PATCH v1 3/3] mm: use "GUP-fast" instead "fast GUP" in remaining comments
Date: Tue, 2 Apr 2024 19:33:09 -0300	[thread overview]
Message-ID: <20240402223309.GS946323@nvidia.com> (raw)
In-Reply-To: <20240402125516.223131-4-david@redhat.com>

On Tue, Apr 02, 2024 at 02:55:16PM +0200, David Hildenbrand wrote:
> Let's fixup the remaining comments to consistently call that thing
> "GUP-fast". With this change, we consistently call it "GUP-fast".
> 
> Reviewed-by: Mike Rapoport (IBM) <rppt@kernel.org>
> Signed-off-by: David Hildenbrand <david@redhat.com>
> ---
>  mm/filemap.c    | 2 +-
>  mm/khugepaged.c | 2 +-
>  2 files changed, 2 insertions(+), 2 deletions(-)

Reviewed-by: Jason Gunthorpe <jgg@nvidia.com>

Jason

WARNING: multiple messages have this Message-ID (diff)
From: Jason Gunthorpe <jgg@nvidia.com>
To: David Hildenbrand <david@redhat.com>
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org,
	Andrew Morton <akpm@linux-foundation.org>,
	Mike Rapoport <rppt@kernel.org>,
	John Hubbard <jhubbard@nvidia.com>, Peter Xu <peterx@redhat.com>,
	linux-arm-kernel@lists.infradead.org, loongarch@lists.linux.dev,
	linux-mips@vger.kernel.org, linuxppc-dev@lists.ozlabs.org,
	linux-s390@vger.kernel.org, linux-sh@vger.kernel.org,
	linux-perf-users@vger.kernel.org, linux-fsdevel@vger.kernel.org,
	linux-riscv@lists.infradead.org, x86@kernel.org
Subject: Re: [PATCH v1 3/3] mm: use "GUP-fast" instead "fast GUP" in remaining comments
Date: Tue, 2 Apr 2024 19:33:09 -0300	[thread overview]
Message-ID: <20240402223309.GS946323@nvidia.com> (raw)
In-Reply-To: <20240402125516.223131-4-david@redhat.com>

On Tue, Apr 02, 2024 at 02:55:16PM +0200, David Hildenbrand wrote:
> Let's fixup the remaining comments to consistently call that thing
> "GUP-fast". With this change, we consistently call it "GUP-fast".
> 
> Reviewed-by: Mike Rapoport (IBM) <rppt@kernel.org>
> Signed-off-by: David Hildenbrand <david@redhat.com>
> ---
>  mm/filemap.c    | 2 +-
>  mm/khugepaged.c | 2 +-
>  2 files changed, 2 insertions(+), 2 deletions(-)

Reviewed-by: Jason Gunthorpe <jgg@nvidia.com>

Jason

_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv

WARNING: multiple messages have this Message-ID (diff)
From: Jason Gunthorpe <jgg@nvidia.com>
To: David Hildenbrand <david@redhat.com>
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org,
	Andrew Morton <akpm@linux-foundation.org>,
	Mike Rapoport <rppt@kernel.org>,
	John Hubbard <jhubbard@nvidia.com>, Peter Xu <peterx@redhat.com>,
	linux-arm-kernel@lists.infradead.org, loongarch@lists.linux.dev,
	linux-mips@vger.kernel.org, linuxppc-dev@lists.ozlabs.org,
	linux-s390@vger.kernel.org, linux-sh@vger.kernel.org,
	linux-perf-users@vger.kernel.org, linux-fsdevel@vger.kernel.org,
	linux-riscv@lists.infradead.org, x86@kernel.org
Subject: Re: [PATCH v1 3/3] mm: use "GUP-fast" instead "fast GUP" in remaining comments
Date: Tue, 2 Apr 2024 19:33:09 -0300	[thread overview]
Message-ID: <20240402223309.GS946323@nvidia.com> (raw)
In-Reply-To: <20240402125516.223131-4-david@redhat.com>

On Tue, Apr 02, 2024 at 02:55:16PM +0200, David Hildenbrand wrote:
> Let's fixup the remaining comments to consistently call that thing
> "GUP-fast". With this change, we consistently call it "GUP-fast".
> 
> Reviewed-by: Mike Rapoport (IBM) <rppt@kernel.org>
> Signed-off-by: David Hildenbrand <david@redhat.com>
> ---
>  mm/filemap.c    | 2 +-
>  mm/khugepaged.c | 2 +-
>  2 files changed, 2 insertions(+), 2 deletions(-)

Reviewed-by: Jason Gunthorpe <jgg@nvidia.com>

Jason

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

WARNING: multiple messages have this Message-ID (diff)
From: Jason Gunthorpe <jgg@nvidia.com>
To: David Hildenbrand <david@redhat.com>
Cc: linux-s390@vger.kernel.org, linux-sh@vger.kernel.org,
	John Hubbard <jhubbard@nvidia.com>,
	x86@kernel.org, linux-kernel@vger.kernel.org,
	Peter Xu <peterx@redhat.com>,
	linux-mips@vger.kernel.org, linux-perf-users@vger.kernel.org,
	linux-mm@kvack.org, linux-arm-kernel@lists.infradead.org,
	loongarch@lists.linux.dev, linux-fsdevel@vger.kernel.org,
	Andrew Morton <akpm@linux-foundation.org>,
	linuxppc-dev@lists.ozlabs.org, linux-riscv@lists.infradead.org,
	Mike Rapoport <rppt@kernel.org>
Subject: Re: [PATCH v1 3/3] mm: use "GUP-fast" instead "fast GUP" in remaining comments
Date: Tue, 2 Apr 2024 19:33:09 -0300	[thread overview]
Message-ID: <20240402223309.GS946323@nvidia.com> (raw)
In-Reply-To: <20240402125516.223131-4-david@redhat.com>

On Tue, Apr 02, 2024 at 02:55:16PM +0200, David Hildenbrand wrote:
> Let's fixup the remaining comments to consistently call that thing
> "GUP-fast". With this change, we consistently call it "GUP-fast".
> 
> Reviewed-by: Mike Rapoport (IBM) <rppt@kernel.org>
> Signed-off-by: David Hildenbrand <david@redhat.com>
> ---
>  mm/filemap.c    | 2 +-
>  mm/khugepaged.c | 2 +-
>  2 files changed, 2 insertions(+), 2 deletions(-)

Reviewed-by: Jason Gunthorpe <jgg@nvidia.com>

Jason

  reply	other threads:[~2024-04-02 22:33 UTC|newest]

Thread overview: 68+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-02 12:55 [PATCH v1 0/3] mm/gup: consistently call it GUP-fast David Hildenbrand
2024-04-02 12:55 ` David Hildenbrand
2024-04-02 12:55 ` David Hildenbrand
2024-04-02 12:55 ` David Hildenbrand
2024-04-02 12:55 ` [PATCH v1 1/3] mm/gup: consistently name GUP-fast functions David Hildenbrand
2024-04-02 12:55   ` David Hildenbrand
2024-04-02 12:55   ` David Hildenbrand
2024-04-02 12:55   ` David Hildenbrand
2024-04-13 20:07   ` John Hubbard
2024-04-13 20:07     ` John Hubbard
2024-04-13 20:07     ` John Hubbard
2024-04-13 20:07     ` John Hubbard
2024-04-26  7:17   ` David Hildenbrand
2024-04-26  7:17     ` David Hildenbrand
2024-04-26  7:17     ` David Hildenbrand
2024-04-26  7:17     ` David Hildenbrand
2024-04-26 13:44     ` Peter Xu
2024-04-26 13:44       ` Peter Xu
2024-04-26 13:44       ` Peter Xu
2024-04-26 13:44       ` Peter Xu
2024-04-26 16:12       ` Peter Xu
2024-04-26 16:12         ` Peter Xu
2024-04-26 16:12         ` Peter Xu
2024-04-26 16:12         ` Peter Xu
2024-04-26 17:28         ` David Hildenbrand
2024-04-26 17:28           ` David Hildenbrand
2024-04-26 17:28           ` David Hildenbrand
2024-04-26 17:28           ` David Hildenbrand
2024-04-26 21:20           ` Peter Xu
2024-04-26 21:20             ` Peter Xu
2024-04-26 21:20             ` Peter Xu
2024-04-26 21:20             ` Peter Xu
2024-04-26 21:33             ` David Hildenbrand
2024-04-26 21:33               ` David Hildenbrand
2024-04-26 21:33               ` David Hildenbrand
2024-04-26 21:33               ` David Hildenbrand
2024-04-26 21:58               ` Peter Xu
2024-04-26 21:58                 ` Peter Xu
2024-04-26 21:58                 ` Peter Xu
2024-04-26 21:58                 ` Peter Xu
2024-04-27  6:58                 ` David Hildenbrand
2024-04-27  6:58                   ` David Hildenbrand
2024-04-27  6:58                   ` David Hildenbrand
2024-04-27  6:58                   ` David Hildenbrand
2024-04-02 12:55 ` [PATCH v1 2/3] mm/treewide: rename CONFIG_HAVE_FAST_GUP to CONFIG_HAVE_GUP_FAST David Hildenbrand
2024-04-02 12:55   ` David Hildenbrand
2024-04-02 12:55   ` David Hildenbrand
2024-04-02 12:55   ` David Hildenbrand
2024-04-02 22:32   ` Jason Gunthorpe
2024-04-02 22:32     ` Jason Gunthorpe
2024-04-02 22:32     ` Jason Gunthorpe
2024-04-02 22:32     ` Jason Gunthorpe
2024-04-13 20:11   ` John Hubbard
2024-04-13 20:11     ` John Hubbard
2024-04-13 20:11     ` John Hubbard
2024-04-13 20:11     ` John Hubbard
2024-04-02 12:55 ` [PATCH v1 3/3] mm: use "GUP-fast" instead "fast GUP" in remaining comments David Hildenbrand
2024-04-02 12:55   ` David Hildenbrand
2024-04-02 12:55   ` David Hildenbrand
2024-04-02 12:55   ` David Hildenbrand
2024-04-02 22:33   ` Jason Gunthorpe [this message]
2024-04-02 22:33     ` Jason Gunthorpe
2024-04-02 22:33     ` Jason Gunthorpe
2024-04-02 22:33     ` Jason Gunthorpe
2024-04-13 20:12   ` John Hubbard
2024-04-13 20:12     ` John Hubbard
2024-04-13 20:12     ` John Hubbard
2024-04-13 20:12     ` John Hubbard

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=20240402223309.GS946323@nvidia.com \
    --to=jgg@nvidia.com \
    --cc=akpm@linux-foundation.org \
    --cc=david@redhat.com \
    --cc=jhubbard@nvidia.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mips@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=linux-perf-users@vger.kernel.org \
    --cc=linux-riscv@lists.infradead.org \
    --cc=linux-s390@vger.kernel.org \
    --cc=linux-sh@vger.kernel.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=loongarch@lists.linux.dev \
    --cc=peterx@redhat.com \
    --cc=rppt@kernel.org \
    --cc=x86@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.