From: patchwork-bot+linux-riscv@kernel.org
To: Andrew Jones <ajones@ventanamicro.com>
Cc: linux-riscv@lists.infradead.org, paul.walmsley@sifive.com,
palmer@dabbelt.com, aou@eecs.berkeley.edu,
cuiyunhui@bytedance.com, woodrow.shen@sifive.com
Subject: Re: [PATCH] RISC-V: selftests: cbo: Ensure asm operands match constraints, take 2
Date: Thu, 25 Apr 2024 23:00:30 +0000 [thread overview]
Message-ID: <171408603070.8761.17857789787379874348.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240322134728.151255-2-ajones@ventanamicro.com>
Hello:
This patch was applied to riscv/linux.git (fixes)
by Palmer Dabbelt <palmer@rivosinc.com>:
On Fri, 22 Mar 2024 14:47:28 +0100 you wrote:
> Commit 0de65288d75f ("RISC-V: selftests: cbo: Ensure asm operands
> match constraints") attempted to ensure MK_CBO() would always
> provide to a compile-time constant when given a constant, but
> cpu_to_le32() isn't necessarily going to do that. Switch to manually
> shifting the bytes, when needed, to finally get this right.
>
> Reported-by: Woodrow Shen <woodrow.shen@sifive.com>
> Closes: https://lore.kernel.org/all/CABquHATcBTUwfLpd9sPObBgNobqQKEAZ2yxk+TWSpyO5xvpXpg@mail.gmail.com/
> Fixes: a29e2a48afe3 ("RISC-V: selftests: Add CBO tests")
> Fixes: 0de65288d75f ("RISC-V: selftests: cbo: Ensure asm operands match constraints")
> Signed-off-by: Andrew Jones <ajones@ventanamicro.com>
>
> [...]
Here is the summary with links:
- RISC-V: selftests: cbo: Ensure asm operands match constraints, take 2
https://git.kernel.org/riscv/c/f6b56df883d4
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
prev parent reply other threads:[~2024-04-25 23:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-22 13:47 [PATCH] RISC-V: selftests: cbo: Ensure asm operands match constraints, take 2 Andrew Jones
2024-04-24 9:41 ` Conor Dooley
2024-04-24 10:33 ` Andrew Jones
2024-04-24 11:05 ` Woodrow Shen
2024-04-25 23:00 ` patchwork-bot+linux-riscv [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=171408603070.8761.17857789787379874348.git-patchwork-notify@kernel.org \
--to=patchwork-bot+linux-riscv@kernel.org \
--cc=ajones@ventanamicro.com \
--cc=aou@eecs.berkeley.edu \
--cc=cuiyunhui@bytedance.com \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=woodrow.shen@sifive.com \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).