From: yeongjun Kim <iam.yeongjunkim@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] fixing typo error in README file. CPU15 -> CP15
Date: Tue, 19 Jul 2016 22:17:05 +0900 [thread overview]
Message-ID: <20160719131705.GA5807@gmail.com> (raw)
Signed-off-by: yeongjun Kim <iam.yeongjunkim@gmail.com>
---
README | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/README b/README
index 3c3b699..8887cf5 100644
--- a/README
+++ b/README
@@ -4806,7 +4806,7 @@ Low Level (hardware related) configuration options:
- CONFIG_SKIP_LOWLEVEL_INIT_ONLY
[ARM926EJ-S only] This allows just the call to lowlevel_init()
- to be skipped. The normal CPU15 init (such as enabling the
+ to be skipped. The normal CP15 init (such as enabling the
instruction cache) is still performed.
- CONFIG_SPL_BUILD
--
1.9.1
next reply other threads:[~2016-07-19 13:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-19 13:17 yeongjun Kim [this message]
[not found] <CGME20160720135629epcas1p192ae85343fb281fb59b38ffdef73e00d@epcas1p1.samsung.com>
2016-07-20 13:56 ` [U-Boot] [PATCH] fixing typo error in README file. CPU15 -> CP15 yeongjun Kim
2016-07-21 13:34 ` Jaehoon Chung
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=20160719131705.GA5807@gmail.com \
--to=iam.yeongjunkim@gmail.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