From: sashiko-bot@kernel.org
To: "Anup Patel" <anup.patel@oss.qualcomm.com>
Cc: linux-clk@vger.kernel.org
Subject: Re: [PATCH 1/4] RISC-V: Move common MPXY helper routines to arch/riscv
Date: Wed, 30 Sep 2026 15:30:48 +0000 [thread overview]
Message-ID: <20260930153049.1FF161F00893@smtp.kernel.org> (raw)
In-Reply-To: <20260930150213.799245-2-anup.patel@oss.qualcomm.com>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Low] build: missing static inline on sbi_mpxy stub functions
--
commit ca97cea8474e30458386eddc230906510a535e88
Author: Anup Patel <anup.patel@oss.qualcomm.com>
RISC-V: Move common MPXY helper routines to arch/riscv
This commit moves the common MPXY helper routines and MPXY shared memory
management from the Linux SBI MPXY mailbox driver into arch/riscv. This
allows the kernel to directly perform SBI MPXY calls and share memory with
the mailbox driver when the Linux mailbox channel instance is unavailable.
> diff --git a/arch/riscv/include/asm/sbi.h b/arch/riscv/include/asm/sbi.h
> index 5725e0ca4dda3..c41e1af31a45f 100644
> --- a/arch/riscv/include/asm/sbi.h
> +++ b/arch/riscv/include/asm/sbi.h
[ ... ]
> @@ -685,7 +716,58 @@ int sbi_debug_console_read(char *bytes, unsigned int num_bytes);
>
> #else /* CONFIG_RISCV_SBI */
> static inline int sbi_remote_fence_i(const struct cpumask *cpu_mask) { return -1; }
[ ... ]
> +static inline int sbi_mpxy_get_channel_ids(u32 channel_count, u32 *channel_ids)
> +{
> + return -ENODEV;
> +}
> +
> +int sbi_mpxy_read_attrs(u32 channel_id, u32 base_attrid, u32 attr_count,
> + u32 *attrs_buf)
> +{
> + return -ENODEV;
> +}
[Severity: Low]
Does this omitted static inline modifier break compilation when
CONFIG_RISCV_SBI=n?
Without static inline on sbi_mpxy_read_attrs (and the other stub functions
below it), every C file including this header will generate a global symbol
for the function. This typically leads to multiple definition linker errors
across different translation units.
> +
> +int sbi_mpxy_write_attrs(u32 channel_id, u32 base_attrid, u32 attr_count,
> + u32 *attrs_buf)
> +{
> + return -ENODEV;
> +}
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260930150213.799245-1-anup.patel@oss.qualcomm.com?part=1
next prev parent reply other threads:[~2026-09-30 15:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-30 15:02 [PATCH 0/4] Parallel message send using SBI MPXY Anup Patel
2026-09-30 15:02 ` [PATCH 1/4] RISC-V: Move common MPXY helper routines to arch/riscv Anup Patel
2026-09-30 15:30 ` sashiko-bot [this message]
2026-09-30 15:02 ` [PATCH 2/4] RISC-V: Factor-out per-hart MPXY shared-memory acquisition Anup Patel
2026-09-30 15:02 ` [PATCH 3/4] mailbox: add direct synchronous send support Anup Patel
2026-09-30 15:02 ` [PATCH 4/4] mailbox: riscv-sbi-mpxy: Move to send_data_sync() for sending messages Anup Patel
2026-09-30 15:38 ` sashiko-bot
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=20260930153049.1FF161F00893@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=anup.patel@oss.qualcomm.com \
--cc=linux-clk@vger.kernel.org \
--cc=sashiko-reviews@lists.linux.dev \
/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