From: Sam Protsenko <semen.protsenko@linaro.org>
To: Tom Rini <trini@konsulko.com>
Cc: Ilias Apalodimas <ilias.apalodimas@linaro.org>,
Sughosh Ganu <sughosh.ganu@linaro.org>,
Heinrich Schuchardt <xypron.glpk@gmx.de>,
Simon Glass <sjg@chromium.org>,
Caleb Connolly <caleb.connolly@linaro.org>,
Marek Vasut <marex@denx.de>,
Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
Patrick Delaunay <patrick.delaunay@foss.st.com>,
u-boot@lists.denx.de
Subject: [PATCH v2 0/4] lmb: Improve style
Date: Tue, 10 Dec 2024 20:25:46 -0600 [thread overview]
Message-ID: <20241211022550.2995-1-semen.protsenko@linaro.org> (raw)
This series is intended to be picked up for -next.
Cleanup the LMB code a bit, after fixing the false positive error
messages. No functional change. This series depends on [1] (which is
"lmb: Fix reserving the same region multiple times").
Changes in v2:
- The original series was split by actual functional change patches
[1] and cleanup patches (this series)
- Collected review tags
[1] https://lists.denx.de/pipermail/u-boot/2024-December/574606.html
Sam Protsenko (4):
lmb: Fix flags data type in lmb_add_region_flags()
lmb: Make const flag_str[] in lmb_print_region_flags() more const
lmb: Improve coding style
lmb: Improve kernel-doc comments
include/lmb.h | 125 ++++++++++++++++++++++++++++++--------------------
lib/lmb.c | 87 ++++++++---------------------------
2 files changed, 94 insertions(+), 118 deletions(-)
--
2.39.5
next reply other threads:[~2024-12-11 2:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-11 2:25 Sam Protsenko [this message]
2024-12-11 2:25 ` [PATCH v2 1/4] lmb: Fix flags data type in lmb_add_region_flags() Sam Protsenko
2024-12-11 2:25 ` [PATCH v2 2/4] lmb: Make const flag_str[] in lmb_print_region_flags() more const Sam Protsenko
2024-12-11 2:25 ` [PATCH v2 3/4] lmb: Improve coding style Sam Protsenko
2024-12-11 2:25 ` [PATCH v2 4/4] lmb: Improve kernel-doc comments Sam Protsenko
2024-12-30 21:52 ` [PATCH v2 0/4] lmb: Improve style 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=20241211022550.2995-1-semen.protsenko@linaro.org \
--to=semen.protsenko@linaro.org \
--cc=caleb.connolly@linaro.org \
--cc=ilias.apalodimas@linaro.org \
--cc=laurent.pinchart@ideasonboard.com \
--cc=marex@denx.de \
--cc=patrick.delaunay@foss.st.com \
--cc=sjg@chromium.org \
--cc=sughosh.ganu@linaro.org \
--cc=trini@konsulko.com \
--cc=u-boot@lists.denx.de \
--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