mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Zhang Jiaming <jiaming@nfschina.com>
To: tsbogend@alpha.franken.de
Cc: rdunlap@infradead.org, linux-mips@vger.kernel.org,
	linux-kernel@vger.kernel.org, liqiong@nfschina.com,
	renyu@nfschina.com, Zhang Jiaming <jiaming@nfschina.com>
Subject: [PATCH] MIPS: Fix 2 typos
Date: Wed, 22 Jun 2022 17:07:13 +0800	[thread overview]
Message-ID: <20220622090713.24370-1-jiaming@nfschina.com> (raw)

Change 'modifed' to 'modified'.
Change 'relys' to 'relays'.

Signed-off-by: Zhang Jiaming <jiaming@nfschina.com>
---
 arch/mips/cavium-octeon/executive/cvmx-helper-board.c | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/arch/mips/cavium-octeon/executive/cvmx-helper-board.c b/arch/mips/cavium-octeon/executive/cvmx-helper-board.c
index 1daa0c6b6f4e..82c51f015ea3 100644
--- 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
+ * data to determine board types and revisions. It relays on the
  * fact that every Octeon board receives a unique board type
  * enumeration from the bootloader.
  *
-- 
2.25.1


             reply	other threads:[~2022-06-22  9:09 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-22  9:07 Zhang Jiaming [this message]
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

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=20220622090713.24370-1-jiaming@nfschina.com \
    --to=jiaming@nfschina.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mips@vger.kernel.org \
    --cc=liqiong@nfschina.com \
    --cc=rdunlap@infradead.org \
    --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®