From: sbabic@denx.de
To: Marek Vasut <marex@denx.de>,u-boot@lists.denx.de
Subject: [PATCH v2 1/4] spl: mmc: Introduce proper layering for spl_mmc_get_uboot_raw_sector()
Date: Wed, 18 Oct 2023 20:17:52 +0200 (CEST) [thread overview]
Message-ID: <20231018181753.CE31E8701C@phobos.denx.de> (raw)
> Introduce two new weak functions, arch_spl_mmc_get_uboot_raw_sector() and
> board_spl_mmc_get_uboot_raw_sector(), each of which can be overridden at
> a matching level, that is arch/ and board/ , in addition to the existing
> weak function spl_mmc_get_uboot_raw_sector().
> This way, architecture code can define a default architecture specific
> implementation of arch_spl_mmc_get_uboot_raw_sector(), while the board
> code can override that using board_spl_mmc_get_uboot_raw_sector() which
> takes precedence over the architecture code. In some sort of unlikely
> special case where code has to take precedence over board code too, the
> spl_mmc_get_uboot_raw_sector() is still left out to be a weak function,
> but it should be unlikely that this is ever needed to be overridden.
> Signed-off-by: Marek Vasut <marex@denx.de>
Applied to u-boot-imx, master, thanks !
Best regards,
Stefano Babic
--
=====================================================================
DENX Software Engineering GmbH, Managing Director: Erika Unter
HRB 165235 Munich, Office: Kirchenstr.5, 82194 Groebenzell, Germany
Phone: +49-8142-66989-53 Fax: +49-8142-66989-80 Email: sbabic@denx.de
=====================================================================
next reply other threads:[~2023-10-18 18:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-18 18:17 sbabic [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-10-16 16:16 [PATCH v2 1/4] spl: mmc: Introduce proper layering for spl_mmc_get_uboot_raw_sector() Marek Vasut
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=20231018181753.CE31E8701C@phobos.denx.de \
--to=sbabic@denx.de \
--cc=marex@denx.de \
--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