From: patchwork-bot+linux-riscv@kernel.org
To: Xingyou Chen <rockrush@rockwork.org>
Cc: linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org,
ajones@ventanamicro.com, cleger@rivosinc.com,
aou@eecs.berkeley.edu, palmer@dabbelt.com,
paul.walmsley@sifive.com
Subject: Re: [PATCH] riscv: typo in comment for get_f64_reg
Date: Wed, 22 May 2024 23:51:47 +0000 [thread overview]
Message-ID: <171642190770.9409.8853343046568203839.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240317055556.9449-1-rockrush@rockwork.org>
Hello:
This patch was applied to riscv/linux.git (for-next)
by Palmer Dabbelt <palmer@rivosinc.com>:
On Sun, 17 Mar 2024 13:55:56 +0800 you wrote:
> Signed-off-by: Xingyou Chen <rockrush@rockwork.org>
> ---
> arch/riscv/kernel/fpu.S | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
Here is the summary with links:
- riscv: typo in comment for get_f64_reg
https://git.kernel.org/riscv/c/fca93def4e41
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
WARNING: multiple messages have this Message-ID (diff)
From: patchwork-bot+linux-riscv@kernel.org
To: Xingyou Chen <rockrush@rockwork.org>
Cc: linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org,
ajones@ventanamicro.com, cleger@rivosinc.com,
aou@eecs.berkeley.edu, palmer@dabbelt.com,
paul.walmsley@sifive.com
Subject: Re: [PATCH] riscv: typo in comment for get_f64_reg
Date: Wed, 22 May 2024 23:51:47 +0000 [thread overview]
Message-ID: <171642190770.9409.8853343046568203839.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240317055556.9449-1-rockrush@rockwork.org>
Hello:
This patch was applied to riscv/linux.git (for-next)
by Palmer Dabbelt <palmer@rivosinc.com>:
On Sun, 17 Mar 2024 13:55:56 +0800 you wrote:
> Signed-off-by: Xingyou Chen <rockrush@rockwork.org>
> ---
> arch/riscv/kernel/fpu.S | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
Here is the summary with links:
- riscv: typo in comment for get_f64_reg
https://git.kernel.org/riscv/c/fca93def4e41
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
next prev parent reply other threads:[~2024-05-22 23:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-17 5:55 [PATCH] riscv: typo in comment for get_f64_reg Xingyou Chen
2024-03-17 5:55 ` Xingyou Chen
2024-03-17 6:07 ` Randy Dunlap
2024-03-17 6:07 ` Randy Dunlap
2024-05-22 23:51 ` patchwork-bot+linux-riscv [this message]
2024-05-22 23:51 ` patchwork-bot+linux-riscv
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=171642190770.9409.8853343046568203839.git-patchwork-notify@kernel.org \
--to=patchwork-bot+linux-riscv@kernel.org \
--cc=ajones@ventanamicro.com \
--cc=aou@eecs.berkeley.edu \
--cc=cleger@rivosinc.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=rockrush@rockwork.org \
/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.