From: kernel test robot <lkp@intel.com>
To: Binglei Wang <l3b2w1@gmail.com>, hch@lst.de
Cc: oe-kbuild-all@lists.linux.dev, m.szyprowski@samsung.com,
robin.murphy@arm.com, iommu@lists.linux.dev,
linux-kernel@vger.kernel.org, l3b2w1@gmail.com
Subject: Re: [PATCH v2] cma: check for memory region overlapping
Date: Wed, 26 Jul 2023 05:30:13 +0800 [thread overview]
Message-ID: <202307260509.OMkcRpqC-lkp@intel.com> (raw)
In-Reply-To: <20230725141602.7759-1-l3b2w1@gmail.com>
Hi Binglei,
kernel test robot noticed the following build warnings:
[auto build test WARNING on linus/master]
[also build test WARNING on v6.5-rc3 next-20230725]
[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#_base_tree_information]
url: https://github.com/intel-lab-lkp/linux/commits/Binglei-Wang/cma-check-for-memory-region-overlapping/20230725-222426
base: linus/master
patch link: https://lore.kernel.org/r/20230725141602.7759-1-l3b2w1%40gmail.com
patch subject: [PATCH v2] cma: check for memory region overlapping
config: i386-allyesconfig (https://download.01.org/0day-ci/archive/20230726/202307260509.OMkcRpqC-lkp@intel.com/config)
compiler: gcc-12 (Debian 12.2.0-14) 12.2.0
reproduce: (https://download.01.org/0day-ci/archive/20230726/202307260509.OMkcRpqC-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/202307260509.OMkcRpqC-lkp@intel.com/
All warnings (new ones prefixed by >>):
In file included from include/linux/elf.h:6,
from include/linux/module.h:19,
from include/linux/device/driver.h:21,
from include/linux/device.h:32,
from include/linux/dma-mapping.h:8,
from include/linux/dma-map-ops.h:9,
from kernel/dma/contiguous.c:51:
arch/x86/include/asm/elf.h: In function 'rmem_cma_setup':
arch/x86/include/asm/elf.h:204:29: error: unterminated argument list invoking macro "pr_info"
204 | (pr_reg)[11] = (regs)->cx; \
| ^
kernel/dma/contiguous.c:414:17: error: 'pr_info' undeclared (first use in this function); did you mean 'pv_info'?
414 | pr_info("Reserved memory: overlap with other memblock reserved region\n",
| ^~~~~~~
| pv_info
kernel/dma/contiguous.c:414:17: note: each undeclared identifier is reported only once for each function it appears in
kernel/dma/contiguous.c:414:24: error: expected ';' at end of input
414 | pr_info("Reserved memory: overlap with other memblock reserved region\n",
| ^
| ;
......
kernel/dma/contiguous.c:414:17: error: expected declaration or statement at end of input
414 | pr_info("Reserved memory: overlap with other memblock reserved region\n",
| ^~~~~~~
kernel/dma/contiguous.c:414:17: error: expected declaration or statement at end of input
>> kernel/dma/contiguous.c:405:13: warning: unused variable 'err' [-Wunused-variable]
405 | int err;
| ^~~
>> kernel/dma/contiguous.c:404:21: warning: unused variable 'cma' [-Wunused-variable]
404 | struct cma *cma;
| ^~~
kernel/dma/contiguous.c: At top level:
>> kernel/dma/contiguous.c:400:19: warning: 'rmem_cma_setup' defined but not used [-Wunused-function]
400 | static int __init rmem_cma_setup(struct reserved_mem *rmem)
| ^~~~~~~~~~~~~~
>> kernel/dma/contiguous.c:395:38: warning: 'rmem_cma_ops' defined but not used [-Wunused-const-variable=]
395 | static const struct reserved_mem_ops rmem_cma_ops = {
| ^~~~~~~~~~~~
vim +/err +405 kernel/dma/contiguous.c
de9e14eebf33a6 drivers/base/dma-contiguous.c Marek Szyprowski 2014-10-13 394
de9e14eebf33a6 drivers/base/dma-contiguous.c Marek Szyprowski 2014-10-13 @395 static const struct reserved_mem_ops rmem_cma_ops = {
de9e14eebf33a6 drivers/base/dma-contiguous.c Marek Szyprowski 2014-10-13 396 .device_init = rmem_cma_device_init,
de9e14eebf33a6 drivers/base/dma-contiguous.c Marek Szyprowski 2014-10-13 397 .device_release = rmem_cma_device_release,
de9e14eebf33a6 drivers/base/dma-contiguous.c Marek Szyprowski 2014-10-13 398 };
de9e14eebf33a6 drivers/base/dma-contiguous.c Marek Szyprowski 2014-10-13 399
de9e14eebf33a6 drivers/base/dma-contiguous.c Marek Szyprowski 2014-10-13 @400 static int __init rmem_cma_setup(struct reserved_mem *rmem)
de9e14eebf33a6 drivers/base/dma-contiguous.c Marek Szyprowski 2014-10-13 401 {
de9e14eebf33a6 drivers/base/dma-contiguous.c Marek Szyprowski 2014-10-13 402 unsigned long node = rmem->fdt_node;
8c8c5a4994a306 kernel/dma/contiguous.c Nicolas Saenz Julienne 2020-01-10 403 bool default_cma = of_get_flat_dt_prop(node, "linux,cma-default", NULL);
de9e14eebf33a6 drivers/base/dma-contiguous.c Marek Szyprowski 2014-10-13 @404 struct cma *cma;
de9e14eebf33a6 drivers/base/dma-contiguous.c Marek Szyprowski 2014-10-13 @405 int err;
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
prev parent reply other threads:[~2023-07-25 21:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-25 14:16 Binglei Wang
2023-07-25 16:19 ` kernel test robot
2023-07-25 17:21 ` kernel test robot
2023-07-25 21:30 ` kernel test robot [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=202307260509.OMkcRpqC-lkp@intel.com \
--to=lkp@intel.com \
--cc=hch@lst.de \
--cc=iommu@lists.linux.dev \
--cc=l3b2w1@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=m.szyprowski@samsung.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=robin.murphy@arm.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
all inboxes | Powered by JetHome®