RISC-V: Fix sparse warnings
Get series with b4
b4 am [email protected]Versions newest first
- v1 Latest3 patches 0 repliesNew
Patches in v1 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/3 | RISC-V: paravirt: steal_time should be staticarch/ | +1 | 1 reply | |
| 2/3 | RISC-V: paravirt: Use correct restricted typesarch/ | +2 | 1 reply | |
| 3/3 | RISC-V: KVM: Use correct restricted typesarch/ | +12 | 1 reply |
Reviews trailers per patch
All 3 patches have a Reviewed-by or Acked-by.
| Patch | Atish Patra |
|---|---|
| 1/3 | R-b |
| 2/3 | R-b |
| 3/3 | R-b |
Trailers given in replies are filled; those carried in the patches from earlier versions are outlined with dashes.
Cover letter [PATCH 0/3] RISC-V: Fix sparse warnings
After the steal-time series was merged, LKP sent me mail with sparse warnings for the lack of using appropriate restricted types and a local variable not being static. This series makes the fixups necessary to appease sparse for 64-bit compiles. Changes to __get_user_8() and __put_user_8() are needed to completely quiet sparse for 32-bit compiles. I'll address those 32-bit sparse warnings separately, since it's not 100% clear how best to approach a couple of them.
Thanks,
drew
Andrew Jones (3):
RISC-V: paravirt: steal_time should be static
RISC-V: paravirt: Use correct restricted types
RISC-V: KVM: Use correct restricted types
arch/riscv/kernel/paravirt.c | 6 +++--- arch/riscv/kvm/vcpu_sbi_sta.c | 20 ++++++++++++-------- 2 files changed, 15 insertions(+), 11 deletions(-)
Signature · 1 line
2.43.0