From: Andrew F. Davis <afd@ti.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 2/3] env: Fix missed getenv_ulong to env_get_ulong conversion
Date: Wed, 14 Feb 2018 11:53:38 -0600 [thread overview]
Message-ID: <20180214175339.31459-2-afd@ti.com> (raw)
In-Reply-To: <20180214175339.31459-1-afd@ti.com>
This seems to have been missed, possibly due to the inability to
enable TI_SECURE_DEVICE on Keystone2 devices previously.
Fixes: bfebc8c965e4 ("env: Rename getenv_hex(), getenv_yesno(), getenv_ulong()")
Signed-off-by: Andrew F. Davis <afd@ti.com>
---
board/ti/ks2_evm/board_k2g.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/board/ti/ks2_evm/board_k2g.c b/board/ti/ks2_evm/board_k2g.c
index 88df419b10..b9575a8e46 100644
--- a/board/ti/ks2_evm/board_k2g.c
+++ b/board/ti/ks2_evm/board_k2g.c
@@ -376,7 +376,7 @@ int get_num_eth_ports(void)
#ifdef CONFIG_TI_SECURE_DEVICE
void board_pmmc_image_process(ulong pmmc_image, size_t pmmc_size)
{
- int id = getenv_ulong("dev_pmmc", 10, 0);
+ int id = env_get_ulong("dev_pmmc", 10, 0);
int ret;
if (!rproc_is_initialized())
--
2.16.1
next prev parent reply other threads:[~2018-02-14 17:53 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-14 17:53 [U-Boot] [PATCH 1/3] ARM: Kconfig: Move TI_SECURE_DEVICE to a common area Andrew F. Davis
2018-02-14 17:53 ` Andrew F. Davis [this message]
2018-02-15 6:29 ` [U-Boot] [PATCH 2/3] env: Fix missed getenv_ulong to env_get_ulong conversion Lokesh Vutla
2018-02-23 18:03 ` [U-Boot] [U-Boot, " Tom Rini
2018-02-14 17:53 ` [U-Boot] [PATCH 3/3] defconfig: k2x_hs_evm: Re-enable TI_SECURE_DEVICE in HS K2x parts Andrew F. Davis
2018-02-15 6:29 ` Lokesh Vutla
2018-02-23 18:03 ` [U-Boot] [U-Boot, " Tom Rini
2018-02-15 6:29 ` [U-Boot] [PATCH 1/3] ARM: Kconfig: Move TI_SECURE_DEVICE to a common area Lokesh Vutla
2018-02-23 18:03 ` [U-Boot] [U-Boot, " 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=20180214175339.31459-2-afd@ti.com \
--to=afd@ti.com \
--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