From: Sasha Levin <sashal@kernel.org>
To: Georgi Djakov <quic_c_gdjako@quicinc.com>
Cc: stable@vger.kernel.org, rppt@linux.ibm.com,
anshuman.khandual@arm.com, david@redhat.com, will@kernel.org,
catalin.marinas@arm.com, hch@lst.de, akpm@linux-foundation.org,
surenb@google.com, quic_sudaraja@quicinc.com, djakov@kernel.org
Subject: Re: [PATCH 5.15 2/2] arm64/mm: drop HAVE_ARCH_PFN_VALID
Date: Wed, 20 Apr 2022 10:49:56 -0400 [thread overview]
Message-ID: <YmAdlNslaGbSKUj4@sashalap> (raw)
In-Reply-To: <20220420124341.14982-2-quic_c_gdjako@quicinc.com>
On Wed, Apr 20, 2022 at 05:43:41AM -0700, Georgi Djakov wrote:
>From: Anshuman Khandual <anshuman.khandual@arm.com>
>
>[ Upstream commit 3de360c3fdb34fbdbaf6da3af94367d3fded95d3 ]
>
>CONFIG_SPARSEMEM_VMEMMAP is now the only available memory model on arm64
>platforms and free_unused_memmap() would just return without creating any
>holes in the memmap mapping. There is no need for any special handling in
>pfn_valid() and HAVE_ARCH_PFN_VALID can just be dropped. This also moves
>the pfn upper bits sanity check into generic pfn_valid().
It's not clear why we need this patch in stable.
--
Thanks,
Sasha
next prev parent reply other threads:[~2022-04-20 14:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-20 12:43 [PATCH 5.15 1/2] dma-mapping: remove bogus test for pfn_valid from dma_map_resource Georgi Djakov
2022-04-20 12:43 ` [PATCH 5.15 2/2] arm64/mm: drop HAVE_ARCH_PFN_VALID Georgi Djakov
2022-04-20 14:49 ` Sasha Levin [this message]
2022-04-20 16:11 ` Georgi Djakov
2022-04-21 6:43 ` [PATCH 5.15 1/2] dma-mapping: remove bogus test for pfn_valid from dma_map_resource Greg KH
2022-04-21 7:51 ` Georgi Djakov
2022-04-21 8:25 ` Greg KH
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=YmAdlNslaGbSKUj4@sashalap \
--to=sashal@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=anshuman.khandual@arm.com \
--cc=catalin.marinas@arm.com \
--cc=david@redhat.com \
--cc=djakov@kernel.org \
--cc=hch@lst.de \
--cc=quic_c_gdjako@quicinc.com \
--cc=quic_sudaraja@quicinc.com \
--cc=rppt@linux.ibm.com \
--cc=stable@vger.kernel.org \
--cc=surenb@google.com \
--cc=will@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.