From: kernel test robot <lkp@intel.com>
To: Yang Yingliang <yangyingliang@huawei.com>,
linux-kernel@vger.kernel.org, linux-pci@vger.kernel.org
Cc: kbuild-all@lists.01.org, bhelgaas@google.com,
guohanjun@huawei.com, yangyingliang@huawei.com
Subject: Re: [PATCH 2/2] pci: fix memleak when calling pci_iomap/unmap()
Date: Fri, 28 Aug 2020 18:19:39 +0800 [thread overview]
Message-ID: <202008281842.M8vUTzwA%lkp@intel.com> (raw)
In-Reply-To: <20200828063403.3995421-3-yangyingliang@huawei.com>
[-- Attachment #1: Type: text/plain, Size: 1418 bytes --]
Hi Yang,
Thank you for the patch! Yet something to improve:
[auto build test ERROR on pci/next]
[also build test ERROR on linux/master linus/master v5.9-rc2 next-20200828]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch]
url: https://github.com/0day-ci/linux/commits/Yang-Yingliang/fix-memleak-when-using-pci_iounmap/20200828-143645
base: https://git.kernel.org/pub/scm/linux/kernel/git/helgaas/pci.git next
config: microblaze-nommu_defconfig (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
# 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 >>):
microblaze-linux-ld: lib/pci_iomap.o: in function `pci_iounmap':
>> (.text+0x108): multiple definition of `pci_iounmap'; arch/microblaze/pci/iomap.o:(.text+0x0): first defined here
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 14265 bytes --]
next prev parent reply other threads:[~2020-08-28 10:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-28 6:34 [PATCH 0/2] fix memleak when using pci_iounmap() Yang Yingliang
2020-08-28 6:34 ` [PATCH 1/2] iomap: move some definitions to include/linux/io.h Yang Yingliang
2020-08-28 6:34 ` [PATCH 2/2] pci: fix memleak when calling pci_iomap/unmap() Yang Yingliang
2020-08-28 10:19 ` kernel test robot [this message]
2020-08-28 11:24 ` kernel test robot
2020-08-28 13:35 ` kernel test robot
2020-08-28 16:06 ` [PATCH 0/2] fix memleak when using pci_iounmap() Bjorn Helgaas
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=202008281842.M8vUTzwA%lkp@intel.com \
--to=lkp@intel.com \
--cc=bhelgaas@google.com \
--cc=guohanjun@huawei.com \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=yangyingliang@huawei.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).