All of lore.kernel.org
 help / color / mirror / Atom feed
From: Catalin Marinas <catalin.marinas@arm.com>
To: Anshuman Khandual <anshuman.khandual@arm.com>
Cc: linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org, Will Deacon <will.deacon@arm.com>,
	Steve Capper <steve.capper@arm.com>
Subject: Re: [PATCH] arm64/mm: Drop [PTE|PMD]_TYPE_FAULT
Date: Wed, 26 Jun 2019 11:21:29 +0100	[thread overview]
Message-ID: <20190626102129.GB1161@arrakis.emea.arm.com> (raw)
In-Reply-To: <1561538170-26594-1-git-send-email-anshuman.khandual@arm.com>

On Wed, Jun 26, 2019 at 02:06:10PM +0530, Anshuman Khandual wrote:
> This was added part of the original commit which added MMU definitions.
> 
> commit 4f04d8f00545 ("arm64: MMU definitions").
> 
> These symbols never got used as confirmed from a git log search.
> 
> git log -p arch/arm64/ | grep PTE_TYPE_FAULT
> git log -p arch/arm64/ | grep PMD_TYPE_FAULT
> 
> These probably meant to identify non present entries which can now be
> achieved with PMD_SECT_VALID or PTE_VALID bits. Hence just drop these
> unused symbols which are not required anymore.
> 
> Cc: Catalin Marinas <catalin.marinas@arm.com>
> Cc: Will Deacon <will.deacon@arm.com>
> Cc: Steve Capper <steve.capper@arm.com>
> Signed-off-by: Anshuman Khandual <anshuman.khandual@arm.com>

Thanks. Queued for 5.3.

-- 
Catalin

WARNING: multiple messages have this Message-ID (diff)
From: Catalin Marinas <catalin.marinas@arm.com>
To: Anshuman Khandual <anshuman.khandual@arm.com>
Cc: Will Deacon <will.deacon@arm.com>,
	linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	Steve Capper <steve.capper@arm.com>
Subject: Re: [PATCH] arm64/mm: Drop [PTE|PMD]_TYPE_FAULT
Date: Wed, 26 Jun 2019 11:21:29 +0100	[thread overview]
Message-ID: <20190626102129.GB1161@arrakis.emea.arm.com> (raw)
In-Reply-To: <1561538170-26594-1-git-send-email-anshuman.khandual@arm.com>

On Wed, Jun 26, 2019 at 02:06:10PM +0530, Anshuman Khandual wrote:
> This was added part of the original commit which added MMU definitions.
> 
> commit 4f04d8f00545 ("arm64: MMU definitions").
> 
> These symbols never got used as confirmed from a git log search.
> 
> git log -p arch/arm64/ | grep PTE_TYPE_FAULT
> git log -p arch/arm64/ | grep PMD_TYPE_FAULT
> 
> These probably meant to identify non present entries which can now be
> achieved with PMD_SECT_VALID or PTE_VALID bits. Hence just drop these
> unused symbols which are not required anymore.
> 
> Cc: Catalin Marinas <catalin.marinas@arm.com>
> Cc: Will Deacon <will.deacon@arm.com>
> Cc: Steve Capper <steve.capper@arm.com>
> Signed-off-by: Anshuman Khandual <anshuman.khandual@arm.com>

Thanks. Queued for 5.3.

-- 
Catalin

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

  reply	other threads:[~2019-06-26 10:21 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-26  8:36 [PATCH] arm64/mm: Drop [PTE|PMD]_TYPE_FAULT Anshuman Khandual
2019-06-26  8:36 ` Anshuman Khandual
2019-06-26 10:21 ` Catalin Marinas [this message]
2019-06-26 10:21   ` Catalin Marinas

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=20190626102129.GB1161@arrakis.emea.arm.com \
    --to=catalin.marinas@arm.com \
    --cc=anshuman.khandual@arm.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=steve.capper@arm.com \
    --cc=will.deacon@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.