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, evan@rivosinc.com,
conor.dooley@microchip.com, apatel@ventanamicro.com,
lkp@intel.com
Subject: Re: [PATCH -next] RISC-V: hwprobe: Always use u64 for extension bits
Date: Thu, 07 Dec 2023 15:20:25 +0000 [thread overview]
Message-ID: <170196242578.12999.9102455009815315888.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20231101141908.192198-2-ajones@ventanamicro.com>
Hello:
This patch was applied to riscv/linux.git (fixes)
by Palmer Dabbelt <palmer@rivosinc.com>:
On Wed, 1 Nov 2023 15:19:09 +0100 you wrote:
> Extensions are getting added quickly and their hwprobe bits will soon
> exceed 31 (which pair values accommodate, since they're of type u64).
> However, in one tree, where a bunch of extensions got merged prior to
> zicboz, zicboz already got pushed to bit 32. Pushing it exposed a
> 32-bit compilation bug, since unsigned long was used instead of u64.
>
> Reported-by: kernel test robot <lkp@intel.com>
> Closes: https://lore.kernel.org/oe-kbuild-all/202310311801.hxduISrr-lkp@intel.com/
> Fixes: 9c7646d5ffd2 ("RISC-V: hwprobe: Expose Zicboz extension and its block size")
> Signed-off-by: Andrew Jones <ajones@ventanamicro.com>
>
> [...]
Here is the summary with links:
- [-next] RISC-V: hwprobe: Always use u64 for extension bits
https://git.kernel.org/riscv/c/777c0d761be7
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:[~2023-12-07 15:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-01 14:19 [PATCH -next] RISC-V: hwprobe: Always use u64 for extension bits Andrew Jones
2023-12-07 15:20 ` 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=170196242578.12999.9102455009815315888.git-patchwork-notify@kernel.org \
--to=patchwork-bot+linux-riscv@kernel.org \
--cc=ajones@ventanamicro.com \
--cc=aou@eecs.berkeley.edu \
--cc=apatel@ventanamicro.com \
--cc=conor.dooley@microchip.com \
--cc=evan@rivosinc.com \
--cc=linux-riscv@lists.infradead.org \
--cc=lkp@intel.com \
--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 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.