From: Brooke Basile <brookebasile@gmail.com>
To: Yun Levi <ppbuk5246@gmail.com>
Cc: Thomas Gleixner <tglx@linutronix.de>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH RESEND] irq: export irq_check_status_bit symbol
Date: Thu, 21 Jan 2021 18:07:22 -1000 [thread overview]
Message-ID: <51edd12f-3200-2498-a088-c9b17b666211@gmail.com> (raw)
In-Reply-To: <CAM7-yPSa8kJkS2xm8w6hCgme7YmUOR8GBrx-kiQuUjGctF2QVw@mail.gmail.com>
On 1/5/21 10:57 PM, Yun Levi wrote:
> Because of the missing export symbol for irq_chekc_status_bit,
> Building arm_spe_pmu.ko is a failure on the modpost step.
>
> Below is an error message I saw:
> ERROR:modpost: "irq_check_status_bit" [drivers/perf/arm_spe_pmu.ko] undefined!
> make[4]: *** [scripts/Makefile.modpost:111: Module.symvers] Error 1
> make[4]: *** Deleting file 'Module.symvers'
> make[3]: *** [Makefile:1396: modules] Error 2
> make[2]: *** [debian/rules:7: build-arch] Error 2
> dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2
> make[1]: *** [scripts/Makefile.package:83: bindeb-pkg] Error 2
>
> Signed-off-by: Levi Yun <ppbuk5246@gmail.com>
> ---
> kernel/irq/manage.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/kernel/irq/manage.c b/kernel/irq/manage.c
> index ab8567f32501..dec3f73e8db9 100644
> --- a/kernel/irq/manage.c
> +++ b/kernel/irq/manage.c
> @@ -2859,3 +2859,4 @@ bool irq_check_status_bit(unsigned int irq,
> unsigned int bitmask)
> rcu_read_unlock();
> return res;
> }
> +EXPORT_SYMBOL_GPL(irq_check_status_bit);
> --
> 2.27.0
>
>
Hi,
I ran into this issue while compiling 5.11-rc4 for my RPi 4B. Applying
this patch fixed the breakage.
Thanks for the fix!
Tested-by: Brooke Basile <brookebasile@gmail.com>
Best,
Brooke Basile
prev parent reply other threads:[~2021-01-22 4:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-06 8:57 Yun Levi
2021-01-22 4:07 ` Brooke Basile [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=51edd12f-3200-2498-a088-c9b17b666211@gmail.com \
--to=brookebasile@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=ppbuk5246@gmail.com \
--cc=tglx@linutronix.de \
/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®