From: Guo Ren <guoren@kernel.org>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: Masanari Iida <standby24x7@gmail.com>,
linux-csky@vger.kernel.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH/v2] csky: Fix typos in Kconfig
Date: Fri, 8 Jan 2021 00:24:36 +0800 [thread overview]
Message-ID: <CAJF2gTQp6EuodAfFjtZZCdBT-nq87RJtuVjco9PkvF1PyimWGQ@mail.gmail.com> (raw)
In-Reply-To: <9de77ea7-c7cd-6235-30f3-50e12fa2d8fe@infradead.org>
Thx, looks good to me.
On Thu, Jan 7, 2021 at 12:23 AM Randy Dunlap <rdunlap@infradead.org> wrote:
>
> On 1/6/21 2:04 AM, Masanari Iida wrote:
> > This patch fixes some spelling typos in Kconfig.
> >
> > Signed-off-by: Masanari Iida <standby24x7@gmail.com>
> > ---
> > arch/csky/Kconfig | 6 +++---
> > 1 file changed, 3 insertions(+), 3 deletions(-)
> >
> > diff --git a/arch/csky/Kconfig b/arch/csky/Kconfig
> > index 7f1721101ea0..e6ddca10e3ee 100644
> > --- a/arch/csky/Kconfig
> > +++ b/arch/csky/Kconfig
> > @@ -243,9 +243,9 @@ menuconfig HAVE_TCM
> > bool "Tightly-Coupled/Sram Memory"
> > select GENERIC_ALLOCATOR
> > help
> > - The implementation are not only used by TCM (Tightly-Coupled Meory)
> > - but also used by sram on SOC bus. It follow existed linux tcm
> > - software interface, so that old tcm application codes could be
> > + The implementation is not only used by TCM (Tightly-Coupled Memory)
> > + but also used by SRAM on SOC bus. It follows the existing Linux TCM
> > + software interface, so that old TCM application codes could be
> > re-used directly.
> >
> > if HAVE_TCM
> >
>
> LGTM. Thanks.
> Reviewed-by: Randy Dunlap <rdunlap@infradead.org>
>
> --
> ~Randy
--
Best Regards
Guo Ren
ML: https://lore.kernel.org/linux-csky/
prev parent reply other threads:[~2021-01-07 16:25 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
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 [this message]
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=CAJF2gTQp6EuodAfFjtZZCdBT-nq87RJtuVjco9PkvF1PyimWGQ@mail.gmail.com \
--to=guoren@kernel.org \
--cc=linux-csky@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rdunlap@infradead.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).