All of lore.kernel.org
 help / color / mirror / Atom feed
From: Will Deacon <will@kernel.org>
To: Anshuman Khandual <anshuman.khandual@arm.com>,
	linux-arm-kernel@lists.infradead.org
Cc: catalin.marinas@arm.com, kernel-team@android.com,
	Will Deacon <will@kernel.org>,
	linux-kernel@vger.kernel.org, Mark Rutland <mark.rutland@arm.com>
Subject: Re: [PATCH] arm64/mm: Rename ARM64_SWAPPER_USES_SECTION_MAPS
Date: Mon, 21 Jun 2021 19:13:59 +0100	[thread overview]
Message-ID: <162429614365.4116678.14416977840509312271.b4-ty@kernel.org> (raw)
In-Reply-To: <1623991622-24294-1-git-send-email-anshuman.khandual@arm.com>

On Fri, 18 Jun 2021 10:17:02 +0530, Anshuman Khandual wrote:
> ARM64_SWAPPER_USES_SECTION_MAPS implies that a PMD level huge page mappings
> are used for swapper, idmap and vmemmap. Lets make it PMD explicit removing
> any possible confusion with generic memory sections and also bit generic as
> it's applicable for idmap and vmemmap mappings as well. Hence rename it as
> ARM64_KERNEL_USES_PMD_MAPS instead.

Applied to arm64 (for-next/mm), thanks!

[1/1] arm64/mm: Rename ARM64_SWAPPER_USES_SECTION_MAPS
      https://git.kernel.org/arm64/c/2062d44da349

Cheers,
-- 
Will

https://fixes.arm64.dev
https://next.arm64.dev
https://will.arm64.dev

WARNING: multiple messages have this Message-ID (diff)
From: Will Deacon <will@kernel.org>
To: Anshuman Khandual <anshuman.khandual@arm.com>,
	linux-arm-kernel@lists.infradead.org
Cc: catalin.marinas@arm.com, kernel-team@android.com,
	Will Deacon <will@kernel.org>,
	linux-kernel@vger.kernel.org, Mark Rutland <mark.rutland@arm.com>
Subject: Re: [PATCH] arm64/mm: Rename ARM64_SWAPPER_USES_SECTION_MAPS
Date: Mon, 21 Jun 2021 19:13:59 +0100	[thread overview]
Message-ID: <162429614365.4116678.14416977840509312271.b4-ty@kernel.org> (raw)
In-Reply-To: <1623991622-24294-1-git-send-email-anshuman.khandual@arm.com>

On Fri, 18 Jun 2021 10:17:02 +0530, Anshuman Khandual wrote:
> ARM64_SWAPPER_USES_SECTION_MAPS implies that a PMD level huge page mappings
> are used for swapper, idmap and vmemmap. Lets make it PMD explicit removing
> any possible confusion with generic memory sections and also bit generic as
> it's applicable for idmap and vmemmap mappings as well. Hence rename it as
> ARM64_KERNEL_USES_PMD_MAPS instead.

Applied to arm64 (for-next/mm), thanks!

[1/1] arm64/mm: Rename ARM64_SWAPPER_USES_SECTION_MAPS
      https://git.kernel.org/arm64/c/2062d44da349

Cheers,
-- 
Will

https://fixes.arm64.dev
https://next.arm64.dev
https://will.arm64.dev

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

  parent reply	other threads:[~2021-06-21 18:14 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-18  4:47 [PATCH] arm64/mm: Rename ARM64_SWAPPER_USES_SECTION_MAPS Anshuman Khandual
2021-06-18  4:47 ` Anshuman Khandual
2021-06-18  8:23 ` Catalin Marinas
2021-06-18  8:23   ` Catalin Marinas
2021-06-21 18:13 ` Will Deacon [this message]
2021-06-21 18:13   ` Will Deacon

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=162429614365.4116678.14416977840509312271.b4-ty@kernel.org \
    --to=will@kernel.org \
    --cc=anshuman.khandual@arm.com \
    --cc=catalin.marinas@arm.com \
    --cc=kernel-team@android.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mark.rutland@arm.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 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.