All of lore.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: kbuild-all@lists.01.org
Subject: [android-common:android12-5.10 2047/10515] ERROR: modpost: "virtio_dma_buf_attach" [drivers/gpu/drm/virtio/virtio-gpu.ko] undefined!
Date: Wed, 07 Jul 2021 23:51:14 +0800	[thread overview]
Message-ID: <202107072307.R8NnPSYo-lkp@intel.com> (raw)

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

Hi Alistair,

FYI, the error/warning still remains.

tree:   https://android.googlesource.com/kernel/common android12-5.10
head:   44584944761fe4adabc0f7c3e29e7535f44a1417
commit: e03a3cf3cc429a2770817a1721bda8946a8c3989 [2047/10515] ANDROID: GKI: Unhide VIRTIO_DMA_SHARED_BUFFER
config: i386-randconfig-a004-20210707 (attached as .config)
compiler: gcc-9 (Debian 9.3.0-22) 9.3.0
reproduce (this is a W=1 build):
        git remote add android-common https://android.googlesource.com/kernel/common
        git fetch --no-tags android-common android12-5.10
        git checkout e03a3cf3cc429a2770817a1721bda8946a8c3989
        # save the attached .config to linux build tree
        make W=1 ARCH=i386 

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: "virtio_dma_buf_attach" [drivers/gpu/drm/virtio/virtio-gpu.ko] undefined!
>> ERROR: modpost: "virtio_dma_buf_export" [drivers/gpu/drm/virtio/virtio-gpu.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: 34805 bytes --]

                 reply	other threads:[~2021-07-07 15:51 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=202107072307.R8NnPSYo-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.