All of lore.kernel.org
 help / color / mirror / Atom feed
From: Xiang wangx <wangxiang@cdjrlc.com>
To: jonas@southpole.se
Cc: stefan.kristiansson@saunalahti.fi, shorne@gmail.com,
	openrisc@lists.librecores.org, linux-kernel@vger.kernel.org,
	Xiang wangx <wangxiang@cdjrlc.com>
Subject: [PATCH] openrisc: Fix syntax errors in comments
Date: Thu,  2 Jun 2022 16:53:50 +0800	[thread overview]
Message-ID: <20220602085350.12741-1-wangxiang@cdjrlc.com> (raw)

Delete the redundant word 'the'.

Signed-off-by: Xiang wangx <wangxiang@cdjrlc.com>
---
 arch/openrisc/kernel/unwinder.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/arch/openrisc/kernel/unwinder.c b/arch/openrisc/kernel/unwinder.c
index 8ae15c2c1845..c6ad6f867a6a 100644
--- a/arch/openrisc/kernel/unwinder.c
+++ b/arch/openrisc/kernel/unwinder.c
@@ -25,7 +25,7 @@ struct or1k_frameinfo {
 /*
  * Verify a frameinfo structure.  The return address should be a valid text
  * address.  The frame pointer may be null if its the last frame, otherwise
- * the frame pointer should point to a location in the stack after the the
+ * the frame pointer should point to a location in the stack after the
  * top of the next frame up.
  */
 static inline int or1k_frameinfo_valid(struct or1k_frameinfo *frameinfo)
-- 
2.36.1


WARNING: multiple messages have this Message-ID (diff)
From: Xiang wangx <wangxiang@cdjrlc.com>
To: jonas@southpole.se
Cc: Xiang wangx <wangxiang@cdjrlc.com>,
	openrisc@lists.librecores.org, linux-kernel@vger.kernel.org
Subject: [PATCH] openrisc: Fix syntax errors in comments
Date: Thu,  2 Jun 2022 16:53:50 +0800	[thread overview]
Message-ID: <20220602085350.12741-1-wangxiang@cdjrlc.com> (raw)

Delete the redundant word 'the'.

Signed-off-by: Xiang wangx <wangxiang@cdjrlc.com>
---
 arch/openrisc/kernel/unwinder.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/arch/openrisc/kernel/unwinder.c b/arch/openrisc/kernel/unwinder.c
index 8ae15c2c1845..c6ad6f867a6a 100644
--- a/arch/openrisc/kernel/unwinder.c
+++ b/arch/openrisc/kernel/unwinder.c
@@ -25,7 +25,7 @@ struct or1k_frameinfo {
 /*
  * Verify a frameinfo structure.  The return address should be a valid text
  * address.  The frame pointer may be null if its the last frame, otherwise
- * the frame pointer should point to a location in the stack after the the
+ * the frame pointer should point to a location in the stack after the
  * top of the next frame up.
  */
 static inline int or1k_frameinfo_valid(struct or1k_frameinfo *frameinfo)
-- 
2.36.1


             reply	other threads:[~2022-06-02  8:55 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-02  8:53 Xiang wangx [this message]
2022-06-02  8:53 ` [PATCH] openrisc: Fix syntax errors in comments Xiang wangx
2022-06-28  0:37 ` Stafford Horne
2022-06-28  0:37   ` Stafford Horne

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=20220602085350.12741-1-wangxiang@cdjrlc.com \
    --to=wangxiang@cdjrlc.com \
    --cc=jonas@southpole.se \
    --cc=linux-kernel@vger.kernel.org \
    --cc=openrisc@lists.librecores.org \
    --cc=shorne@gmail.com \
    --cc=stefan.kristiansson@saunalahti.fi \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.