From: Marek Szyprowski <m.szyprowski@samsung.com>
To: Oreoluwa Babatunde <oreoluwa.babatunde@oss.qualcomm.com>,
robh@kernel.org, robin.murphy@arm.com
Cc: saravanak@google.com, quic_obabatun@quicinc.com,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
iommu@lists.linux.dev, william.zhang@broadcom.com,
kernel@oss.qualcomm.com, will@kernel.org, djakov@kernel.org
Subject: Re: [PATCH v4] of: reserved_mem: Restructure call site for dma_contiguous_early_fixup()
Date: Mon, 11 Aug 2025 13:07:39 +0200 [thread overview]
Message-ID: <416dbaed-a68f-4edb-a20c-94cb4c53c748@samsung.com> (raw)
In-Reply-To: <20250806172421.2748302-1-oreoluwa.babatunde@oss.qualcomm.com>
On 06.08.2025 19:24, Oreoluwa Babatunde wrote:
> Restructure the call site for dma_contiguous_early_fixup() to
> where the reserved_mem nodes are being parsed from the DT so that
> dma_mmu_remap[] is populated before dma_contiguous_remap() is called.
>
> Fixes: 8a6e02d0c00e ("of: reserved_mem: Restructure how the reserved memory regions are processed")
> Signed-off-by: Oreoluwa Babatunde <oreoluwa.babatunde@oss.qualcomm.com>
> Tested-by: William Zhang <william.zhang@broadcom.com>
Thanks, applied to dma-mapping-fixes branch.
Best regards
--
Marek Szyprowski, PhD
Samsung R&D Institute Poland
next prev parent reply other threads:[~2025-08-11 11:07 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20250806172503eucas1p264d6731c73592fcc380b0dcc21cdeadf@eucas1p2.samsung.com>
2025-08-06 17:24 ` Oreoluwa Babatunde
2025-08-11 11:07 ` Marek Szyprowski [this message]
2025-11-26 1:37 ` Ye Li
2025-11-28 12:43 ` Marek Szyprowski
2025-12-01 6:31 ` Oreoluwa Babatunde
2025-12-01 7:51 ` Marek Szyprowski
2025-12-02 6:54 ` Oreoluwa Babatunde
2025-12-10 0:29 ` Oreoluwa Babatunde
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=416dbaed-a68f-4edb-a20c-94cb4c53c748@samsung.com \
--to=m.szyprowski@samsung.com \
--cc=devicetree@vger.kernel.org \
--cc=djakov@kernel.org \
--cc=iommu@lists.linux.dev \
--cc=kernel@oss.qualcomm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=oreoluwa.babatunde@oss.qualcomm.com \
--cc=quic_obabatun@quicinc.com \
--cc=robh@kernel.org \
--cc=robin.murphy@arm.com \
--cc=saravanak@google.com \
--cc=will@kernel.org \
--cc=william.zhang@broadcom.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®