From: Udit Kumar <u-kumar1@ti.com>
To: <nm@ti.com>, <vigneshr@ti.com>, <patrick.delaunay@foss.st.com>,
<sjoerd@collabora.com>, <sjg@google.com>, <trini@konsulko.com>
Cc: <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>, Udit Kumar <u-kumar1@ti.com>
Subject: [PATCH v2 0/2] lmb: remove overlapping region with next range
Date: Tue, 26 Sep 2023 16:54:41 +0530 [thread overview]
Message-ID: <20230926112443.4190471-1-u-kumar1@ti.com> (raw)
In case, newly address range to be added is coalescing with some region
but also overlapping with next region.
In such, case overlapped region was getting created.
This patch series, detect such overlap and coalescing such region as one
Change logs:
test logs
https://gist.github.com/uditkumarti/7be37a662fabfcfefb74d1a67ccde2bd
Changes in v2:
Patch 1/2: Corrected typo
Patch 2/2 : Added test case as suggested by Simon
Link to v1:
https://lore.kernel.org/all/20230924111832.3741245-1-u-kumar1@ti.com/#t
Udit Kumar (2):
lmb: remove overlapping region with next range
test: lmb: Added test case for coaleacse with first and overlap with
Second
lib/lmb.c | 37 +++++++++++++++++++++++++++++++++----
test/lib/lmb.c | 13 ++++++++++++-
2 files changed, 45 insertions(+), 5 deletions(-)
--
2.34.1
next reply other threads:[~2023-09-26 11:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-26 11:24 Udit Kumar [this message]
2023-09-26 11:24 ` [PATCH v2 1/2] lmb: remove overlapping region with next range Udit Kumar
2023-10-10 12:58 ` Tom Rini
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=20230926112443.4190471-1-u-kumar1@ti.com \
--to=u-kumar1@ti.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=sam.shih@mediatek.com \
--cc=sjg@chromium.org \
--cc=sjg@google.com \
--cc=sjoerd@collabora.com \
--cc=sumit.garg@linaro.org \
--cc=trini@konsulko.com \
--cc=u-boot@lists.denx.de \
--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