From: Alexandre Ghiti <alexghiti@rivosinc.com>
To: kernel test robot <lkp@intel.com>,
Al Viro <viro@zeniv.linux.org.uk>,
Paul Walmsley <paul.walmsley@sifive.com>,
Palmer Dabbelt <palmer@dabbelt.com>,
Albert Ou <aou@eecs.berkeley.edu>,
Alexandre Ghiti <alex@ghiti.fr>,
Cyril Bur <cyrilbur@tenstorrent.com>,
Jisheng Zhang <jszhang@kernel.org>
Cc: linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org,
Alexandre Ghiti <alexghiti@rivosinc.com>,
stable@vger.kernel.org
Subject: [PATCH 0/2] Fix riscv sparse warnings
Date: Wed, 03 Sep 2025 18:53:07 +0000 [thread overview]
Message-ID: <20250903-dev-alex-sparse_warnings_v1-v1-0-7e6350beb700@rivosinc.com> (raw)
This series simply fixes 2 recently introduced sparse warnings.
Signed-off-by: Alexandre Ghiti <alexghiti@rivosinc.com>
---
Alexandre Ghiti (2):
riscv: Fix sparse warning in __get_user_error()
riscv: Fix sparse warning about different address spaces
arch/riscv/include/asm/uaccess.h | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
---
base-commit: ae9a687664d965b13eeab276111b2f97dd02e090
change-id: 20250903-dev-alex-sparse_warnings_v1-ecb4a333afdd
Best regards,
--
Alexandre Ghiti <alexghiti@rivosinc.com>
next reply other threads:[~2025-09-03 18:53 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-03 18:53 Alexandre Ghiti [this message]
2025-09-03 18:53 ` [PATCH 1/2] riscv: Fix sparse warning in __get_user_error() Alexandre Ghiti
2025-09-04 0:34 ` Cyril Bur
2025-09-04 13:50 ` Clément Léger
2025-09-05 22:14 ` Paul Walmsley
2025-09-20 0:55 ` Paul Walmsley
2025-09-03 18:53 ` [PATCH 2/2] riscv: Fix sparse warning about different address spaces Alexandre Ghiti
2025-09-04 0:42 ` Cyril Bur
2025-09-05 6:29 ` Clément Léger
2025-09-05 22:15 ` Paul Walmsley
2025-09-20 0:55 ` Paul Walmsley
2025-09-17 2:40 ` [PATCH 0/2] Fix riscv sparse warnings patchwork-bot+linux-riscv
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=20250903-dev-alex-sparse_warnings_v1-v1-0-7e6350beb700@rivosinc.com \
--to=alexghiti@rivosinc.com \
--cc=alex@ghiti.fr \
--cc=aou@eecs.berkeley.edu \
--cc=cyrilbur@tenstorrent.com \
--cc=jszhang@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=lkp@intel.com \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=stable@vger.kernel.org \
--cc=viro@zeniv.linux.org.uk \
/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
all inboxes | Powered by JetHome®