From: kernel test robot <lkp@intel.com>
To: Andrew Davis <afd@ti.com>
Cc: oe-kbuild-all@lists.linux.dev, vigneshr@ti.com, nm@ti.com
Subject: [ti:ti-rt-linux-6.1.y-cicd 256/382] WARNING: modpost: module dma-buf-phys uses symbol dma_buf_unmap_attachment from namespace DMA_BUF, but does not import it.
Date: Sun, 13 Oct 2024 09:45:17 +0800 [thread overview]
Message-ID: <202410130927.pen12PCq-lkp@intel.com> (raw)
tree: git://git.ti.com/ti-linux-kernel/ti-linux-kernel.git ti-rt-linux-6.1.y-cicd
head: 451df8c0a2a3bcf0656b2f6fdc49d6fb4d05f186
commit: a6d074da1a95aa77f6d6315d7c454623ff578a7e [256/382] HACK: misc: Add dma-buf to physical address exporter
config: sh-randconfig-002-20241013 (https://download.01.org/0day-ci/archive/20241013/202410130927.pen12PCq-lkp@intel.com/config)
compiler: sh4-linux-gcc (GCC) 14.1.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20241013/202410130927.pen12PCq-lkp@intel.com/reproduce)
If you fix the issue in a separate patch/commit (i.e. not just a new version of
the same patch/commit), kindly add following tags
| Reported-by: kernel test robot <lkp@intel.com>
| Closes: https://lore.kernel.org/oe-kbuild-all/202410130927.pen12PCq-lkp@intel.com/
All warnings (new ones prefixed by >>, old ones prefixed by <<):
>> WARNING: modpost: module dma-buf-phys uses symbol dma_buf_unmap_attachment from namespace DMA_BUF, but does not import it.
>> WARNING: modpost: module dma-buf-phys uses symbol dma_buf_put from namespace DMA_BUF, but does not import it.
>> WARNING: modpost: module dma-buf-phys uses symbol dma_buf_detach from namespace DMA_BUF, but does not import it.
>> WARNING: modpost: module dma-buf-phys uses symbol dma_buf_get from namespace DMA_BUF, but does not import it.
>> WARNING: modpost: module dma-buf-phys uses symbol dma_buf_attach from namespace DMA_BUF, but does not import it.
>> WARNING: modpost: module dma-buf-phys uses symbol dma_buf_map_attachment from namespace DMA_BUF, but does not import it.
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2024-10-13 1:45 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=202410130927.pen12PCq-lkp@intel.com \
--to=lkp@intel.com \
--cc=afd@ti.com \
--cc=nm@ti.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=vigneshr@ti.com \
/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.