public inbox for linux-riscv@lists.infradead.org
 help / color / mirror / Atom feed
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
Subject: Re: [PATCH] RISC-V: selftests: cbo: Ensure asm operands match constraints
Date: Sat, 20 Jan 2024 21:09:59 +0000	[thread overview]
Message-ID: <170578499925.24348.4221862120348193500.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240117130933.57514-2-ajones@ventanamicro.com>

Hello:

This patch was applied to riscv/linux.git (fixes)
by Palmer Dabbelt <palmer@rivosinc.com>:

On Wed, 17 Jan 2024 14:09:34 +0100 you wrote:
> The 'i' constraint expects a constant operand, which fn and its
> constant derivative MK_CBO(fn) are, but passing fn through a function
> as a parameter and using a local variable for MK_CBO(fn) allow the
> compiler to lose sight of that when no optimization is done. Use
> a macro instead of a function and skip the local variable to ensure
> the compiler uses constants, matching the asm constraints.
> 
> [...]

Here is the summary with links:
  - RISC-V: selftests: cbo: Ensure asm operands match constraints
    https://git.kernel.org/riscv/c/0de65288d75f

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

      reply	other threads:[~2024-01-20 21:10 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-17 13:09 [PATCH] RISC-V: selftests: cbo: Ensure asm operands match constraints Andrew Jones
2024-01-20 21:09 ` 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=170578499925.24348.4221862120348193500.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 \
    /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