From: Randy Dunlap <rdunlap@infradead.org>
To: Joe Perches <joe@perches.com>,
Zhang Jiaming <jiaming@nfschina.com>,
tsbogend@alpha.franken.de
Cc: linux-mips@vger.kernel.org, linux-kernel@vger.kernel.org,
liqiong@nfschina.com, renyu@nfschina.com
Subject: Re: [PATCH] MIPS: Fix 2 typos
Date: Wed, 22 Jun 2022 19:59:26 -0700 [thread overview]
Message-ID: <f174fa2c-40b8-af76-812f-0f3bb680b2da@infradead.org> (raw)
In-Reply-To: <37d560bc5267408eb9cc806339025418094cf5bb.camel@perches.com>
On 6/22/22 07:46, Joe Perches wrote:
> On Wed, 2022-06-22 at 07:28 -0700, Randy Dunlap wrote:
>> On 6/22/22 02:07, Zhang Jiaming wrote:
>>> Change 'modifed' to 'modified'.
>>> Change 'relys' to 'relays'.
> []
>>> diff --git a/arch/mips/cavium-octeon/executive/cvmx-helper-board.c b/arch/mips/cavium-octeon/executive/cvmx-helper-board.c
> []
>>> @@ -282,9 +282,9 @@ union cvmx_helper_link_info __cvmx_helper_board_link_get(int ipd_port)
>>> * support and should return the number of actual ports on the
>>> * board.
>>> *
>>> - * This function must be modifed for every new Octeon board.
>>> + * This function must be modified for every new Octeon board.
>>> * Internally it uses switch statements based on the cvmx_sysinfo
>>> - * data to determine board types and revisions. It relys on the
>>
>> relies
>>
>> But it would be better to restrict this barrage (or swarm) of patches
>> to Kconfig help text problems and/or strings that are printed to users.
>
> I believe fixing typos isn't a particular problem and is
> overall rather a good thing.
OK, I can agree with that.
> Though backporting these patches would be silly.
Ack.
--
~Randy
prev parent reply other threads:[~2022-06-23 3:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-22 9:07 Zhang Jiaming
2022-06-22 9:24 ` Sergei Shtylyov
2022-06-22 10:27 ` [PATCH v2] MIPS: Fix some typos Zhang Jiaming
2022-07-05 10:25 ` Thomas Bogendoerfer
2022-06-22 14:28 ` [PATCH] MIPS: Fix 2 typos Randy Dunlap
2022-06-22 14:46 ` Joe Perches
2022-06-23 2:59 ` Randy Dunlap [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=f174fa2c-40b8-af76-812f-0f3bb680b2da@infradead.org \
--to=rdunlap@infradead.org \
--cc=jiaming@nfschina.com \
--cc=joe@perches.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=liqiong@nfschina.com \
--cc=renyu@nfschina.com \
--cc=tsbogend@alpha.franken.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
all inboxes | Powered by JetHome®