linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Jason Gunthorpe <jgg@nvidia.com>
To: peterx@redhat.com
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org,
	linuxppc-dev@lists.ozlabs.org, Yang Shi <shy828301@gmail.com>,
	"Kirill A . Shutemov" <kirill@shutemov.name>,
	Muchun Song <muchun.song@linux.dev>,
	Andrew Morton <akpm@linux-foundation.org>,
	x86@kernel.org
Subject: Re: [PATCH v2 6/7] mm/treewide: Replace pud_large() with pud_leaf()
Date: Mon, 4 Mar 2024 09:09:46 -0400	[thread overview]
Message-ID: <20240304130946.GT9179@nvidia.com> (raw)
In-Reply-To: <20240229084258.599774-7-peterx@redhat.com>

On Thu, Feb 29, 2024 at 04:42:57PM +0800, peterx@redhat.com wrote:
> From: Peter Xu <peterx@redhat.com>
> 
> pud_large() is always defined as pud_leaf().  Merge their usages.  Chose
> pud_leaf() because pud_leaf() is a global API, while pud_large() is not.
> 
> Signed-off-by: Peter Xu <peterx@redhat.com>
> ---
>  arch/powerpc/mm/book3s64/pgtable.c | 2 +-
>  arch/s390/boot/vmem.c              | 2 +-
>  arch/s390/include/asm/pgtable.h    | 4 ++--
>  arch/s390/mm/gmap.c                | 2 +-
>  arch/s390/mm/hugetlbpage.c         | 4 ++--
>  arch/s390/mm/pageattr.c            | 2 +-
>  arch/s390/mm/pgtable.c             | 2 +-
>  arch/s390/mm/vmem.c                | 6 +++---
>  arch/sparc/mm/init_64.c            | 2 +-
>  arch/x86/kvm/mmu/mmu.c             | 2 +-
>  arch/x86/mm/fault.c                | 4 ++--
>  arch/x86/mm/ident_map.c            | 2 +-
>  arch/x86/mm/init_64.c              | 4 ++--
>  arch/x86/mm/kasan_init_64.c        | 2 +-
>  arch/x86/mm/mem_encrypt_identity.c | 2 +-
>  arch/x86/mm/pat/set_memory.c       | 6 +++---
>  arch/x86/mm/pgtable.c              | 2 +-
>  arch/x86/mm/pti.c                  | 2 +-
>  arch/x86/power/hibernate.c         | 2 +-
>  arch/x86/xen/mmu_pv.c              | 4 ++--
>  20 files changed, 29 insertions(+), 29 deletions(-)

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

Jason


  reply	other threads:[~2024-03-04 13:09 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-29  8:42 [PATCH v2 0/7] mm/treewide: Replace pXd_large() with pXd_leaf() peterx
2024-02-29  8:42 ` [PATCH v2 1/7] mm/ppc: Define " peterx
2024-03-04 12:56   ` Jason Gunthorpe
2024-02-29  8:42 ` [PATCH v2 2/7] mm/ppc: Replace pXd_is_leaf() " peterx
2024-03-04 12:57   ` Jason Gunthorpe
2024-02-29  8:42 ` [PATCH v2 3/7] mm/x86: Replace p4d_large() with p4d_leaf() peterx
2024-03-04 12:58   ` Jason Gunthorpe
2024-02-29  8:42 ` [PATCH v2 4/7] mm/x86: Drop two unnecessary pud_leaf() definitions peterx
2024-03-04 13:03   ` Jason Gunthorpe
2024-03-05  3:25     ` Peter Xu
2024-03-04 14:18   ` Thomas Gleixner
2024-02-29  8:42 ` [PATCH v2 5/7] mm/treewide: Replace pmd_large() with pmd_leaf() peterx
2024-03-04 13:09   ` Jason Gunthorpe
2024-02-29  8:42 ` [PATCH v2 6/7] mm/treewide: Replace pud_large() with pud_leaf() peterx
2024-03-04 13:09   ` Jason Gunthorpe [this message]
2024-02-29  8:42 ` [PATCH v2 7/7] mm/treewide: Drop pXd_large() peterx
2024-03-04 13:10   ` Jason Gunthorpe

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=20240304130946.GT9179@nvidia.com \
    --to=jgg@nvidia.com \
    --cc=akpm@linux-foundation.org \
    --cc=kirill@shutemov.name \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=muchun.song@linux.dev \
    --cc=peterx@redhat.com \
    --cc=shy828301@gmail.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox