From: Tom Rini <trini@konsulko.com>
To: Udit Kumar <u-kumar1@ti.com>
Cc: nm@ti.com, vigneshr@ti.com, patrick.delaunay@foss.st.com,
sjoerd@collabora.com, sjg@google.com, u-boot@lists.denx.de,
xypron.glpk@gmx.de, michal.simek@amd.com, dsankouski@gmail.com,
kettenis@openbsd.org, sumit.garg@linaro.org,
sam.shih@mediatek.com, mark.kettenis@xs4all.nl, sjg@chromium.org,
Suman Anna <s-anna@ti.com>
Subject: Re: [PATCH v2 1/2] lmb: remove overlapping region with next range
Date: Tue, 10 Oct 2023 08:58:28 -0400 [thread overview]
Message-ID: <20231010125828.GA2227687@bill-the-cat> (raw)
In-Reply-To: <20230926112443.4190471-2-u-kumar1@ti.com>
[-- Attachment #1: Type: text/plain, Size: 650 bytes --]
On Tue, Sep 26, 2023 at 04:54:42PM +0530, Udit Kumar wrote:
> In case of new memory range to be added is coalesced
> with any already added non last lmb region.
>
> And there is possibility that, then region in which new memory
> range added is not adjacent to next region. But have some
> sections are overlapping.
>
> So along with adjacency check with next lmb region,
> check for overlap should be done.
>
> In case overlap is found, adjust and merge these two lmb
> region into one.
>
> Reported-by: Suman Anna <s-anna@ti.com>
> Signed-off-by: Udit Kumar <u-kumar1@ti.com>
Applied to u-boot/master, thanks!
--
Tom
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 659 bytes --]
next prev parent reply other threads:[~2023-10-10 13:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-26 11:24 [PATCH v2 0/2] lmb: remove overlapping region with next range Udit Kumar
2023-09-26 11:24 ` [PATCH v2 1/2] " Udit Kumar
2023-10-10 12:58 ` Tom Rini [this message]
2023-09-26 11:24 ` [PATCH v2 2/2] test: lmb: Add test for coalescing and overlap range Udit Kumar
2023-09-26 14:16 ` Simon Glass
2023-10-10 12:58 ` Tom Rini
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=20231010125828.GA2227687@bill-the-cat \
--to=trini@konsulko.com \
--cc=dsankouski@gmail.com \
--cc=kettenis@openbsd.org \
--cc=mark.kettenis@xs4all.nl \
--cc=michal.simek@amd.com \
--cc=nm@ti.com \
--cc=patrick.delaunay@foss.st.com \
--cc=s-anna@ti.com \
--cc=sam.shih@mediatek.com \
--cc=sjg@chromium.org \
--cc=sjg@google.com \
--cc=sjoerd@collabora.com \
--cc=sumit.garg@linaro.org \
--cc=u-boot@lists.denx.de \
--cc=u-kumar1@ti.com \
--cc=vigneshr@ti.com \
--cc=xypron.glpk@gmx.de \
/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