From: Marco Elver <[email protected]>
To: kernel test robot <[email protected]>
Cc: [email protected], [email protected],
Ammar Faizi <[email protected]>,
"GNU/Weeb Mailing List" <[email protected]>,
"Paul E. McKenney" <[email protected]>
Subject: Re: [ammarfaizi2-block:paulmck/linux-rcu/kcsan 1/3] ERROR: modpost: "devm_ioremap_resource" [drivers/dma/fsl-edma.ko] undefined!
Date: Mon, 5 Dec 2022 08:00:00 +0100 [thread overview]
Message-ID: <CANpmjNM9T1KFwjG6yTXXyJR83oJujvfnDzhTPeW_2q=j=qi9LQ@mail.gmail.com> (raw)
In-Reply-To: <[email protected]>
On Sun, 4 Dec 2022 at 17:35, kernel test robot <[email protected]> wrote:
>
> Hi Marco,
>
> First bad commit (maybe != root cause):
>
> tree: https://github.com/ammarfaizi2/linux-block paulmck/linux-rcu/kcsan
> head: 144b9152791ffcd038c3b63063999b25780060d8
> commit: 7c201739beef1a586d806463f1465429cdce34c5 [1/3] kcsan: Instrument memcpy/memset/memmove with newer Clang
> config: s390-randconfig-r011-20221204
> compiler: clang version 16.0.0 (https://github.com/llvm/llvm-project 6e4cea55f0d1104408b26ac574566a0e4de48036)
My guess is that the above commit fixed the Clang 16 builds, which
means that compilation is proceeding and new errors are produced.
> ERROR: modpost: "devm_ioremap_resource" [drivers/dma/qcom/hdma.ko] undefined!
> >> ERROR: modpost: "devm_ioremap_resource" [drivers/dma/fsl-edma.ko] undefined!
Thanks,
-- Marco
prev parent reply other threads:[~2022-12-05 7:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-04 16:34 [ammarfaizi2-block:paulmck/linux-rcu/kcsan 1/3] ERROR: modpost: "devm_ioremap_resource" [drivers/dma/fsl-edma.ko] undefined! kernel test robot
2022-12-05 7:00 ` Marco Elver [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='CANpmjNM9T1KFwjG6yTXXyJR83oJujvfnDzhTPeW_2q=j=qi9LQ@mail.gmail.com' \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
/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