From: Will Deacon <will@kernel.org>
To: linux-arm-kernel@lists.infradead.org,
Anshuman Khandual <anshuman.khandual@arm.com>
Cc: catalin.marinas@arm.com, kernel-team@android.com,
Will Deacon <will@kernel.org>,
Ryan Roberts <ryan.roberts@arm.com>,
linux-kernel@vger.kernel.org, Dev Jain <dev.jain@arm.com>
Subject: Re: [PATCH V2] arm64/mm: Drop redundant addr increment in set_huge_pte_at()
Date: Thu, 17 Jul 2025 11:46:15 +0100 [thread overview]
Message-ID: <175274693707.736549.5663594233250106618.b4-ty@kernel.org> (raw)
In-Reply-To: <20250716035432.293682-1-anshuman.khandual@arm.com>
On Wed, 16 Jul 2025 04:54:32 +0100, Anshuman Khandual wrote:
> The 'addr' need not be incremented in the loop because that is not going to
> be used subsequently.
>
>
Applied to arm64 (for-next/misc), thanks!
[1/1] arm64/mm: Drop redundant addr increment in set_huge_pte_at()
https://git.kernel.org/arm64/c/aa46e18836c0
Cheers,
--
Will
https://fixes.arm64.dev
https://next.arm64.dev
https://will.arm64.dev
prev parent reply other threads:[~2025-07-17 10:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-16 3:54 Anshuman Khandual
2025-07-17 10:46 ` Will Deacon [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=175274693707.736549.5663594233250106618.b4-ty@kernel.org \
--to=will@kernel.org \
--cc=anshuman.khandual@arm.com \
--cc=catalin.marinas@arm.com \
--cc=dev.jain@arm.com \
--cc=kernel-team@android.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ryan.roberts@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®