[xlnx:master 9476/10004] include/soc/xilinx/xlnx_vcu.h:15:1: error: unknown type name 'u32'
by kbuild test robot
Hi Michal,
FYI, the error/warning still remains.
tree: https://github.com/Xilinx/linux-xlnx master
head: d3eb15af1318b1d374e9a02dc2c119e34864c2b2
commit: b9042c17137500422bf53982253f44552e51ef87 [9476/10004] soc: xilinx: vcu: Add exported functions
config: ia64-randconfig-a001-20200430 (attached as .config)
compiler: ia64-linux-gcc (GCC) 9.3.0
reproduce:
wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
git checkout b9042c17137500422bf53982253f44552e51ef87
# save the attached .config to linux build tree
COMPILER_INSTALL_PATH=$HOME/0day GCC_VERSION=9.3.0 make.cross ARCH=ia64
If you fix the issue, kindly add following tag as appropriate
Reported-by: kbuild test robot <lkp(a)intel.com>
All errors (new ones prefixed by >>):
In file included from <command-line>:
>> include/soc/xilinx/xlnx_vcu.h:15:1: error: unknown type name 'u32'
15 | u32 xvcu_get_color_depth(struct xvcu_device *xvcu);
| ^~~
include/soc/xilinx/xlnx_vcu.h:16:1: error: unknown type name 'u32'
16 | u32 xvcu_get_memory_depth(struct xvcu_device *xvcu);
| ^~~
vim +/u32 +15 include/soc/xilinx/xlnx_vcu.h
14
> 15 u32 xvcu_get_color_depth(struct xvcu_device *xvcu);
16 u32 xvcu_get_memory_depth(struct xvcu_device *xvcu);
17
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
2 years
Re: [Intel-gfx] [PATCH 24/24] drm/i915: Ensure we hold the pin mutex
by kbuild test robot
Hi Maarten,
I love your patch! Yet something to improve:
[auto build test ERROR on drm-tip/drm-tip]
[cannot apply to drm-intel/for-linux-next tip/perf/core v5.7-rc3 next-20200501]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system. BTW, we also suggest to use '--base' option to specify the
base tree in git format-patch, please see https://stackoverflow.com/a/37406982]
url: https://github.com/0day-ci/linux/commits/Maarten-Lankhorst/perf-core-Only...
base: git://anongit.freedesktop.org/drm/drm-tip drm-tip
config: i386-defconfig (attached as .config)
compiler: gcc-7 (Ubuntu 7.5.0-6ubuntu2) 7.5.0
reproduce:
# save the attached .config to linux build tree
make ARCH=i386
If you fix the issue, kindly add following tag as appropriate
Reported-by: kbuild test robot <lkp(a)intel.com>
All errors (new ones prefixed by >>):
In file included from arch/x86/include/asm/bug.h:83:0,
from include/linux/bug.h:5,
from include/linux/cpumask.h:14,
from arch/x86/include/asm/cpumask.h:5,
from arch/x86/include/asm/msr.h:11,
from arch/x86/include/asm/processor.h:22,
from include/linux/mutex.h:19,
from include/linux/kernfs.h:12,
from include/linux/sysfs.h:16,
from include/linux/kobject.h:20,
from include/linux/of.h:17,
from include/linux/irqdomain.h:35,
from include/linux/acpi.h:13,
from drivers/gpu/drm/i915/i915_drv.c:30:
drivers/gpu/drm/i915/i915_vma.h: In function 'i915_vma_pin':
>> include/linux/dma-resv.h:80:28: error: implicit declaration of function 'lockdep_is_held'; did you mean 'lockdep_assert_held'? [-Werror=implicit-function-declaration]
#define dma_resv_held(obj) lockdep_is_held(&(obj)->lock.base)
^
include/asm-generic/bug.h:151:27: note: in definition of macro 'WARN_ONCE'
int __ret_warn_once = !!(condition); \
^~~~~~~~~
drivers/gpu/drm/i915/i915_vma.h:245:2: note: in expansion of macro 'WARN_ON_ONCE'
WARN_ON_ONCE(vma->resv && dma_resv_held(vma->resv));
^~~~~~~~~~~~
drivers/gpu/drm/i915/i915_vma.h:245:28: note: in expansion of macro 'dma_resv_held'
WARN_ON_ONCE(vma->resv && dma_resv_held(vma->resv));
^~~~~~~~~~~~~
cc1: some warnings being treated as errors
vim +80 include/linux/dma-resv.h
786d7257e537da0 include/linux/reservation.h Maarten Lankhorst 2013-06-27 79
52791eeec1d9f4a include/linux/dma-resv.h Christian König 2019-08-11 @80 #define dma_resv_held(obj) lockdep_is_held(&(obj)->lock.base)
52791eeec1d9f4a include/linux/dma-resv.h Christian König 2019-08-11 81 #define dma_resv_assert_held(obj) lockdep_assert_held(&(obj)->lock.base)
04a5faa8cbe5a8e include/linux/reservation.h Maarten Lankhorst 2014-07-01 82
:::::: The code at line 80 was first introduced by commit
:::::: 52791eeec1d9f4a7e7fe08aaba0b1553149d93bc dma-buf: rename reservation_object to dma_resv
:::::: TO: Christian König <christian.koenig(a)amd.com>
:::::: CC: Christian König <christian.koenig(a)amd.com>
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
2 years
[RFC PATCH] drm/mm: insert_hole_addr() can be static
by kbuild test robot
Signed-off-by: kbuild test robot <lkp(a)intel.com>
---
drm_mm.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/gpu/drm/drm_mm.c b/drivers/gpu/drm/drm_mm.c
index effc6e5cac459..89df90a6052d1 100644
--- a/drivers/gpu/drm/drm_mm.c
+++ b/drivers/gpu/drm/drm_mm.c
@@ -245,7 +245,7 @@ RB_DECLARE_CALLBACKS_MAX(static, augment_callbacks,
struct drm_mm_node, rb_hole_addr,
u64, subtree_max_hole, HOLE_SIZE)
-void insert_hole_addr(struct rb_root *root, struct drm_mm_node *node)
+static void insert_hole_addr(struct rb_root *root, struct drm_mm_node *node)
{
struct rb_node **link = &root->rb_node, *rb_parent = NULL;
u64 start = HOLE_ADDR(node), subtree_max_hole = node->subtree_max_hole;
2 years
Re: [PATCH v2 1/1] drm/mm: optimize rb_hole_addr rbtree search
by kbuild test robot
Hi Nirmoy,
Thank you for the patch! Perhaps something to improve:
[auto build test WARNING on drm-intel/for-linux-next]
[also build test WARNING on drm-exynos/exynos-drm-next tegra-drm/drm/tegra/for-next drm-tip/drm-tip linus/master v5.7-rc3 next-20200501]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system. BTW, we also suggest to use '--base' option to specify the
base tree in git format-patch, please see https://stackoverflow.com/a/37406982]
url: https://github.com/0day-ci/linux/commits/Nirmoy-Das/drm-mm-optimize-rb_ho...
base: git://anongit.freedesktop.org/drm-intel for-linux-next
reproduce:
# apt-get install sparse
# sparse version: v0.6.1-191-gc51a0382-dirty
make ARCH=x86_64 allmodconfig
make C=1 CF='-fdiagnostic-prefix -D__CHECK_ENDIAN__'
If you fix the issue, kindly add following tag as appropriate
Reported-by: kbuild test robot <lkp(a)intel.com>
sparse warnings: (new ones prefixed by >>)
>> drivers/gpu/drm/drm_mm.c:248:6: sparse: sparse: symbol 'insert_hole_addr' was not declared. Should it be static?
drivers/gpu/drm/drm_mm.c:401:24: sparse: sparse: Using plain integer as NULL pointer
drivers/gpu/drm/drm_mm.c:441:24: sparse: sparse: Using plain integer as NULL pointer
Please review and possibly fold the followup patch.
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
2 years
[linux-next:master 4171/6218] dpaa2-eth-debugfs.c:undefined reference to `__udivdi3'
by kbuild test robot
tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
head: fb9d670f57e3f6478602328bbbf71138be06ca4f
commit: 460fd830dd9d68e07c4d15363fd764944090e1f8 [4171/6218] dpaa2-eth: add channel stat to debugfs
config: i386-allyesconfig (attached as .config)
compiler: gcc-7 (Ubuntu 7.5.0-6ubuntu2) 7.5.0
reproduce:
git checkout 460fd830dd9d68e07c4d15363fd764944090e1f8
# save the attached .config to linux build tree
make ARCH=i386
If you fix the issue, kindly add following tag as appropriate
Reported-by: kbuild test robot <lkp(a)intel.com>
Note: the linux-next/master HEAD fb9d670f57e3f6478602328bbbf71138be06ca4f builds fine.
It may have been fixed somewhere.
All errors (new ones prefixed by >>):
ld: drivers/net/ethernet/freescale/dpaa2/dpaa2-eth-debugfs.o: in function `dpaa2_dbg_ch_show':
>> dpaa2-eth-debugfs.c:(.text+0x194): undefined reference to `__udivdi3'
ld: net/openvswitch/meter.o: in function `ovs_meter_cmd_set':
meter.c:(.text+0x71e): undefined reference to `__udivdi3'
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
2 years
[RFC PATCH] ext4: __pcpu_scope_discard_pa_seq can be static
by kbuild test robot
Signed-off-by: kbuild test robot <lkp(a)intel.com>
---
mballoc.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/fs/ext4/mballoc.c b/fs/ext4/mballoc.c
index 6bb08bb3c0cee..462ddad104315 100644
--- a/fs/ext4/mballoc.c
+++ b/fs/ext4/mballoc.c
@@ -375,7 +375,7 @@ static void ext4_mb_generate_from_freelist(struct super_block *sb, void *bitmap,
* below function ext4_get_discard_pa_seq_sum(). This happens after making
* sure that all the PAs on grp->bb_prealloc_list got freed.
*/
-DEFINE_PER_CPU(u64, discard_pa_seq);
+static DEFINE_PER_CPU(u64, discard_pa_seq);
static inline u64 ext4_get_discard_pa_seq_sum(void)
{
int __cpu;
2 years
[lkp] [+3086 bytes kernel size regression] [i386-tinyconfig] [3a4ac121c2] x86/perf: Add hardware performance events support for Zhaoxin CPU.
by kbuild test robot
FYI, we noticed a +3086 bytes kernel size regression due to commit:
commit: 3a4ac121c2cacbf97d493fa3bc42ead88657abe4 (x86/perf: Add hardware performance events support for Zhaoxin CPU.)
https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git perf/core
Details as below (size data is obtained by `nm --size-sort vmlinux`):
87cfeb19: Merge tag 'perf-core-for-mingo-5.8-20200420' of git://git.kernel.org/pub/scm/linux/kernel/git/acme/linux into perf/core
3a4ac121: x86/perf: Add hardware performance events support for Zhaoxin CPU.
+------------------------------------+----------+----------+-------+
| symbol | 87cfeb19 | 3a4ac121 | delta |
+------------------------------------+----------+----------+-------+
| bzImage | 439232 | 440192 | 960 |
| nm.T.zhaoxin_pmu_init | 0 | 877 | 877 |
| nm.t.zhaoxin_pmu_handle_irq | 0 | 480 | 480 |
| nm.t.zxd_hw_cache_event_ids | 0 | 336 | 336 |
| nm.t.zxe_hw_cache_event_ids | 0 | 336 | 336 |
| nm.t.zhaoxin_pmu_enable_event | 0 | 292 | 292 |
| nm.d.zxd_event_constraints | 0 | 160 | 160 |
| nm.t.zhaoxin_pmu_disable_event | 0 | 143 | 143 |
| nm.d.zx_pmon_event_map | 0 | 80 | 80 |
| nm.d.zxc_event_constraints | 0 | 80 | 80 |
| nm.t.zhaoxin_arch_events_quirk | 0 | 70 | 70 |
| nm.t.zhaoxin_get_event_constraints | 0 | 66 | 66 |
| nm.t.zx_arch_events_map | 0 | 56 | 56 |
| nm.d.zx_arch_formats_attr | 0 | 24 | 24 |
| nm.t.zhaoxin_pmu_enable_all | 0 | 22 | 22 |
| nm.t.zhaoxin_pmu_event_map | 0 | 21 | 21 |
| nm.t.zhaoxin_event_sysfs_show | 0 | 19 | 19 |
| nm.t.init_hw_perf_events | 726 | 739 | 13 |
| nm.t.zhaoxin_pmu_disable_all | 0 | 11 | 11 |
| nm.T.intel_pmu_init | 4196 | 4197 | 1 |
| nm.R.linux_banner | 164 | 163 | -1 |
+------------------------------------+----------+----------+-------+
Thanks,
Kbuild test robot
2 years
Re: [PATCH 1/4] counter: Internalize sysfs interface code (fwd)
by Julia Lawall
Hello,
Normally, the argument of kfree should not start with &.
julia
---------- Forwarded message ----------
Date: Fri, 1 May 2020 06:07:26 +0800
From: kbuild test robot <lkp(a)intel.com>
To: kbuild(a)lists.01.org
Cc: lkp(a)intel.com, Julia Lawall <julia.lawall(a)lip6.fr>
Subject: Re: [PATCH 1/4] counter: Internalize sysfs interface code
CC: kbuild-all(a)lists.01.org
In-Reply-To: <d84f0bb3258d1664e90da64d75f787829c50a9bd.1588176662.git.vilhelm.gray(a)gmail.com>
References: <d84f0bb3258d1664e90da64d75f787829c50a9bd.1588176662.git.vilhelm.gray(a)gmail.com>
TO: William Breathitt Gray <vilhelm.gray(a)gmail.com>
TO: jic23(a)kernel.org
CC: kamel.bouhara(a)bootlin.com
CC: gwendal(a)chromium.org
CC: alexandre.belloni(a)bootlin.com
CC: david(a)lechnology.com
CC: felipe.balbi(a)linux.intel.com
CC: fabien.lahoudere(a)collabora.com
CC: linux-iio(a)vger.kernel.org
CC: linux-kernel(a)vger.kernel.org
CC: linux-stm32(a)st-md-mailman.stormreply.com
Hi William,
I love your patch! Perhaps something to improve:
[auto build test WARNING on stm32/stm32-next]
[cannot apply to linus/master linux/master v5.7-rc3 next-20200430]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system. BTW, we also suggest to use '--base' option to specify the
base tree in git format-patch, please see https://stackoverflow.com/a/37406982]
url: https://github.com/0day-ci/linux/commits/William-Breathitt-Gray/Introduce...
base: https://git.kernel.org/pub/scm/linux/kernel/git/atorgue/stm32.git stm32-next
:::::: branch date: 25 hours ago
:::::: commit date: 25 hours ago
If you fix the issue, kindly add following tag as appropriate
Reported-by: kbuild test robot <lkp(a)intel.com>
Reported-by: Julia Lawall <julia.lawall(a)lip6.fr>
coccinelle warnings: (new ones prefixed by >>)
>> drivers/counter/counter-core.c:26:1-6: ERROR: invalid free of structure field
# https://github.com/0day-ci/linux/commit/bdd9a6aa70c61f16dacaf057f0ce70fc2...
git remote add linux-review https://github.com/0day-ci/linux
git remote update linux-review
git checkout bdd9a6aa70c61f16dacaf057f0ce70fc210b5ec9
vim +26 drivers/counter/counter-core.c
bdd9a6aa70c61f1 William Breathitt Gray 2020-04-29 20
bdd9a6aa70c61f1 William Breathitt Gray 2020-04-29 21 static void counter_device_release(struct device *dev)
bdd9a6aa70c61f1 William Breathitt Gray 2020-04-29 22 {
bdd9a6aa70c61f1 William Breathitt Gray 2020-04-29 23 struct counter_device *const counter = dev_get_drvdata(dev);
bdd9a6aa70c61f1 William Breathitt Gray 2020-04-29 24
bdd9a6aa70c61f1 William Breathitt Gray 2020-04-29 25 counter_sysfs_free(counter);
bdd9a6aa70c61f1 William Breathitt Gray 2020-04-29 @26 kfree(&counter->dev);
bdd9a6aa70c61f1 William Breathitt Gray 2020-04-29 27 ida_simple_remove(&counter_ida, counter->id);
bdd9a6aa70c61f1 William Breathitt Gray 2020-04-29 28 }
bdd9a6aa70c61f1 William Breathitt Gray 2020-04-29 29
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
2 years
Re: [PATCH v3 02/25] mm: Introduce thp_size
by kbuild test robot
Hi Matthew,
Thank you for the patch! Yet something to improve:
[auto build test ERROR on next-20200429]
[also build test ERROR on v5.7-rc3]
[cannot apply to xfs-linux/for-next linux-nvdimm/libnvdimm-for-next ext4/dev f2fs/dev-test linus/master shaggy/jfs-next v5.7-rc3 v5.7-rc2 v5.7-rc1]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system. BTW, we also suggest to use '--base' option to specify the
base tree in git format-patch, please see https://stackoverflow.com/a/37406982]
url: https://github.com/0day-ci/linux/commits/Matthew-Wilcox/Large-pages-in-th...
base: 861978d1331b7e988e0295a2275c669c767fa3f1
config: arm64-allyesconfig (attached as .config)
compiler: aarch64-linux-gcc (GCC) 9.3.0
reproduce:
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 GCC_VERSION=9.3.0 make.cross ARCH=arm64
If you fix the issue, kindly add following tag as appropriate
Reported-by: kbuild test robot <lkp(a)intel.com>
All errors (new ones prefixed by >>):
drivers/nvdimm/pmem.c: In function 'pmem_rw_page':
>> drivers/nvdimm/pmem.c:238:45: error: implicit declaration of function 'tmp_size'; did you mean 'thp_size'? [-Werror=implicit-function-declaration]
238 | rc = pmem_do_write(pmem, page, 0, sector, tmp_size(page));
| ^~~~~~~~
| thp_size
cc1: some warnings being treated as errors
vim +238 drivers/nvdimm/pmem.c
230
231 static int pmem_rw_page(struct block_device *bdev, sector_t sector,
232 struct page *page, unsigned int op)
233 {
234 struct pmem_device *pmem = bdev->bd_queue->queuedata;
235 blk_status_t rc;
236
237 if (op_is_write(op))
> 238 rc = pmem_do_write(pmem, page, 0, sector, tmp_size(page));
239 else
240 rc = pmem_do_read(pmem, page, 0, sector, thp_size(page));
241 /*
242 * The ->rw_page interface is subtle and tricky. The core
243 * retries on any error, so we can only invoke page_endio() in
244 * the successful completion case. Otherwise, we'll see crashes
245 * caused by double completion.
246 */
247 if (rc == 0)
248 page_endio(page, op_is_write(op), 0);
249
250 return blk_status_to_errno(rc);
251 }
252
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
2 years