From: Tom Rini <trini@konsulko.com>
To: Jerome Forissier <jerome.forissier@linaro.org>
Cc: u-boot@lists.denx.de,
Ilias Apalodimas <ilias.apalodimas@linaro.org>,
Lukasz Majewski <lukma@denx.de>,
Mattijs Korpershoek <mkorpershoek@baylibre.com>,
Marek Vasut <marex@denx.de>, Sean Anderson <seanga2@gmail.com>,
Simon Glass <sjg@chromium.org>,
Andre Przywara <andre.przywara@arm.com>,
Samuel Holland <samuel@sholland.org>,
Lukas Funke <lukas.funke@weidmueller.com>,
Jonas Karlman <jonas@kwiboo.se>,
Miquel Raynal <miquel.raynal@bootlin.com>
Subject: Re: [PATCH v2] spl: ram: hide SPL_RAM_SUPPORT
Date: Tue, 10 Sep 2024 11:22:26 -0600 [thread overview]
Message-ID: <20240910172226.GK4252@bill-the-cat> (raw)
In-Reply-To: <20240910130019.3211647-1-jerome.forissier@linaro.org>
[-- Attachment #1: Type: text/plain, Size: 683 bytes --]
On Tue, Sep 10, 2024 at 03:00:18PM +0200, Jerome Forissier wrote:
> Make SPL_RAM_SUPPORT a hidden Kconfig symbol, automatically selected
> by SPL_RAM_DEVICE or SPL_DFU. Avoids the situation where SPL_RAM_SUPPORT
> may be enabled without the other two being enabled, which results in the
> following build warning:
>
> common/spl/spl_ram.c:19:14: warning: ‘spl_ram_load_read’ defined but not used [-Wunused-function]
> 19 | static ulong spl_ram_load_read(struct spl_load_info *load, ulong sector,
> | ^~~~~~~~~~~~~~~~~
>
> Signed-off-by: Jerome Forissier <jerome.forissier@linaro.org>
Reviewed-by: Tom Rini <trini@konsulko.com>
--
Tom
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 659 bytes --]
next prev parent reply other threads:[~2024-09-10 17:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-10 13:00 [PATCH v2] spl: ram: hide SPL_RAM_SUPPORT Jerome Forissier
2024-09-10 13:04 ` Sean Anderson
2024-09-10 17:22 ` Tom Rini [this message]
2024-09-12 13:31 ` Mattijs Korpershoek
2024-09-24 23:40 ` 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=20240910172226.GK4252@bill-the-cat \
--to=trini@konsulko.com \
--cc=andre.przywara@arm.com \
--cc=ilias.apalodimas@linaro.org \
--cc=jerome.forissier@linaro.org \
--cc=jonas@kwiboo.se \
--cc=lukas.funke@weidmueller.com \
--cc=lukma@denx.de \
--cc=marex@denx.de \
--cc=miquel.raynal@bootlin.com \
--cc=mkorpershoek@baylibre.com \
--cc=samuel@sholland.org \
--cc=seanga2@gmail.com \
--cc=sjg@chromium.org \
--cc=u-boot@lists.denx.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