From: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
To: Jason Wang <wangborong@cdjrlc.com>
Cc: zajec5@gmail.com, hauke@hauke-m.de, linux-mips@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] MIPS: Fix comment typo
Date: Sat, 30 Jul 2022 11:03:22 +0200 [thread overview]
Message-ID: <20220730090322.GC4620@alpha.franken.de> (raw)
In-Reply-To: <20220716040119.31221-1-wangborong@cdjrlc.com>
On Sat, Jul 16, 2022 at 12:01:19PM +0800, Jason Wang wrote:
> Fix the typo `s/that that/than that/' in line 72.
>
> Signed-off-by: Jason Wang <wangborong@cdjrlc.com>
> ---
> arch/mips/bcm47xx/prom.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/arch/mips/bcm47xx/prom.c b/arch/mips/bcm47xx/prom.c
> index 0a63721d0fbf..ab203e66ba0d 100644
> --- a/arch/mips/bcm47xx/prom.c
> +++ b/arch/mips/bcm47xx/prom.c
> @@ -69,7 +69,7 @@ static __init void prom_init_mem(void)
> * call them at the beginning of the boot.
> *
> * BCM47XX uses 128MB for addressing the ram, if the system contains
> - * less that that amount of ram it remaps the ram more often into the
> + * less than that amount of ram it remaps the ram more often into the
> * available space.
> */
>
> --
> 2.35.1
applied to mips-next.
Thomas.
--
Crap can work. Given enough thrust pigs will fly, but it's not necessarily a
good idea. [ RFC1925, 2.3 ]
next prev parent reply other threads:[~2022-07-30 9:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-16 4:01 [PATCH] MIPS: Fix comment typo Jason Wang
2022-07-30 9:03 ` Thomas Bogendoerfer [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-08-11 12:14 Jason Wang
2022-09-12 13:41 ` Thomas Bogendoerfer
2022-07-15 4:39 Jason Wang
2022-07-18 15:06 ` Sergey Shtylyov
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=20220730090322.GC4620@alpha.franken.de \
--to=tsbogend@alpha.franken.de \
--cc=hauke@hauke-m.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=wangborong@cdjrlc.com \
--cc=zajec5@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