From: Michal Simek <michal.simek@amd.com>
To: linux-kernel@vger.kernel.org, monstr@monstr.eu,
michal.simek@xilinx.com, git@xilinx.com,
quic_jjohnson@quicinc.com
Cc: Appana Durga Kedareswara rao <appana.durga.rao@xilinx.com>
Subject: Re: [PATCH] microblaze: Export xmb_manager functions
Date: Mon, 29 Jul 2024 07:43:32 +0200 [thread overview]
Message-ID: <b7d2d3e2-5c24-4dda-9f6b-60d8f83d2fdc@amd.com> (raw)
In-Reply-To: <e322dbbbde0feef83f44304ea13249d365d1dc5f.1718799090.git.michal.simek@amd.com>
On 6/19/24 14:11, Michal Simek wrote:
> When TMR_MANAGER is enabled as module there is a need to export functions
> which are present in architecture code.
>
> It has been found by running:
> make W=1 C=1 allmodconfig
> sed -i -e 's/WERROR=y/WERROR=n/g' .config
> make C=1 W=1
>
> which errors out like this:
> ERROR: modpost: "xmb_manager_register" [drivers/misc/xilinx_tmr_manager.ko] undefined!
> ERROR: modpost: "xmb_inject_err" [drivers/misc/xilinx_tmr_inject.ko] undefined!
>
> Fixes: a5e3aaa654c1 ("microblaze: Add xmb_manager_register function")
> Reported-by: Jeff Johnson <quic_jjohnson@quicinc.com>
> Signed-off-by: Michal Simek <michal.simek@amd.com>
> ---
>
> arch/microblaze/kernel/microblaze_ksyms.c | 10 ++++++++++
> 1 file changed, 10 insertions(+)
>
> diff --git a/arch/microblaze/kernel/microblaze_ksyms.c b/arch/microblaze/kernel/microblaze_ksyms.c
> index c892e173ec99..a8553f54152b 100644
> --- a/arch/microblaze/kernel/microblaze_ksyms.c
> +++ b/arch/microblaze/kernel/microblaze_ksyms.c
> @@ -16,6 +16,7 @@
> #include <asm/page.h>
> #include <linux/ftrace.h>
> #include <linux/uaccess.h>
> +#include <asm/xilinx_mb_manager.h>
>
> #ifdef CONFIG_FUNCTION_TRACER
> extern void _mcount(void);
> @@ -46,3 +47,12 @@ extern void __udivsi3(void);
> EXPORT_SYMBOL(__udivsi3);
> extern void __umodsi3(void);
> EXPORT_SYMBOL(__umodsi3);
> +
> +#ifdef CONFIG_MB_MANAGER
> +extern void xmb_manager_register(uintptr_t phys_baseaddr, u32 cr_val,
> + void (*callback)(void *data),
> + void *priv, void (*reset_callback)(void *data));
> +EXPORT_SYMBOL(xmb_manager_register);
> +extern asmlinkage void xmb_inject_err(void);
> +EXPORT_SYMBOL(xmb_inject_err);
> +#endif
Applied.
M
prev parent reply other threads:[~2024-07-29 5:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-19 12:11 Michal Simek
2024-07-29 5:43 ` Michal Simek [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=b7d2d3e2-5c24-4dda-9f6b-60d8f83d2fdc@amd.com \
--to=michal.simek@amd.com \
--cc=appana.durga.rao@xilinx.com \
--cc=git@xilinx.com \
--cc=linux-kernel@vger.kernel.org \
--cc=michal.simek@xilinx.com \
--cc=monstr@monstr.eu \
--cc=quic_jjohnson@quicinc.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
all inboxes | Powered by JetHome®