linux-doc.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: patchwork-bot+linux-riscv@kernel.org
To: Evan Green <evan@rivosinc.com>
Cc: linux-riscv@lists.infradead.org, palmer@dabbelt.com,
	cyy@cyyself.name, aou@eecs.berkeley.edu, alexghiti@rivosinc.com,
	ajones@ventanamicro.com, andy.chiu@sifive.com,
	anup@brainfault.org, ben.dooks@codethink.co.uk,
	bjorn@rivosinc.com, charlie@rivosinc.com, cleger@rivosinc.com,
	conor.dooley@microchip.com, costa.shul@redhat.com,
	erick.archer@gmx.com, gustavoars@kernel.org, corbet@lwn.net,
	paul.walmsley@sifive.com, linux-doc@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4 0/2] RISC-V: hwprobe: Misaligned scalar perf fix and rename
Date: Thu, 15 Aug 2024 17:50:36 +0000	[thread overview]
Message-ID: <172374423644.2967007.14196195556000349824.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240809214444.3257596-1-evan@rivosinc.com>

Hello:

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

On Fri,  9 Aug 2024 14:44:42 -0700 you wrote:
> The CPUPERF0 hwprobe key was documented and identified in code as
> a bitmask value, but its contents were an enum. This produced
> incorrect behavior in conjunction with the WHICH_CPUS hwprobe flag.
> The first patch in this series fixes the bitmask/enum problem by
> creating a new hwprobe key that returns the same data, but is
> properly described as a value instead of a bitmask. The second patch
> renames the value definitions in preparation for adding vector misaligned
> access info. As of this version, the old defines are kept in place to
> maintain source compatibility with older userspace programs.
> 
> [...]

Here is the summary with links:
  - [v4,1/2] RISC-V: hwprobe: Add MISALIGNED_PERF key
    https://git.kernel.org/riscv/c/c42e2f076769
  - [v4,2/2] RISC-V: hwprobe: Add SCALAR to misaligned perf defines
    https://git.kernel.org/riscv/c/1f5288874de7

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      parent reply	other threads:[~2024-08-15 17:50 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-09 21:44 [PATCH v4 0/2] RISC-V: hwprobe: Misaligned scalar perf fix and rename Evan Green
2024-08-09 21:44 ` [PATCH v4 1/2] RISC-V: hwprobe: Add MISALIGNED_PERF key Evan Green
2024-08-09 21:44 ` [PATCH v4 2/2] RISC-V: hwprobe: Add SCALAR to misaligned perf defines Evan Green
2024-08-09 21:57   ` Charlie Jenkins
2024-08-13 18:03     ` enh
2024-08-15 17:50 ` 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=172374423644.2967007.14196195556000349824.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+linux-riscv@kernel.org \
    --cc=ajones@ventanamicro.com \
    --cc=alexghiti@rivosinc.com \
    --cc=andy.chiu@sifive.com \
    --cc=anup@brainfault.org \
    --cc=aou@eecs.berkeley.edu \
    --cc=ben.dooks@codethink.co.uk \
    --cc=bjorn@rivosinc.com \
    --cc=charlie@rivosinc.com \
    --cc=cleger@rivosinc.com \
    --cc=conor.dooley@microchip.com \
    --cc=corbet@lwn.net \
    --cc=costa.shul@redhat.com \
    --cc=cyy@cyyself.name \
    --cc=erick.archer@gmx.com \
    --cc=evan@rivosinc.com \
    --cc=gustavoars@kernel.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --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;
as well as URLs for NNTP newsgroup(s).