public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Jaehoon Chung <jh80.chung@samsung.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] fixing typo error in README file. CPU15 -> CP15
Date: Thu, 21 Jul 2016 22:34:53 +0900	[thread overview]
Message-ID: <5790CF7D.3030909@samsung.com> (raw)
In-Reply-To: <20160720135612.GA6113@gmail.com>

Hi Yeongjun,

On 07/20/2016 10:56 PM, yeongjun Kim wrote:
> It looks typo error. 

It's not error..Just typo.
Subject should be add the prefix "README: fix the typo..."

> Not CPU15, CP15(CoProcessor15)
> 	
> Signed-off-by: yeongjun Kim <iam.yeongjunkim@gmail.com>
> ---

If you send the patch V2, add the changelog at here.
Write the changelog what is changed from previous patch.

But you're right, it's typo. 
I added the Simon as Author who sent patch.

Best Regards,
Jaehoon Chung

>  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
> 

  reply	other threads:[~2016-07-21 13:34 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [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 [this message]
2016-07-23  0:13   ` [U-Boot] " Tom Rini
2016-07-19 13:17 [U-Boot] [PATCH] " yeongjun Kim

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=5790CF7D.3030909@samsung.com \
    --to=jh80.chung@samsung.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