From: Catalin Marinas <catalin.marinas@arm.com>
To: Jackie Liu <liu.yun@linux.dev>
Cc: will@kernel.org, mark.rutland@arm.com, suzuki.poulose@arm.com,
linux-arm-kernel@lists.infradead.org, mathieu.poirier@linaro.org
Subject: Re: [PATCH] arm64: export this_cpu_has_cap
Date: Thu, 11 Nov 2021 15:32:41 +0000 [thread overview]
Message-ID: <YY03mbRCW0iMPftm@arm.com> (raw)
In-Reply-To: <20211111032138.2359201-1-liu.yun@linux.dev>
On Thu, Nov 11, 2021 at 11:21:38AM +0800, Jackie Liu wrote:
> From: Jackie Liu <liuyun01@kylinos.cn>
>
> After commit 8a1065127d95 ("coresight: trbe: Add infrastructure for Errata handling"),
> driver coresight use this_cpu_has_cap for check feature, but if we compile it
> as a module, it will cause a compilation error.
>
> [...]
> ERROR: modpost: "this_cpu_has_cap" [drivers/hwtracing/coresight/coresight-trbe.ko] undefined!
> make[1]: *** [scripts/Makefile.modpost:134: modules-only.symvers] Error 1
> make[1]: *** Deleting file 'modules-only.symvers'
> make: *** [Makefile:1765: modules] Error 2
> make: *** Waiting for unfinished jobs....
> [...]
>
> Fixes: 8a1065127d95 ("coresight: trbe: Add infrastructure for Errata handling")
> Reported-by: kernelbot <kernel-bot@kylinos.cn>
> Signed-off-by: Jackie Liu <liuyun01@kylinos.cn>
There is a patch already, not sure whether it has made it into mainline:
https://lore.kernel.org/r/20211103221256.725080-1-suzuki.poulose@arm.com
--
Catalin
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2021-11-11 15:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-11 3:21 [PATCH] arm64: export this_cpu_has_cap Jackie Liu
2021-11-11 15:32 ` Catalin Marinas [this message]
2021-11-11 16:59 ` Suzuki K Poulose
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=YY03mbRCW0iMPftm@arm.com \
--to=catalin.marinas@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=liu.yun@linux.dev \
--cc=mark.rutland@arm.com \
--cc=mathieu.poirier@linaro.org \
--cc=suzuki.poulose@arm.com \
--cc=will@kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.