All of lore.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: kbuild-all@lists.01.org
Subject: [stffrdhrn:starfive-bad-dcache-flush 9/39] ERROR: modpost: "__udivdi3" [drivers/pwm/pwm-sifive-ptc.ko] undefined!
Date: Sun, 23 May 2021 02:27:12 +0800	[thread overview]
Message-ID: <202105230206.BxQmPEsk-lkp@intel.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1324 bytes --]

tree:   https://github.com/stffrdhrn/linux.git starfive-bad-dcache-flush
head:   a5c948a9cc2b8944f00056c067fb7bde19b34843
commit: 76d60389d04dfd86f4a655e3b1e5b2d4dd4cc896 [9/39] drivers/pwm: Add SiFive PWM PTC driver
config: microblaze-randconfig-c003-20210522 (attached as .config)
compiler: microblaze-linux-gcc (GCC) 9.3.0
reproduce (this is a W=1 build):
        wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
        chmod +x ~/bin/make.cross
        # https://github.com/stffrdhrn/linux/commit/76d60389d04dfd86f4a655e3b1e5b2d4dd4cc896
        git remote add stffrdhrn https://github.com/stffrdhrn/linux.git
        git fetch --no-tags stffrdhrn starfive-bad-dcache-flush
        git checkout 76d60389d04dfd86f4a655e3b1e5b2d4dd4cc896
        # save the attached .config to linux build tree
        COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-9.3.0 make.cross ARCH=microblaze 

If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>

All errors (new ones prefixed by >>, old ones prefixed by <<):

>> ERROR: modpost: "__udivdi3" [drivers/pwm/pwm-sifive-ptc.ko] undefined!

---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all(a)lists.01.org

[-- Attachment #2: config.gz --]
[-- Type: application/gzip, Size: 17411 bytes --]

                 reply	other threads:[~2021-05-22 18:27 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=202105230206.BxQmPEsk-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=kbuild-all@lists.01.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.