From: Rob Herring <robh@kernel.org>
To: Marek Szyprowski <m.szyprowski@samsung.com>
Cc: Saravana Kannan <saravanak@kernel.org>,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
linux-mm@kvack.org, iommu@lists.linux.dev,
Krzysztof Kozlowski <krzk@kernel.org>,
Oreoluwa Babatunde <oreoluwa.babatunde@oss.qualcomm.com>,
Andrew Morton <akpm@linux-foundation.org>,
Robin Murphy <robin.murphy@arm.com>
Subject: Re: [PATCH 0/7] Refactor reserved memory regions handling code
Date: Sun, 22 Mar 2026 17:44:32 -0500 [thread overview]
Message-ID: <20260322224432.GA16628-robh@kernel.org> (raw)
In-Reply-To: <20260313150802.1121442-1-m.szyprowski@samsung.com>
On Fri, Mar 13, 2026 at 04:07:55PM +0100, Marek Szyprowski wrote:
> Hello,
>
> The reserved memory regions handling code was reworked to handle
> unlimited so called "static" memory nodes in commit 00c9a452a235 ("of:
> reserved_mem: Add code to dynamically allocate reserved_mem array").
>
> The side effect of this rework was a set of bugs fixed later by commits
> 0fd17e598333 ("of: reserved_mem: Allow reserved_mem framework detect
> "cma=" kernel param") and 2c223f7239f3 ("of: reserved_mem: Restructure
> call site for dma_contiguous_early_fixup()"). As a result, the code in
> drivers/of/of_reserved_mem.c became a mix of generic code and CMA
> specific fixups.
>
> In this patchset I try to untangle this spaghetti and perform some code
> cleanup. I hope nothing breaks this time.
This all looks good to me. Can you respin and fixup the issues.
Rob
prev parent reply other threads:[~2026-03-22 22:44 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20260313150809eucas1p169ab0904a217a04e0601e2ef01854c73@eucas1p1.samsung.com>
2026-03-13 15:07 ` [PATCH 0/7] Refactor reserved memory regions handling code Marek Szyprowski
2026-03-13 15:07 ` [PATCH 1/7] of: reserved_mem: remove fdt node from the structure Marek Szyprowski
2026-03-13 15:07 ` [PATCH 2/7] of: reserved_mem: use -ENODEV instead of -ENOENT Marek Szyprowski
2026-03-13 15:07 ` [PATCH 3/7] of: reserved_mem: switch to ops based OF_DECLARE() Marek Szyprowski
2026-03-13 15:58 ` Marek Szyprowski
2026-03-14 15:20 ` kernel test robot
2026-03-13 15:07 ` [PATCH 4/7] of: reserved_mem: replace CMA quirks by generic methods Marek Szyprowski
2026-03-13 15:08 ` [PATCH 5/7] of: reserved_mem: rearrange code a bit Marek Szyprowski
2026-03-13 15:08 ` [PATCH 6/7] of: reserved_mem: clarify fdt_scan_reserved_mem*() functions Marek Szyprowski
2026-03-13 15:08 ` [PATCH 7/7] of: reserved_mem: rework fdt_init_reserved_mem_node() Marek Szyprowski
2026-03-14 3:43 ` kernel test robot
2026-03-14 7:57 ` kernel test robot
2026-03-22 22:44 ` Rob Herring [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=20260322224432.GA16628-robh@kernel.org \
--to=robh@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=devicetree@vger.kernel.org \
--cc=iommu@lists.linux.dev \
--cc=krzk@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=m.szyprowski@samsung.com \
--cc=oreoluwa.babatunde@oss.qualcomm.com \
--cc=robin.murphy@arm.com \
--cc=saravanak@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.