From: Sean Anderson <seanga2@gmail.com>
To: Mayuresh Chitale <mchitale@ventanamicro.com>,
Ilias Apalodimas <ilias.apalodimas@linaro.org>,
Leo Yu-Chi Liang <ycliang@andestech.com>,
Marek Vasut <marek.vasut+renesas@mailbox.org>,
Shengyu Qu <wiagn233@outlook.com>
Cc: Simon Glass <sjg@chromium.org>,
u-boot@lists.denx.de, Tom Rini <trini@konsulko.com>
Subject: Re: [PATCH v2] fs: Fix SPL build if FS_LOADER is enabled
Date: Thu, 16 Nov 2023 13:39:11 -0500 [thread overview]
Message-ID: <2ab0dd14-3bcb-e092-a1f1-13bde2d7b08e@gmail.com> (raw)
In-Reply-To: <20231116171612.143910-1-mchitale@ventanamicro.com>
On 11/16/23 12:16, Mayuresh Chitale wrote:
> If FS_LOADER is enabled for the SPL then the build fails with the error:
>
> fs/fs.o:(.data.rel.fstypes+0x128):
> undefined reference to `smh_fs_set_blk_dev'
> fs/fs.o:(.data.rel.fstypes+0x140):
> undefined reference to `smh_fs_size'
> fs/fs.o:(.data.rel.fstypes+0x148):
> undefined reference to `smh_fs_read'
> fs/fs.o:(.data.rel.fstypes+0x150):
> undefined reference to `smh_fs_write'
>
> Fix the error by populating the semihosting entry in the fs_types array
> only for non-SPL builds.
>
> Signed-off-by: Mayuresh Chitale <mchitale@ventanamicro.com>
> ---
> Changes in v2:
> - Use CONFIG_IS_ENABLED instead of CONFIG_SPL_BUILD
>
> fs/fs.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/fs/fs.c b/fs/fs.c
> index 4cb4310c9c..5c27ae2fe1 100644
> --- a/fs/fs.c
> +++ b/fs/fs.c
> @@ -256,7 +256,7 @@ static struct fstype_info fstypes[] = {
> .ln = fs_ln_unsupported,
> },
> #endif
> -#ifdef CONFIG_SEMIHOSTING
> +#if CONFIG_IS_ENABLED(SEMIHOSTING)
> {
> .fstype = FS_TYPE_SEMIHOSTING,
> .name = "semihosting",
Reviewed-by: Sean Anderson <seanga2@gmail.com>
next prev parent reply other threads:[~2023-11-16 18:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-16 17:16 [PATCH v2] fs: Fix SPL build if FS_LOADER is enabled Mayuresh Chitale
2023-11-16 18:33 ` Tom Rini
2023-11-16 18:39 ` Sean Anderson [this message]
2023-12-21 21:06 ` 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=2ab0dd14-3bcb-e092-a1f1-13bde2d7b08e@gmail.com \
--to=seanga2@gmail.com \
--cc=ilias.apalodimas@linaro.org \
--cc=marek.vasut+renesas@mailbox.org \
--cc=mchitale@ventanamicro.com \
--cc=sjg@chromium.org \
--cc=trini@konsulko.com \
--cc=u-boot@lists.denx.de \
--cc=wiagn233@outlook.com \
--cc=ycliang@andestech.com \
/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