* [PATCH] openrisc: Fix syntax errors in comments
@ 2022-06-02 8:53 Xiang wangx
2022-06-28 0:37 ` Stafford Horne
0 siblings, 1 reply; 2+ messages in thread
From: Xiang wangx @ 2022-06-02 8:53 UTC (permalink / raw)
To: jonas; +Cc: Xiang wangx, openrisc, linux-kernel
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
^ permalink raw reply related [flat|nested] 2+ messages in thread* Re: [PATCH] openrisc: Fix syntax errors in comments
2022-06-02 8:53 [PATCH] openrisc: Fix syntax errors in comments Xiang wangx
@ 2022-06-28 0:37 ` Stafford Horne
0 siblings, 0 replies; 2+ messages in thread
From: Stafford Horne @ 2022-06-28 0:37 UTC (permalink / raw)
To: Xiang wangx; +Cc: jonas, openrisc, linux-kernel
On Thu, Jun 02, 2022 at 04:53:50PM +0800, Xiang wangx wrote:
> 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
This looks good to me, I will queue with 5.19 fixes.
-Stafford
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2022-06-28 0:37 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2022-06-02 8:53 [PATCH] openrisc: Fix syntax errors in comments Xiang wangx
2022-06-28 0:37 ` Stafford Horne
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox