From: Yangyu Chen <cyy@cyyself.name>
To: linux-riscv@lists.infradead.org
Cc: "Elliott Hughes" <enh@google.com>,
"Charlie Jenkins" <charlie@rivosinc.com>,
"Jonathan Corbet" <corbet@lwn.net>,
"Paul Walmsley" <paul.walmsley@sifive.com>,
"Palmer Dabbelt" <palmer@dabbelt.com>,
"Evan Green" <evan@rivosinc.com>,
"Clément Léger" <cleger@rivosinc.com>,
"Conor Dooley" <conor.dooley@microchip.com>,
"Andrew Jones" <ajones@ventanamicro.com>,
linux-kernel@vger.kernel.org, linux-doc@vger.kernel.org,
"Yangyu Chen" <cyy@cyyself.name>
Subject: [PATCH 0/2] docs: riscv: Some clarifies on hwprobe misaligned performance
Date: Sat, 18 May 2024 23:57:45 +0800 [thread overview]
Message-ID: <tencent_9D721BDDF88C04DBB5151D57711D62524209@qq.com> (raw)
This patchset clarifies some unclear things about hwprobe's misaligned
performance. Including:
- hwprobe misaligned performance is only applied to scalar from patch [1]
- The defined keys of RISCV_HWPROBE_MISALIGNED_* are values not bitmasks
I cherry-picked [1] rather than write dependency because the original patch
was submitted with a line wrapped to 80 characters. We can't directly apply
that patch using `git am.`
[1] https://lore.kernel.org/linux-riscv/CAJgzZorn5anPH8dVPqvjVWmLKqTi5bkLDR=FH-ZAcdXFnNe8Eg@mail.gmail.com/
Yangyu Chen (1):
docs: riscv: hwprobe: Clarify misaligned keys are values not bitmasks
enh (1):
docs: riscv: Clarify risc-v hwprobe RISCV_HWPROBE_MISALIGNED_* docs.
Documentation/arch/riscv/hwprobe.rst | 31 ++++++++++++++++------------
1 file changed, 18 insertions(+), 13 deletions(-)
--
2.43.0
next reply other threads:[~2024-05-18 15:58 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-18 15:57 Yangyu Chen [this message]
2024-05-18 16:00 ` [PATCH 1/2] docs: riscv: Clarify risc-v hwprobe RISCV_HWPROBE_MISALIGNED_* docs Yangyu Chen
2024-05-18 16:00 ` [PATCH 2/2] docs: riscv: hwprobe: Clarify misaligned keys are values not bitmasks Yangyu Chen
2024-05-21 18:36 ` Evan Green
2024-05-21 21:13 ` Charlie Jenkins
2024-05-22 7:26 ` Andrew Jones
2024-05-23 21:17 ` Charlie Jenkins
2024-05-24 1:08 ` Evan Green
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=tencent_9D721BDDF88C04DBB5151D57711D62524209@qq.com \
--to=cyy@cyyself.name \
--cc=ajones@ventanamicro.com \
--cc=charlie@rivosinc.com \
--cc=cleger@rivosinc.com \
--cc=conor.dooley@microchip.com \
--cc=corbet@lwn.net \
--cc=enh@google.com \
--cc=evan@rivosinc.com \
--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