diff options
author | Bin Meng <bmeng.cn@gmail.com> | 2016-02-05 19:30:11 -0800 |
---|---|---|
committer | Anatolij Gustschin <agust@denx.de> | 2016-02-06 12:00:59 +0100 |
commit | a187559e3d586891c917279044c5386d1b2adc6e (patch) | |
tree | 8d50525d0381f28cd41f86e6d8f42ad47d26063e /drivers/net/fsl-mc | |
parent | 94985cc9d3d7ed991ca8b2627d5894df5ea68f49 (diff) |
Use correct spelling of "U-Boot"
Correct spelling of "U-Boot" shall be used in all written text
(documentation, comments in source files etc.).
Signed-off-by: Bin Meng <bmeng.cn@gmail.com>
Reviewed-by: Heiko Schocher <hs@denx.de>
Reviewed-by: Simon Glass <sjg@chromium.org>
Reviewed-by: Minkyu Kang <mk7.kang@samsung.com>
Diffstat (limited to 'drivers/net/fsl-mc')
-rw-r--r-- | drivers/net/fsl-mc/mc.c | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/drivers/net/fsl-mc/mc.c b/drivers/net/fsl-mc/mc.c index fdbd584186..53c4966c33 100644 --- a/drivers/net/fsl-mc/mc.c +++ b/drivers/net/fsl-mc/mc.c @@ -455,7 +455,7 @@ int mc_init(u64 mc_fw_addr, u64 mc_dpc_addr) /* * Management Complex cores should be held at reset out of POR. - * U-boot should be the first software to touch MC. To be safe, + * U-Boot should be the first software to touch MC. To be safe, * we reset all cores again by setting GCR1 to 0. It doesn't do * anything if they are held at reset. After we setup the firmware * we kick off MC by deasserting the reset bit for core 0, and |