linux-csky.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Randy Dunlap <rdunlap@infradead.org>
To: Masanari Iida <standby24x7@gmail.com>,
	guoren@kernel.org, linux-csky@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] csky: Fix a typo in Kconfig
Date: Tue, 5 Jan 2021 13:33:24 -0800	[thread overview]
Message-ID: <ae3672c0-84d1-7ee5-1858-33d119544906@infradead.org> (raw)
In-Reply-To: <20210105134107.217920-1-standby24x7@gmail.com>

Hi,
There's a lot more to do here.  Please see below.

On 1/5/21 5:41 AM, Masanari Iida wrote:
> This patch fixes a spelling typo in Kconfig.
> 
> Signed-off-by: Masanari Iida <standby24x7@gmail.com>
> ---
>  arch/csky/Kconfig | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/arch/csky/Kconfig b/arch/csky/Kconfig
> index 7f1721101ea0..ce680f6e3b4b 100644
> --- a/arch/csky/Kconfig
> +++ b/arch/csky/Kconfig
> @@ -243,7 +243,7 @@ menuconfig HAVE_TCM
>  	bool "Tightly-Coupled/Sram Memory"
>  	select GENERIC_ALLOCATOR
>  	help
> -	  The implementation are not only used by TCM (Tightly-Coupled Meory)
> +	  The implementation are not only used by TCM (Tightly-Coupled Memory)

	                     is not

>  	  but also used by sram on SOC bus. It follow existed linux tcm

	                   SRAM                follows the existing Linux TCM

>  	  software interface, so that old tcm application codes could be

	                                  TCM

>  	  re-used directly.
> 


-- 
~Randy


  reply	other threads:[~2021-01-05 21:34 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-05 13:41 [PATCH] csky: Fix a typo in Kconfig Masanari Iida
2021-01-05 21:33 ` Randy Dunlap [this message]
2021-01-06 10:04   ` [PATCH/v2] csky: Fix typos " Masanari Iida
2021-01-06 16:21     ` Randy Dunlap
2021-01-07 16:24       ` Guo Ren

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=ae3672c0-84d1-7ee5-1858-33d119544906@infradead.org \
    --to=rdunlap@infradead.org \
    --cc=guoren@kernel.org \
    --cc=linux-csky@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=standby24x7@gmail.com \
    /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;
as well as URLs for NNTP newsgroup(s).