[linux-next:master] BUILD REGRESSION 632483ea8004edfadd035de36e1ab2c7c4f53158

2024-05-20 Thread kernel test robot
tree/branch: 
https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
branch HEAD: 632483ea8004edfadd035de36e1ab2c7c4f53158  Add linux-next specific 
files for 20240520

Error/Warning reports:

https://lore.kernel.org/oe-kbuild-all/202405202243.shvs2otq-...@intel.com
https://lore.kernel.org/oe-kbuild-all/202405210004.5m02x213-...@intel.com

Error/Warning: (recently discovered and may have been fixed)

drivers/thermal/thermal_trip.o: warning: objtool: unexpected relocation symbol 
type in .rela.discard.reachable

Error/Warning ids grouped by kconfigs:

gcc_recent_errors
|-- alpha-allyesconfig
|   |-- 
drivers-gpu-drm-imx-ipuv3-imx-ldb.c:error:_sel-directive-output-may-be-truncated-writing-bytes-into-a-region-of-size-between-and
|   |-- 
drivers-gpu-drm-nouveau-nouveau_backlight.c:error:d-directive-output-may-be-truncated-writing-between-and-bytes-into-a-region-of-size
|   `-- 
drivers-regulator-rtq2208-regulator.c:warning:rtq2208_regulator_ldo_ops-defined-but-not-used
|-- arc-allmodconfig
|   `-- 
drivers-regulator-rtq2208-regulator.c:warning:rtq2208_regulator_ldo_ops-defined-but-not-used
|-- arc-allyesconfig
|   `-- 
drivers-regulator-rtq2208-regulator.c:warning:rtq2208_regulator_ldo_ops-defined-but-not-used
|-- arc-randconfig-002-20240520
|   `-- 
drivers-regulator-rtq2208-regulator.c:warning:rtq2208_regulator_ldo_ops-defined-but-not-used
|-- arm-allmodconfig
|   |-- 
drivers-gpu-drm-imx-ipuv3-imx-ldb.c:error:_sel-directive-output-may-be-truncated-writing-bytes-into-a-region-of-size-between-and
|   |-- 
drivers-gpu-drm-nouveau-nouveau_backlight.c:error:d-directive-output-may-be-truncated-writing-between-and-bytes-into-a-region-of-size
|   `-- 
drivers-regulator-rtq2208-regulator.c:warning:rtq2208_regulator_ldo_ops-defined-but-not-used
|-- arm-allyesconfig
|   |-- 
drivers-gpu-drm-imx-ipuv3-imx-ldb.c:error:_sel-directive-output-may-be-truncated-writing-bytes-into-a-region-of-size-between-and
|   |-- 
drivers-gpu-drm-nouveau-nouveau_backlight.c:error:d-directive-output-may-be-truncated-writing-between-and-bytes-into-a-region-of-size
|   `-- 
drivers-regulator-rtq2208-regulator.c:warning:rtq2208_regulator_ldo_ops-defined-but-not-used
|-- arm-randconfig-003-20240520
|   `-- 
drivers-regulator-rtq2208-regulator.c:warning:rtq2208_regulator_ldo_ops-defined-but-not-used
|-- csky-allmodconfig
|   |-- 
drivers-gpu-drm-imx-ipuv3-imx-ldb.c:error:_sel-directive-output-may-be-truncated-writing-bytes-into-a-region-of-size-between-and
|   |-- 
drivers-gpu-drm-nouveau-nouveau_backlight.c:error:d-directive-output-may-be-truncated-writing-between-and-bytes-into-a-region-of-size
|   `-- 
drivers-regulator-rtq2208-regulator.c:warning:rtq2208_regulator_ldo_ops-defined-but-not-used
|-- csky-allyesconfig
|   |-- 
drivers-gpu-drm-imx-ipuv3-imx-ldb.c:error:_sel-directive-output-may-be-truncated-writing-bytes-into-a-region-of-size-between-and
|   |-- 
drivers-gpu-drm-nouveau-nouveau_backlight.c:error:d-directive-output-may-be-truncated-writing-between-and-bytes-into-a-region-of-size
|   `-- 
drivers-regulator-rtq2208-regulator.c:warning:rtq2208_regulator_ldo_ops-defined-but-not-used
|-- csky-randconfig-001-20240520
|   `-- 
drivers-regulator-rtq2208-regulator.c:warning:rtq2208_regulator_ldo_ops-defined-but-not-used
|-- i386-allmodconfig
|   |-- ERROR:__udivdi3-drivers-vdpa-octeon_ep-octep_vdpa.ko-undefined
|   `-- 
drivers-regulator-rtq2208-regulator.c:warning:rtq2208_regulator_ldo_ops-defined-but-not-used
|-- i386-allyesconfig
|   |-- ERROR:__udivdi3-drivers-vdpa-octeon_ep-octep_vdpa.ko-undefined
|   `-- 
drivers-regulator-rtq2208-regulator.c:warning:rtq2208_regulator_ldo_ops-defined-but-not-used
|-- i386-randconfig-012-20240520
|   `-- 
drivers-regulator-rtq2208-regulator.c:warning:rtq2208_regulator_ldo_ops-defined-but-not-used
|-- i386-randconfig-014-20240520
|   `-- 
drivers-regulator-rtq2208-regulator.c:warning:rtq2208_regulator_ldo_ops-defined-but-not-used
|-- i386-randconfig-016-20240520
|   `-- 
drivers-regulator-rtq2208-regulator.c:warning:rtq2208_regulator_ldo_ops-defined-but-not-used
|-- loongarch-allmodconfig
|   |-- 
drivers-gpu-drm-imx-ipuv3-imx-ldb.c:error:_sel-directive-output-may-be-truncated-writing-bytes-into-a-region-of-size-between-and
|   |-- 
drivers-gpu-drm-nouveau-nouveau_backlight.c:error:d-directive-output-may-be-truncated-writing-between-and-bytes-into-a-region-of-size
|   `-- 
drivers-regulator-rtq2208-regulator.c:warning:rtq2208_regulator_ldo_ops-defined-but-not-used
|-- loongarch-defconfig
|   `-- 
drivers-thermal-thermal_trip.o:warning:objtool:unexpected-relocation-symbol-type-in-.rela.discard.reachable
|-- loongarch-randconfig-002-20240520
|   `-- 
drivers-regulator-rtq2208-regulator.c:warning:rtq2208_regulator_ldo_ops-defined-but-not-used
|-- m68k-allmodconfig
|   `-- 
drivers-regulator-rtq2208-regulator.c:warning:rtq2208_regulator_ldo_ops-defined-but-not-used
|-- m68k-allyesconfig
|   `-- 

[drm-tip:drm-tip 10/10] htmldocs: Warning: integration-manifest references a file that doesn't exist: Documentation/i915

2024-05-14 Thread kernel test robot
tree:   git://anongit.freedesktop.org/drm/drm-tip drm-tip
head:   723adadf19b6bd8a54881b0e7d04ba56c4e8f401
commit: 723adadf19b6bd8a54881b0e7d04ba56c4e8f401 [10/10] drm-tip: 
2024y-05m-14d-12h-21m-31s UTC integration manifest
reproduce: 
(https://download.01.org/0day-ci/archive/20240514/202405142346.oqo7oogu-...@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 
| Closes: 
https://lore.kernel.org/oe-kbuild-all/202405142346.oqo7oogu-...@intel.com/

All warnings (new ones prefixed by >>):

   Warning: Documentation/devicetree/bindings/power/wakeup-source.txt 
references a file that doesn't exist: 
Documentation/devicetree/bindings/input/qcom,pm8xxx-keypad.txt
   Warning: 
Documentation/devicetree/bindings/regulator/siliconmitus,sm5703-regulator.yaml 
references a file that doesn't exist: 
Documentation/devicetree/bindings/mfd/siliconmitus,sm5703.yaml
   Warning: Documentation/devicetree/bindings/sound/fsl-asoc-card.txt 
references a file that doesn't exist: 
Documentation/devicetree/bindings/sound/fsl,asrc.txt
   Warning: Documentation/userspace-api/netlink/index.rst references a file 
that doesn't exist: Documentation/networking/netlink_spec/index.rst
   Warning: Documentation/userspace-api/netlink/specs.rst references a file 
that doesn't exist: Documentation/networking/netlink_spec/index.rst
>> Warning: integration-manifest references a file that doesn't exist: 
>> Documentation/i915
   Using alabaster theme

-- 
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki


Re: [PATCH 4/5] refcount: Introduce refcount_long_t and APIs

2024-05-06 Thread kernel test robot


hi, Kees Cook,

we noticed a WARNING is our boot tests. 
as we understand, the WARNING is not introduced by this patch, instead, just
changing stats as below.
however, we failed to bisect
"dmesg.WARNING:at_lib/refcount.c:#refcount_warn_saturate"
which shows in parent commit to capture real commit which introduced the WARNING

just made this report FYI what we observed in our boot tests.


8090de6a0536f462 93b9cd30de232c9b4e27221dff6
 ---
   fail:runs  %reproductionfail:runs
   | | |
   :6  100%   6:6 
dmesg.EIP:refcount_report_saturation
  6:6 -100%:6 dmesg.EIP:refcount_warn_saturate
   :6  100%   6:6 
dmesg.WARNING:at_lib/refcount.c:#refcount_report_saturation
  6:6 -100%:6 
dmesg.WARNING:at_lib/refcount.c:#refcount_warn_saturate


Hello,

kernel test robot noticed 
"WARNING:at_lib/refcount.c:#refcount_report_saturation" on:

commit: 93b9cd30de232c9b4e27221dff6d02ac557b86eb ("[PATCH 4/5] refcount: 
Introduce refcount_long_t and APIs")
url: 
https://github.com/intel-lab-lkp/linux/commits/Kees-Cook/fs-Do-not-allow-get_file-to-resurrect-0-f_count/20240503-063542
base: https://git.kernel.org/cgit/linux/kernel/git/vfs/vfs.git vfs.all
patch link: 
https://lore.kernel.org/all/20240502223341.1835070-4-keesc...@chromium.org/
patch subject: [PATCH 4/5] refcount: Introduce refcount_long_t and APIs

in testcase: boot

compiler: gcc-13
test machine: qemu-system-x86_64 -enable-kvm -cpu SandyBridge -smp 2 -m 16G

(please refer to attached dmesg/kmsg for entire log/backtrace)



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 
| Closes: 
https://lore.kernel.org/oe-lkp/202405061514.23fedba1-oliver.s...@intel.com


[2.683270][T1] [ cut here ]
[2.684014][T1] refcount_t: decrement hit 0; leaking memory.
[ 2.684829][ T1] WARNING: CPU: 0 PID: 1 at lib/refcount.c:29 
refcount_report_saturation (lib/refcount.c:29 (discriminator 1)) 
[2.686080][T1] Modules linked in:
[2.686633][T1] CPU: 0 PID: 1 Comm: swapper/0 Not tainted 
6.9.0-rc3-00078-g93b9cd30de23 #1 ade0d32fff89aed56247bad9c6991c6e60a975d2
[2.688188][T1] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), 
BIOS 1.16.2-debian-1.16.2-1 04/01/2014
[ 2.689523][ T1] EIP: refcount_report_saturation (lib/refcount.c:29 
(discriminator 1)) 
[ 2.690327][ T1] Code: c2 01 e8 92 8a b1 ff 0f 0b 58 c9 31 c0 31 d2 31 c9 c3 8d 
b4 26 00 00 00 00 68 ec bc f4 c1 c6 05 3e 42 4a c2 01 e8 6f 8a b1 ff <0f> 0b 5a 
c9 31 c0 31 d2 31 c9 c3 55 89 c1 89 d0 c7 01 00 00 00 c0
All code

   0:   c2 01 e8ret$0xe801
   3:   92  xchg   %eax,%edx
   4:   8a b1 ff 0f 0b 58   mov0x580b0fff(%rcx),%dh
   a:   c9  leave
   b:   31 c0   xor%eax,%eax
   d:   31 d2   xor%edx,%edx
   f:   31 c9   xor%ecx,%ecx
  11:   c3  ret
  12:   8d b4 26 00 00 00 00lea0x0(%rsi,%riz,1),%esi
  19:   68 ec bc f4 c1  push   $0xc1f4bcec
  1e:   c6 05 3e 42 4a c2 01movb   $0x1,-0x3db5bdc2(%rip)# 
0xc24a4263
  25:   e8 6f 8a b1 ff  call   0xffb18a99
  2a:*  0f 0b   ud2 <-- trapping instruction
  2c:   5a  pop%rdx
  2d:   c9  leave
  2e:   31 c0   xor%eax,%eax
  30:   31 d2   xor%edx,%edx
  32:   31 c9   xor%ecx,%ecx
  34:   c3  ret
  35:   55  push   %rbp
  36:   89 c1   mov%eax,%ecx
  38:   89 d0   mov%edx,%eax
  3a:   c7 01 00 00 00 c0   movl   $0xc000,(%rcx)

Code starting with the faulting instruction
===
   0:   0f 0b   ud2
   2:   5a  pop%rdx
   3:   c9  leave
   4:   31 c0   xor%eax,%eax
   6:   31 d2   xor%edx,%edx
   8:   31 c9   xor%ecx,%ecx
   a:   c3  ret
   b:   55  push   %rbp
   c:   89 c1   mov%eax,%ecx
   e:   89 d0   mov%edx,%eax
  10:   c7 01 00 00 00 c0   movl   $0xc000,(%rcx)
[2.692770][T1] EAX:  EBX: e19ee0c4 ECX:  EDX: 
[2.693685][T1] ESI: e19ee0c0 EDI: c37ad880 EBP: c3767dd0 ESP: c3767dcc
[2.694597][T1] DS: 007b ES: 007b FS: 00d8 GS:  SS: 0068 EFLAGS: 
00010246
[2.695638][T1] CR0: 80050033 CR2: ffcb2000 CR3: 02723000 CR4: 00040690
[2.696557][T1] DR0: 0

[linux-next:master] BUILD REGRESSION 9c6ecb3cb6e20c4fd7997047213ba0efcf9ada1a

2024-05-02 Thread kernel test robot
tree/branch: 
https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
branch HEAD: 9c6ecb3cb6e20c4fd7997047213ba0efcf9ada1a  Add linux-next specific 
files for 20240502

Unverified Error/Warning (likely false positive, please contact us if 
interested):

drivers/gpu/drm/amd/amdgpu/../pm/swsmu/smu14/smu_v14_0.c:80:52: error: '%s' 
directive output may be truncated writing up to 29 bytes into a region of size 
23 [-Werror=format-truncation=]
{standard input}:898: Warning: overflow in branch to .L152; converted into 
longer instruction sequence

Error/Warning ids grouped by kconfigs:

gcc_recent_errors
|-- alpha-allyesconfig
|   |-- 
drivers-gpu-drm-amd-amdgpu-gmc_v12_0.c:warning:Function-parameter-or-struct-member-all_hub-not-described-in-gmc_v12_0_flush_gpu_tlb_pasid
|   |-- 
drivers-gpu-drm-amd-amdgpu-gmc_v12_0.c:warning:Function-parameter-or-struct-member-flush_type-not-described-in-gmc_v12_0_flush_gpu_tlb
|   |-- 
drivers-gpu-drm-amd-amdgpu-gmc_v12_0.c:warning:Function-parameter-or-struct-member-flush_type-not-described-in-gmc_v12_0_flush_gpu_tlb_pasid
|   |-- 
drivers-gpu-drm-amd-amdgpu-gmc_v12_0.c:warning:Function-parameter-or-struct-member-inst-not-described-in-gmc_v12_0_flush_gpu_tlb_pasid
|   |-- 
drivers-gpu-drm-amd-amdgpu-gmc_v12_0.c:warning:Function-parameter-or-struct-member-vmhub-not-described-in-gmc_v12_0_flush_gpu_tlb
|   |-- 
drivers-gpu-drm-amd-amdgpu-sdma_v7_0.c:warning:Excess-function-parameter-addr-description-in-sdma_v7_0_vm_write_pte
|   |-- 
drivers-gpu-drm-amd-amdgpu-sdma_v7_0.c:warning:Excess-function-parameter-fence-description-in-sdma_v7_0_ring_emit_fence
|   |-- 
drivers-gpu-drm-amd-amdgpu-sdma_v7_0.c:warning:Excess-function-parameter-flags-description-in-sdma_v7_0_vm_write_pte
|   |-- 
drivers-gpu-drm-amd-amdgpu-sdma_v7_0.c:warning:Excess-function-parameter-ib-description-in-sdma_v7_0_ring_emit_mem_sync
|   |-- 
drivers-gpu-drm-amd-amdgpu-sdma_v7_0.c:warning:Excess-function-parameter-job-description-in-sdma_v7_0_ring_emit_mem_sync
|   |-- 
drivers-gpu-drm-amd-amdgpu-sdma_v7_0.c:warning:Excess-function-parameter-ring-description-in-sdma_v7_0_emit_copy_buffer
|   |-- 
drivers-gpu-drm-amd-amdgpu-sdma_v7_0.c:warning:Excess-function-parameter-ring-description-in-sdma_v7_0_emit_fill_buffer
|   |-- 
drivers-gpu-drm-amd-amdgpu-sdma_v7_0.c:warning:Excess-function-parameter-vm-description-in-sdma_v7_0_ring_emit_vm_flush
|   |-- 
drivers-gpu-drm-amd-amdgpu-sdma_v7_0.c:warning:Function-parameter-or-struct-member-addr-not-described-in-sdma_v7_0_ring_emit_fence
|   |-- 
drivers-gpu-drm-amd-amdgpu-sdma_v7_0.c:warning:Function-parameter-or-struct-member-flags-not-described-in-sdma_v7_0_ring_emit_fence
|   |-- 
drivers-gpu-drm-amd-amdgpu-sdma_v7_0.c:warning:Function-parameter-or-struct-member-flags-not-described-in-sdma_v7_0_ring_emit_ib
|   |-- 
drivers-gpu-drm-amd-amdgpu-sdma_v7_0.c:warning:Function-parameter-or-struct-member-ib-not-described-in-sdma_v7_0_emit_copy_buffer
|   |-- 
drivers-gpu-drm-amd-amdgpu-sdma_v7_0.c:warning:Function-parameter-or-struct-member-ib-not-described-in-sdma_v7_0_emit_fill_buffer
|   |-- 
drivers-gpu-drm-amd-amdgpu-sdma_v7_0.c:warning:Function-parameter-or-struct-member-job-not-described-in-sdma_v7_0_ring_emit_ib
|   |-- 
drivers-gpu-drm-amd-amdgpu-sdma_v7_0.c:warning:Function-parameter-or-struct-member-pd_addr-not-described-in-sdma_v7_0_ring_emit_vm_flush
|   |-- 
drivers-gpu-drm-amd-amdgpu-sdma_v7_0.c:warning:Function-parameter-or-struct-member-ring-not-described-in-sdma_v7_0_ring_pad_ib
|   |-- 
drivers-gpu-drm-amd-amdgpu-sdma_v7_0.c:warning:Function-parameter-or-struct-member-seq-not-described-in-sdma_v7_0_ring_emit_fence
|   |-- 
drivers-gpu-drm-amd-amdgpu-sdma_v7_0.c:warning:Function-parameter-or-struct-member-timeout-not-described-in-sdma_v7_0_ring_test_ib
|   |-- 
drivers-gpu-drm-amd-amdgpu-sdma_v7_0.c:warning:Function-parameter-or-struct-member-value-not-described-in-sdma_v7_0_vm_write_pte
|   |-- 
drivers-gpu-drm-amd-amdgpu-sdma_v7_0.c:warning:Function-parameter-or-struct-member-vmid-not-described-in-sdma_v7_0_ring_emit_vm_flush
|   |-- 
drivers-gpu-drm-imx-ipuv3-imx-ldb.c:error:_sel-directive-output-may-be-truncated-writing-bytes-into-a-region-of-size-between-and
|   |-- 
drivers-gpu-drm-nouveau-nouveau_backlight.c:error:d-directive-output-may-be-truncated-writing-between-and-bytes-into-a-region-of-size
|   `-- drivers-usb-dwc3-core.c:warning:variable-hw_mode-set-but-not-used
|-- arc-allmodconfig
|   |-- 
drivers-gpu-drm-amd-amdgpu-gmc_v12_0.c:warning:Function-parameter-or-struct-member-all_hub-not-described-in-gmc_v12_0_flush_gpu_tlb_pasid
|   |-- 
drivers-gpu-drm-amd-amdgpu-gmc_v12_0.c:warning:Function-parameter-or-struct-member-flush_type-not-described-in-gmc_v12_0_flush_gpu_tlb
|   |-- 
drivers-gpu-drm-amd-amdgpu-gmc_v12_0.c:warning:Function-parameter-or-struct-member-flush_type-not-described-in-gmc_v12_0_flush_gpu_tlb_pasid
|   |-- 

[linux-next:master] BUILD REGRESSION d04466706db5e241ee026f17b5f920e50dee26b5

2024-04-30 Thread kernel test robot
tree/branch: 
https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
branch HEAD: d04466706db5e241ee026f17b5f920e50dee26b5  Add linux-next specific 
files for 20240430

Error/Warning reports:

https://lore.kernel.org/oe-kbuild-all/202404301738.j71xgyar-...@intel.com

Unverified Error/Warning (likely false positive, please contact us if 
interested):

drivers/virt/acrn/mm.c:217 acrn_vm_ram_map() error: uninitialized symbol 
'start_pfn'.
drivers/virt/acrn/mm.c:224 acrn_vm_ram_map() error: uninitialized symbol 'ret'.
net/ipv6/route.c:5712 rt6_fill_node() error: we previously assumed 'dst' could 
be null (see line 5697)

Error/Warning ids grouped by kconfigs:

gcc_recent_errors
|-- alpha-allyesconfig
|   `-- drivers-usb-dwc3-core.c:warning:variable-hw_mode-set-but-not-used
|-- arc-allmodconfig
|   `-- drivers-usb-dwc3-core.c:warning:variable-hw_mode-set-but-not-used
|-- arc-allyesconfig
|   `-- drivers-usb-dwc3-core.c:warning:variable-hw_mode-set-but-not-used
|-- arc-randconfig-r121-20240430
|   |-- 
drivers-hwmon-pmbus-xdp710.c:sparse:sparse:symbol-micro_ohm_rsense-was-not-declared.-Should-it-be-static
|   |-- 
fs-bcachefs-btree_cache.c:sparse:sparse:incorrect-type-in-assignment-(different-base-types)-expected-struct-task_struct-got-unsigned-long
|   `-- 
fs-ext4-orphan.c:sparse:sparse:incorrect-type-in-assignment-(different-base-types)-expected-restricted-__le32-_prev_-got-unsigned-long
|-- arc-randconfig-r122-20240430
|   |-- 
block-blk-mq.c:sparse:sparse:incorrect-type-in-argument-(different-base-types)-expected-unsigned-long-usertype-new-got-struct-request
|   |-- 
block-blk-mq.c:sparse:sparse:incorrect-type-in-argument-(different-base-types)-expected-unsigned-long-usertype-old-got-struct-request
|   |-- 
block-blk-mq.c:sparse:sparse:incorrect-type-in-assignment-(different-base-types)-expected-struct-request-got-unsigned-long
|   |-- 
drivers-dma-buf-dma-fence-chain.c:sparse:sparse:incorrect-type-in-argument-(different-base-types)-expected-unsigned-long-usertype-new-got-struct-dma_fence-noderef-__rcu
|   |-- 
drivers-dma-buf-dma-fence-chain.c:sparse:sparse:incorrect-type-in-argument-(different-base-types)-expected-unsigned-long-usertype-old-got-struct-dma_fence-noderef-__rcu
|   |-- 
drivers-dma-buf-dma-fence-chain.c:sparse:sparse:incorrect-type-in-assignment-(different-base-types)-expected-struct-dma_fence-noderef-__rcu-got-unsigned-long
|   |-- 
drivers-nvme-target-fabrics-cmd.c:sparse:sparse:incorrect-type-in-argument-(different-base-types)-expected-unsigned-long-usertype-new-got-struct-nvmet_ctrl
|   |-- 
drivers-nvme-target-fabrics-cmd.c:sparse:sparse:incorrect-type-in-argument-(different-base-types)-expected-unsigned-long-usertype-old-got-struct-nvmet_ctrl
|   |-- 
drivers-nvme-target-fabrics-cmd.c:sparse:sparse:incorrect-type-in-assignment-(different-base-types)-expected-struct-nvmet_ctrl-got-unsigned-long
|   |-- 
fs-btrfs-raid56.c:sparse:sparse:incorrect-type-in-argument-(different-base-types)-expected-unsigned-long-usertype-new-got-struct-btrfs_stripe_hash_table
|   |-- 
fs-btrfs-raid56.c:sparse:sparse:incorrect-type-in-argument-(different-base-types)-expected-unsigned-long-usertype-old-got-struct-btrfs_stripe_hash_table
|   |-- 
fs-btrfs-raid56.c:sparse:sparse:incorrect-type-in-assignment-(different-base-types)-expected-struct-btrfs_stripe_hash_table-got-unsigned-long
|   |-- 
fs-crypto-hooks.c:sparse:sparse:incorrect-type-in-argument-(different-base-types)-expected-unsigned-long-usertype-new-got-char
|   |-- 
fs-crypto-hooks.c:sparse:sparse:incorrect-type-in-argument-(different-base-types)-expected-unsigned-long-usertype-old-got-char
|   |-- 
fs-crypto-hooks.c:sparse:sparse:incorrect-type-in-assignment-(different-base-types)-expected-char-got-unsigned-long
|   |-- 
fs-crypto-keysetup.c:sparse:sparse:incorrect-type-in-argument-(different-base-types)-expected-unsigned-long-usertype-new-got-struct-fscrypt_inode_info
|   |-- 
fs-crypto-keysetup.c:sparse:sparse:incorrect-type-in-argument-(different-base-types)-expected-unsigned-long-usertype-old-got-struct-fscrypt_inode_info
|   |-- 
fs-crypto-keysetup.c:sparse:sparse:incorrect-type-in-assignment-(different-base-types)-expected-struct-fscrypt_inode_info-got-unsigned-long
|   |-- 
fs-debugfs-file.c:sparse:sparse:incorrect-type-in-argument-(different-base-types)-expected-unsigned-long-usertype-new-got-void
|   |-- 
fs-debugfs-file.c:sparse:sparse:incorrect-type-in-argument-(different-base-types)-expected-unsigned-long-usertype-old-got-void
|   |-- 
fs-debugfs-file.c:sparse:sparse:incorrect-type-in-assignment-(different-base-types)-expected-void-got-unsigned-long
|   |-- 
fs-ext4-orphan.c:sparse:sparse:incorrect-type-in-argument-(different-base-types)-expected-unsigned-long-usertype-new-got-restricted-__le32-_n_
|   |-- 
fs-ext4-orphan.c:sparse:sparse:incorrect-type-in-argument-(different-base-types)-expected-unsigned-long-usertype-old-got-restricted-__le32-_o_
|   |-- 

[linux-next:master] BUILD REGRESSION b0a2c79c6f3590b74742cbbc76687014d47972d8

2024-04-29 Thread kernel test robot
tree/branch: 
https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
branch HEAD: b0a2c79c6f3590b74742cbbc76687014d47972d8  Add linux-next specific 
files for 20240429

Error/Warning reports:

https://lore.kernel.org/oe-kbuild-all/20240429.kkvw8mvg-...@intel.com
https://lore.kernel.org/oe-kbuild-all/202404292317.uk7gvrsc-...@intel.com
https://lore.kernel.org/oe-kbuild-all/202404300248.dblz5vz7-...@intel.com

Error/Warning: (recently discovered and may have been fixed)

arch/arm64/boot/dts/ti/k3-am62a7-sk.dtb: syscon@4300: 'syscon@4008', 
'syscon@4018' do not match any of the regexes: '^chipid@[0-9a-f]+$', 
'^clock-controller@[0-9a-f]+$', '^mux-controller@[0-9a-f]+$', 'phy@[0-9a-f]+$', 
'pinctrl-[0-9]+'
make[4]: *** No rule to make target 
'arch/arm64/boot/dts/ti/k3-j784s4-evm-usxgmii-exp1-exp2.dtb', needed by 
'arch/arm64/boot/dts/ti/'.
make[4]: *** No rule to make target 
'arch/arm64/boot/dts/ti/k3-j784s4-evm-usxgmii-exp1-exp2.dtb', needed by 
'arch/arm64/boot/dts/ti/dtbs-list'.

Unverified Error/Warning (likely false positive, please contact us if 
interested):

{standard input}:2000: Error: unknown pseudo-op: `.lfe4886'

Error/Warning ids grouped by kconfigs:

gcc_recent_errors
|-- alpha-allyesconfig
|   `-- drivers-usb-dwc3-core.c:warning:variable-hw_mode-set-but-not-used
|-- arc-allmodconfig
|   `-- drivers-usb-dwc3-core.c:warning:variable-hw_mode-set-but-not-used
|-- arc-allyesconfig
|   `-- drivers-usb-dwc3-core.c:warning:variable-hw_mode-set-but-not-used
|-- arc-randconfig-001-20240429
|   `-- drivers-usb-dwc3-core.c:warning:variable-hw_mode-set-but-not-used
|-- arm-allmodconfig
|   `-- drivers-usb-dwc3-core.c:warning:variable-hw_mode-set-but-not-used
|-- arm-allyesconfig
|   `-- drivers-usb-dwc3-core.c:warning:variable-hw_mode-set-but-not-used
|-- arm64-defconfig
|   `-- drivers-usb-dwc3-core.c:warning:variable-hw_mode-set-but-not-used
|-- arm64-randconfig-r131-20230824
|   `-- 
make:No-rule-to-make-target-arch-arm64-boot-dts-ti-k3-j784s4-evm-usxgmii-exp1-exp2.dtb-needed-by-arch-arm64-boot-dts-ti-dtbs-list-.
|-- csky-allmodconfig
|   `-- drivers-usb-dwc3-core.c:warning:variable-hw_mode-set-but-not-used
|-- csky-allyesconfig
|   `-- drivers-usb-dwc3-core.c:warning:variable-hw_mode-set-but-not-used
|-- i386-allmodconfig
|   `-- drivers-usb-dwc3-core.c:warning:variable-hw_mode-set-but-not-used
|-- i386-allyesconfig
|   `-- drivers-usb-dwc3-core.c:warning:variable-hw_mode-set-but-not-used
|-- i386-buildonly-randconfig-005-20240429
|   `-- drivers-usb-dwc3-core.c:warning:variable-hw_mode-set-but-not-used
|-- i386-randconfig-141-20240429
|   |-- 
drivers-gpu-drm-bridge-cadence-cdns-mhdp8546-core.c-cdns_mhdp_atomic_enable()-warn:inconsistent-returns-mhdp-link_mutex-.
|   |-- 
drivers-pwm-core.c-pwm_put()-warn:variable-dereferenced-before-check-pwm-(see-line-)
|   `-- 
drivers-usb-typec-ucsi-ucsi.c-ucsi_get_pd_caps()-warn:passing-zero-to-ERR_PTR
|-- loongarch-allmodconfig
|   `-- drivers-usb-dwc3-core.c:warning:variable-hw_mode-set-but-not-used
|-- loongarch-randconfig-002-20240429
|   `-- drivers-usb-dwc3-core.c:warning:variable-hw_mode-set-but-not-used
|-- m68k-allmodconfig
|   `-- drivers-usb-dwc3-core.c:warning:variable-hw_mode-set-but-not-used
|-- m68k-allyesconfig
|   `-- drivers-usb-dwc3-core.c:warning:variable-hw_mode-set-but-not-used
|-- microblaze-allmodconfig
|   `-- drivers-usb-dwc3-core.c:warning:variable-hw_mode-set-but-not-used
|-- microblaze-allyesconfig
|   `-- drivers-usb-dwc3-core.c:warning:variable-hw_mode-set-but-not-used
|-- mips-allyesconfig
|   `-- drivers-usb-dwc3-core.c:warning:variable-hw_mode-set-but-not-used
|-- nios2-allmodconfig
|   `-- drivers-usb-dwc3-core.c:warning:variable-hw_mode-set-but-not-used
|-- nios2-allyesconfig
|   `-- drivers-usb-dwc3-core.c:warning:variable-hw_mode-set-but-not-used
|-- nios2-randconfig-001-20240429
|   `-- drivers-usb-dwc3-core.c:warning:variable-hw_mode-set-but-not-used
|-- nios2-randconfig-002-20240429
|   `-- drivers-usb-dwc3-core.c:warning:variable-hw_mode-set-but-not-used
|-- openrisc-allyesconfig
|   `-- drivers-usb-dwc3-core.c:warning:variable-hw_mode-set-but-not-used
|-- parisc-allmodconfig
|   `-- drivers-usb-dwc3-core.c:warning:variable-hw_mode-set-but-not-used
|-- parisc-allyesconfig
|   `-- drivers-usb-dwc3-core.c:warning:variable-hw_mode-set-but-not-used
|-- parisc-randconfig-002-20240429
|   `-- drivers-usb-dwc3-core.c:warning:variable-hw_mode-set-but-not-used
|-- powerpc-allmodconfig
|   `-- drivers-usb-dwc3-core.c:warning:variable-hw_mode-set-but-not-used
|-- powerpc-randconfig-002-20240429
|   |-- drivers-usb-dwc3-core.c:warning:variable-hw_mode-set-but-not-used
|   |-- 
powerpc-linux-ld:drivers-gpu-drm-amd-amdgpu-..-display-dc-dml-calcs-dcn_calc_auto.o-uses-hard-float-drivers-gpu-drm-amd-amdgpu-..-display-amdgpu_dm-amdgpu_dm_helpers.o-uses-soft-float
|   |-- 

[linux-next:master] BUILD REGRESSION bb7a2467e6beef44a80a17d45ebf2931e7631083

2024-04-26 Thread kernel test robot
tree/branch: 
https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
branch HEAD: bb7a2467e6beef44a80a17d45ebf2931e7631083  Add linux-next specific 
files for 20240426

Error/Warning reports:

https://lore.kernel.org/oe-kbuild-all/202404262217.dt4hoodh-...@intel.com

Error/Warning: (recently discovered and may have been fixed)

arch/riscv/mm/init.c:1495:25: error: 'MODULES_VADDR' undeclared (first use in 
this function)
arch/riscv/mm/init.c:1496:23: error: 'MODULES_END' undeclared (first use in 
this function)
drivers/gpu/drm/amd/amdgpu/../display/dc/dml2/dml21/src/dml2_dpmm/dml2_dpmm_dcn4.c:181:58:
 error: arithmetic between enumeration type 'enum dentist_divider_range' and 
floating-point type 'double' [-Werror,-Wenum-float-conversion]
drivers/gpu/drm/drm_mm.c:152:1: error: unused function 
'drm_mm_interval_tree_insert' [-Werror,-Wunused-function]
drivers/gpu/drm/drm_mm.c:152:1: error: unused function 
'drm_mm_interval_tree_iter_next' [-Werror,-Wunused-function]

Unverified Error/Warning (likely false positive, please contact us if 
interested):

ERROR: modpost: "add_preferred_console_match" 
[drivers/tty/serial/serial_base.ko] undefined!
ERROR: modpost: "pnp_bus_type" [drivers/tty/serial/serial_base.ko] undefined!
drivers/usb/dwc3/core.c:679:15: warning: variable 'hw_mode' set but not used 
[-Wunused-but-set-variable]

Error/Warning ids grouped by kconfigs:

gcc_recent_errors
|-- arc-allmodconfig
|   `-- drivers-usb-dwc3-core.c:warning:variable-hw_mode-set-but-not-used
|-- arc-allyesconfig
|   `-- drivers-usb-dwc3-core.c:warning:variable-hw_mode-set-but-not-used
|-- arm-allmodconfig
|   |-- 
drivers-gpu-drm-imx-ipuv3-imx-ldb.c:error:_sel-directive-output-may-be-truncated-writing-bytes-into-a-region-of-size-between-and
|   |-- 
drivers-gpu-drm-nouveau-nouveau_backlight.c:error:d-directive-output-may-be-truncated-writing-between-and-bytes-into-a-region-of-size
|   `-- drivers-usb-dwc3-core.c:warning:variable-hw_mode-set-but-not-used
|-- arm-allyesconfig
|   |-- 
drivers-gpu-drm-imx-ipuv3-imx-ldb.c:error:_sel-directive-output-may-be-truncated-writing-bytes-into-a-region-of-size-between-and
|   |-- 
drivers-gpu-drm-nouveau-nouveau_backlight.c:error:d-directive-output-may-be-truncated-writing-between-and-bytes-into-a-region-of-size
|   `-- drivers-usb-dwc3-core.c:warning:variable-hw_mode-set-but-not-used
|-- arm-randconfig-r111-20240426
|   `-- 
drivers-gpu-drm-panel-panel-lg-sw43408.c:sparse:sparse:symbol-sw43408_backlight_ops-was-not-declared.-Should-it-be-static
|-- arm-randconfig-r132-20240426
|   `-- drivers-usb-dwc3-core.c:warning:variable-hw_mode-set-but-not-used
|-- csky-allmodconfig
|   |-- 
drivers-gpu-drm-imx-ipuv3-imx-ldb.c:error:_sel-directive-output-may-be-truncated-writing-bytes-into-a-region-of-size-between-and
|   |-- 
drivers-gpu-drm-nouveau-nouveau_backlight.c:error:d-directive-output-may-be-truncated-writing-between-and-bytes-into-a-region-of-size
|   `-- drivers-usb-dwc3-core.c:warning:variable-hw_mode-set-but-not-used
|-- csky-allyesconfig
|   |-- 
drivers-gpu-drm-imx-ipuv3-imx-ldb.c:error:_sel-directive-output-may-be-truncated-writing-bytes-into-a-region-of-size-between-and
|   |-- 
drivers-gpu-drm-nouveau-nouveau_backlight.c:error:d-directive-output-may-be-truncated-writing-between-and-bytes-into-a-region-of-size
|   `-- drivers-usb-dwc3-core.c:warning:variable-hw_mode-set-but-not-used
|-- i386-allyesconfig
|   `-- drivers-usb-dwc3-core.c:warning:variable-hw_mode-set-but-not-used
|-- i386-randconfig-001-20240426
|   `-- drivers-usb-dwc3-core.c:warning:variable-hw_mode-set-but-not-used
|-- i386-randconfig-053-20240427
|   `-- drivers-usb-dwc3-core.c:warning:variable-hw_mode-set-but-not-used
|-- i386-randconfig-r121-20240426
|   |-- 
drivers-gpu-drm-panel-panel-lg-sw43408.c:(.text):undefined-reference-to-drm_dsc_pps_payload_pack
|   |-- 
drivers-gpu-drm-panel-panel-lg-sw43408.c:sparse:sparse:symbol-sw43408_backlight_ops-was-not-declared.-Should-it-be-static
|   `-- drivers-usb-dwc3-core.c:warning:variable-hw_mode-set-but-not-used
|-- loongarch-randconfig-r064-20231215
|   `-- ERROR:pnp_bus_type-drivers-tty-serial-serial_base.ko-undefined
|-- mips-allyesconfig
|   `-- drivers-usb-dwc3-core.c:warning:variable-hw_mode-set-but-not-used
|-- mips-randconfig-r064-20240427
|   `-- drivers-usb-dwc3-core.c:warning:variable-hw_mode-set-but-not-used
|-- nios2-allmodconfig
|   `-- drivers-usb-dwc3-core.c:warning:variable-hw_mode-set-but-not-used
|-- nios2-allyesconfig
|   `-- drivers-usb-dwc3-core.c:warning:variable-hw_mode-set-but-not-used
|-- nios2-randconfig-001-20240426
|   `-- drivers-usb-dwc3-core.c:warning:variable-hw_mode-set-but-not-used
|-- powerpc-randconfig-r061-20240427
|   `-- 
ERROR:drm_dsc_pps_payload_pack-drivers-gpu-drm-panel-panel-lg-sw43408.ko-undefined
|-- powerpc64-randconfig-001-20240426
|   `-- drivers-usb-dwc3-core.c:warning:variable-hw_mode-set-but-not-used
|-- powerpc64-randconfig-002-20240426
|   `-- 

Re: [PATCH v3 4/6] drm/i915/alpm: Add compute config for lobf

2024-04-26 Thread kernel test robot
Hi Animesh,

kernel test robot noticed the following build errors:

[auto build test ERROR on drm-intel/for-linux-next]
[also build test ERROR on drm-tip/drm-tip drm/drm-next 
drm-exynos/exynos-drm-next next-20240426]
[cannot apply to drm-intel/for-linux-next-fixes linus/master v6.9-rc5]
[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/Animesh-Manna/drm-i915-alpm-Move-alpm-parameters-from-intel_psr/20240425-025652
base:   git://anongit.freedesktop.org/drm-intel for-linux-next
patch link:
https://lore.kernel.org/r/20240424183820.3591593-5-animesh.manna%40intel.com
patch subject: [PATCH v3 4/6] drm/i915/alpm: Add compute config for lobf
config: loongarch-allmodconfig 
(https://download.01.org/0day-ci/archive/20240427/202404270117.qrlkmdn7-...@intel.com/config)
compiler: loongarch64-linux-gcc (GCC) 13.2.0
reproduce (this is a W=1 build): 
(https://download.01.org/0day-ci/archive/20240427/202404270117.qrlkmdn7-...@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 
| Closes: 
https://lore.kernel.org/oe-kbuild-all/202404270117.qrlkmdn7-...@intel.com/

All errors (new ones prefixed by >>, old ones prefixed by <<):

WARNING: modpost: missing MODULE_DESCRIPTION() in drivers/mtd/maps/map_funcs.o
WARNING: modpost: missing MODULE_DESCRIPTION() in 
drivers/spmi/hisi-spmi-controller.o
WARNING: modpost: missing MODULE_DESCRIPTION() in drivers/spmi/spmi-pmic-arb.o
WARNING: modpost: missing MODULE_DESCRIPTION() in drivers/uio/uio.o
WARNING: modpost: missing MODULE_DESCRIPTION() in drivers/uio/uio_cif.o
WARNING: modpost: missing MODULE_DESCRIPTION() in drivers/uio/uio_aec.o
WARNING: modpost: missing MODULE_DESCRIPTION() in drivers/uio/uio_netx.o
WARNING: modpost: missing MODULE_DESCRIPTION() in drivers/uio/uio_pruss.o
WARNING: modpost: missing MODULE_DESCRIPTION() in drivers/uio/uio_mf624.o
WARNING: modpost: missing MODULE_DESCRIPTION() in drivers/pcmcia/pcmcia_rsrc.o
WARNING: modpost: missing MODULE_DESCRIPTION() in drivers/pcmcia/yenta_socket.o
WARNING: modpost: missing MODULE_DESCRIPTION() in drivers/pcmcia/i82092.o
WARNING: modpost: missing MODULE_DESCRIPTION() in drivers/hwmon/corsair-cpro.o
WARNING: modpost: missing MODULE_DESCRIPTION() in drivers/hwmon/mr75203.o
WARNING: modpost: missing MODULE_DESCRIPTION() in drivers/vhost/vringh.o
WARNING: modpost: missing MODULE_DESCRIPTION() in drivers/greybus/greybus.o
WARNING: modpost: missing MODULE_DESCRIPTION() in drivers/greybus/gb-es2.o
WARNING: modpost: missing MODULE_DESCRIPTION() in drivers/rpmsg/rpmsg_char.o
WARNING: modpost: missing MODULE_DESCRIPTION() in drivers/iio/adc/ingenic-adc.o
WARNING: modpost: missing MODULE_DESCRIPTION() in drivers/iio/adc/xilinx-ams.o
WARNING: modpost: missing MODULE_DESCRIPTION() in drivers/iio/buffer/kfifo_buf.o
WARNING: modpost: missing MODULE_DESCRIPTION() in drivers/fsi/fsi-core.o
WARNING: modpost: missing MODULE_DESCRIPTION() in drivers/fsi/fsi-master-hub.o
WARNING: modpost: missing MODULE_DESCRIPTION() in 
drivers/fsi/fsi-master-aspeed.o
WARNING: modpost: missing MODULE_DESCRIPTION() in drivers/fsi/fsi-master-gpio.o
WARNING: modpost: missing MODULE_DESCRIPTION() in 
drivers/fsi/fsi-master-ast-cf.o
WARNING: modpost: missing MODULE_DESCRIPTION() in drivers/fsi/fsi-scom.o
WARNING: modpost: missing MODULE_DESCRIPTION() in drivers/siox/siox-bus-gpio.o
WARNING: modpost: missing MODULE_DESCRIPTION() in drivers/counter/ftm-quaddec.o
WARNING: modpost: missing MODULE_DESCRIPTION() in sound/core/snd-pcm-dmaengine.o
WARNING: modpost: missing MODULE_DESCRIPTION() in sound/core/sound_kunit.o
WARNING: modpost: missing MODULE_DESCRIPTION() in sound/drivers/snd-pcmtest.o
WARNING: modpost: missing MODULE_DESCRIPTION() in 
sound/pci/hda/snd-hda-cirrus-scodec-test.o
WARNING: modpost: missing MODULE_DESCRIPTION() in sound/soc/soc-topology-test.o
WARNING: modpost: missing MODULE_DESCRIPTION() in 
sound/soc/codecs/snd-soc-ab8500-codec.o
WARNING: modpost: missing MODULE_DESCRIPTION() in 
sound/soc/codecs/snd-soc-sigmadsp.o
WARNING: modpost: missing MODULE_DESCRIPTION() in 
sound/soc/codecs/snd-soc-wm-adsp.o
WARNING: modpost: missing MODULE_DESCRIPTION() in sound/soc/fsl/imx-pcm-dma.o
WARNING: modpost: missing MODULE_DESCRIPTION() in 
sound/soc/intel/avs/boards/snd-soc-avs-da7219.o
WARNING: modpost: missing MODULE_DESCRIPTION() in 
sound/soc/intel/avs/boards/snd-soc-avs-dmic.o
WARNING: modpost: missing MODULE_DESCRIPTION() in 
sound/soc/intel/avs/boards/snd-soc-avs-i2s-test.o
WARNING: modpost: missing MODULE_DESCRIPTION() in 
sound/soc/intel/avs/boards/snd-soc-avs-max98927.o
WARNING: modpost: missing MODULE_DESCRIPTION() in 
sound/soc/intel/avs/boards/snd-soc-avs-max98357a.o
WARNING: modp

Re: [PATCH v3 2/6] drm/i915/alpm: Move alpm related code to a new file

2024-04-26 Thread kernel test robot
Hi Animesh,

kernel test robot noticed the following build errors:

[auto build test ERROR on drm-intel/for-linux-next]
[also build test ERROR on drm/drm-next drm-exynos/exynos-drm-next next-20240424]
[cannot apply to drm-intel/for-linux-next-fixes linus/master v6.9-rc5]
[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/Animesh-Manna/drm-i915-alpm-Move-alpm-parameters-from-intel_psr/20240425-025652
base:   git://anongit.freedesktop.org/drm-intel for-linux-next
patch link:
https://lore.kernel.org/r/20240424183820.3591593-3-animesh.manna%40intel.com
patch subject: [PATCH v3 2/6] drm/i915/alpm: Move alpm related code to a new 
file
config: loongarch-allmodconfig 
(https://download.01.org/0day-ci/archive/20240426/202404261542.p0fckhhm-...@intel.com/config)
compiler: loongarch64-linux-gcc (GCC) 13.2.0
reproduce (this is a W=1 build): 
(https://download.01.org/0day-ci/archive/20240426/202404261542.p0fckhhm-...@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 
| Closes: 
https://lore.kernel.org/oe-kbuild-all/202404261542.p0fckhhm-...@intel.com/

All errors (new ones prefixed by >>, old ones prefixed by <<):

WARNING: modpost: missing MODULE_DESCRIPTION() in drivers/mtd/maps/map_funcs.o
WARNING: modpost: missing MODULE_DESCRIPTION() in 
drivers/spmi/hisi-spmi-controller.o
WARNING: modpost: missing MODULE_DESCRIPTION() in drivers/spmi/spmi-pmic-arb.o
WARNING: modpost: missing MODULE_DESCRIPTION() in drivers/uio/uio.o
WARNING: modpost: missing MODULE_DESCRIPTION() in drivers/uio/uio_cif.o
WARNING: modpost: missing MODULE_DESCRIPTION() in drivers/uio/uio_aec.o
WARNING: modpost: missing MODULE_DESCRIPTION() in drivers/uio/uio_netx.o
WARNING: modpost: missing MODULE_DESCRIPTION() in drivers/uio/uio_pruss.o
WARNING: modpost: missing MODULE_DESCRIPTION() in drivers/uio/uio_mf624.o
WARNING: modpost: missing MODULE_DESCRIPTION() in drivers/pcmcia/pcmcia_rsrc.o
WARNING: modpost: missing MODULE_DESCRIPTION() in drivers/pcmcia/yenta_socket.o
WARNING: modpost: missing MODULE_DESCRIPTION() in drivers/pcmcia/i82092.o
WARNING: modpost: missing MODULE_DESCRIPTION() in drivers/hwmon/corsair-cpro.o
WARNING: modpost: missing MODULE_DESCRIPTION() in drivers/hwmon/mr75203.o
WARNING: modpost: missing MODULE_DESCRIPTION() in drivers/vhost/vringh.o
WARNING: modpost: missing MODULE_DESCRIPTION() in drivers/greybus/greybus.o
WARNING: modpost: missing MODULE_DESCRIPTION() in drivers/greybus/gb-es2.o
WARNING: modpost: missing MODULE_DESCRIPTION() in drivers/rpmsg/rpmsg_char.o
WARNING: modpost: missing MODULE_DESCRIPTION() in drivers/iio/adc/ingenic-adc.o
WARNING: modpost: missing MODULE_DESCRIPTION() in drivers/iio/adc/xilinx-ams.o
WARNING: modpost: missing MODULE_DESCRIPTION() in drivers/iio/buffer/kfifo_buf.o
WARNING: modpost: missing MODULE_DESCRIPTION() in drivers/fsi/fsi-core.o
WARNING: modpost: missing MODULE_DESCRIPTION() in drivers/fsi/fsi-master-hub.o
WARNING: modpost: missing MODULE_DESCRIPTION() in 
drivers/fsi/fsi-master-aspeed.o
WARNING: modpost: missing MODULE_DESCRIPTION() in drivers/fsi/fsi-master-gpio.o
WARNING: modpost: missing MODULE_DESCRIPTION() in 
drivers/fsi/fsi-master-ast-cf.o
WARNING: modpost: missing MODULE_DESCRIPTION() in drivers/fsi/fsi-scom.o
WARNING: modpost: missing MODULE_DESCRIPTION() in drivers/siox/siox-bus-gpio.o
WARNING: modpost: missing MODULE_DESCRIPTION() in drivers/counter/ftm-quaddec.o
WARNING: modpost: missing MODULE_DESCRIPTION() in sound/core/snd-pcm-dmaengine.o
WARNING: modpost: missing MODULE_DESCRIPTION() in sound/core/sound_kunit.o
WARNING: modpost: missing MODULE_DESCRIPTION() in sound/drivers/snd-pcmtest.o
WARNING: modpost: missing MODULE_DESCRIPTION() in 
sound/pci/hda/snd-hda-cirrus-scodec-test.o
WARNING: modpost: missing MODULE_DESCRIPTION() in sound/soc/soc-topology-test.o
WARNING: modpost: missing MODULE_DESCRIPTION() in 
sound/soc/codecs/snd-soc-ab8500-codec.o
WARNING: modpost: missing MODULE_DESCRIPTION() in 
sound/soc/codecs/snd-soc-sigmadsp.o
WARNING: modpost: missing MODULE_DESCRIPTION() in 
sound/soc/codecs/snd-soc-wm-adsp.o
WARNING: modpost: missing MODULE_DESCRIPTION() in sound/soc/fsl/imx-pcm-dma.o
WARNING: modpost: missing MODULE_DESCRIPTION() in 
sound/soc/intel/avs/boards/snd-soc-avs-da7219.o
WARNING: modpost: missing MODULE_DESCRIPTION() in 
sound/soc/intel/avs/boards/snd-soc-avs-dmic.o
WARNING: modpost: missing MODULE_DESCRIPTION() in 
sound/soc/intel/avs/boards/snd-soc-avs-i2s-test.o
WARNING: modpost: missing MODULE_DESCRIPTION() in 
sound/soc/intel/avs/boards/snd-soc-avs-max98927.o
WARNING: modpost: missing MODULE_DESCRIPTION() in 
sound/soc/intel/avs/boards/snd-soc-avs-max98357a.o
WARNING: modp

[linux-next:master] BUILD REGRESSION 5e4f84f18c4ee9b0ccdc19e39b7de41df21699dd

2024-04-24 Thread kernel test robot
tree/branch: 
https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
branch HEAD: 5e4f84f18c4ee9b0ccdc19e39b7de41df21699dd  Add linux-next specific 
files for 20240424

Error/Warning reports:

https://lore.kernel.org/oe-kbuild-all/202404242144.8931hnhx-...@intel.com
https://lore.kernel.org/oe-kbuild-all/202404242330.fb2cmamd-...@intel.com
https://lore.kernel.org/oe-kbuild-all/202404242344.myso5vxe-...@intel.com
https://lore.kernel.org/oe-kbuild-all/202404250156.2pqrwmex-...@intel.com
https://lore.kernel.org/oe-kbuild-all/202404250209.hmhcgegb-...@intel.com
https://lore.kernel.org/oe-kbuild-all/202404250552.gnss0wy7-...@intel.com
https://lore.kernel.org/oe-kbuild-all/202404250558.hmgiruu0-...@intel.com

Error/Warning: (recently discovered and may have been fixed)

/usr/bin/ld: pse_core.c:(.text+0x72): undefined reference to `rdev_get_id'
ERROR: modpost: "__spi_register_driver" [drivers/iio/dac/ad9739a.ko] undefined!
ERROR: modpost: "spi_async" [drivers/base/regmap/regmap-spi.ko] undefined!
ERROR: modpost: "spi_sync" [drivers/base/regmap/regmap-spi.ko] undefined!
ERROR: modpost: "spi_write_then_read" [drivers/base/regmap/regmap-spi.ko] 
undefined!
WARNING: modpost: vmlinux: section mismatch in reference: dentry_name+0x7c 
(section: .text) -> .LVL1195 (section: .init.text)
WARNING: modpost: vmlinux: section mismatch in reference: fwnode_string+0x230 
(section: .text) -> .LVL1131 (section: .init.text)
drivers/gpu/drm/amd/amdgpu/gfx_v9_4_3.c:379:52: error: '%s' directive output 
may be truncated writing up to 29 bytes into a region of size 23 
[-Werror=format-truncation=]
drivers/gpu/drm/amd/amdgpu/gfx_v9_4_3.c:379:52: warning: '%s' directive output 
may be truncated writing up to 29 bytes into a region of size 23 
[-Wformat-truncation=]
kismet: WARNING: unmet direct dependencies detected for REGMAP_SPI when 
selected by AD9739A
powerpc-linux-ld: 
drivers/gpu/drm/amd/amdgpu/../display/dc/dml/dcn401/dcn401_fpu.o uses hard 
float, drivers/gpu/drm/amd/amdgpu/../display/amdgpu_dm/amdgpu_dm_helpers.o uses 
soft float
powerpc-linux-ld: 
drivers/gpu/drm/amd/amdgpu/../display/dc/dml2/dml21/dml21_translation_helper.o 
uses hard float, 
drivers/gpu/drm/amd/amdgpu/../display/amdgpu_dm/amdgpu_dm_helpers.o uses soft 
float
powerpc-linux-ld: 
drivers/gpu/drm/amd/amdgpu/../display/dc/dml2/dml21/dml21_utils.o uses hard 
float, drivers/gpu/drm/amd/amdgpu/../display/amdgpu_dm/amdgpu_dm_helpers.o uses 
soft float
powerpc-linux-ld: 
drivers/gpu/drm/amd/amdgpu/../display/dc/dml2/dml21/src/dml2_core/dml2_core_dcn4.o
 uses hard float, 
drivers/gpu/drm/amd/amdgpu/../display/amdgpu_dm/amdgpu_dm_helpers.o uses soft 
float
powerpc-linux-ld: 
drivers/gpu/drm/amd/amdgpu/../display/dc/dml2/dml21/src/dml2_core/dml2_core_dcn4_calcs.o
 uses hard float, 
drivers/gpu/drm/amd/amdgpu/../display/amdgpu_dm/amdgpu_dm_helpers.o uses soft 
float
powerpc-linux-ld: 
drivers/gpu/drm/amd/amdgpu/../display/dc/dml2/dml21/src/dml2_core/dml2_core_shared.o
 uses hard float, 
drivers/gpu/drm/amd/amdgpu/../display/amdgpu_dm/amdgpu_dm_helpers.o uses soft 
float
powerpc-linux-ld: 
drivers/gpu/drm/amd/amdgpu/../display/dc/dml2/dml21/src/dml2_dpmm/dml2_dpmm_dcn4.o
 uses hard float, 
drivers/gpu/drm/amd/amdgpu/../display/amdgpu_dm/amdgpu_dm_helpers.o uses soft 
float
powerpc-linux-ld: 
drivers/gpu/drm/amd/amdgpu/../display/dc/dml2/dml21/src/dml2_mcg/dml2_mcg_dcn4.o
 uses hard float, 
drivers/gpu/drm/amd/amdgpu/../display/amdgpu_dm/amdgpu_dm_helpers.o uses soft 
float
powerpc-linux-ld: 
drivers/gpu/drm/amd/amdgpu/../display/dc/dml2/dml21/src/dml2_pmo/dml2_pmo_dcn3.o
 uses hard float, 
drivers/gpu/drm/amd/amdgpu/../display/amdgpu_dm/amdgpu_dm_helpers.o uses soft 
float
powerpc-linux-ld: 
drivers/gpu/drm/amd/amdgpu/../display/dc/dml2/dml21/src/dml2_pmo/dml2_pmo_dcn4.o
 uses hard float, 
drivers/gpu/drm/amd/amdgpu/../display/amdgpu_dm/amdgpu_dm_helpers.o uses soft 
float
powerpc-linux-ld: 
drivers/gpu/drm/amd/amdgpu/../display/dc/dml2/dml21/src/dml2_pmo/dml2_pmo_dcn4_fams2.o
 uses hard float, 
drivers/gpu/drm/amd/amdgpu/../display/amdgpu_dm/amdgpu_dm_helpers.o uses soft 
float
powerpc-linux-ld: 
drivers/gpu/drm/amd/amdgpu/../display/dc/dml2/dml21/src/dml2_standalone_libraries/lib_float_math.o
 uses hard float, 
drivers/gpu/drm/amd/amdgpu/../display/amdgpu_dm/amdgpu_dm_helpers.o uses soft 
float
powerpc-linux-ld: 
drivers/gpu/drm/amd/amdgpu/../display/dc/dml2/dml21/src/dml2_top/dml_top_mcache.o
 uses hard float, 
drivers/gpu/drm/amd/amdgpu/../display/amdgpu_dm/amdgpu_dm_helpers.o uses soft 
float
powerpc-linux-ld: drivers/gpu/drm/amd/display/dc/dml/dcn401/dcn401_fpu.o uses 
hard float, arch/powerpc/kernel/udbg.o uses soft float
powerpc-linux-ld: 
drivers/gpu/drm/amd/display/dc/dml2/dml21/dml21_translation_helper.o uses hard 
float, arch/powerpc/kernel/udbg.o uses soft float
powerpc-linux-ld: drivers/gpu/drm/amd/display/dc/dml2/dml21/dml21_utils.o uses 
hard float, arch/powerpc/kernel/udbg.o uses soft float
powerpc-linux-ld: 

[linux-next:master] BUILD REGRESSION a59668a9397e7245b26e9be85d23f242ff757ae8

2024-04-23 Thread kernel test robot
tree/branch: 
https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
branch HEAD: a59668a9397e7245b26e9be85d23f242ff757ae8  Add linux-next specific 
files for 20240423

Error/Warning reports:

https://lore.kernel.org/oe-kbuild-all/202404231839.ohiy9lw8-...@intel.com

Error/Warning: (recently discovered and may have been fixed)

WARNING: modpost: vmlinux: section mismatch in reference: 
__io_uring_register+0x4e (section: .text) -> .L443 (section: .init.text)
WARNING: modpost: vmlinux: section mismatch in reference: add_master_key+0xcc 
(section: .text) -> .L443 (section: .init.text)
WARNING: modpost: vmlinux: section mismatch in reference: address_val+0x172 
(section: .text) -> .L443 (section: .init.text)
WARNING: modpost: vmlinux: section mismatch in reference: affine_move_task+0x7c 
(section: .text) -> .L443 (section: .init.text)
WARNING: modpost: vmlinux: section mismatch in reference: bcma_pmu_init+0x11c 
(section: .text) -> .LBE2162 (section: .init.text)
WARNING: modpost: vmlinux: section mismatch in reference: 
bitmap_list_string.isra.0+0x176 (section: .text) -> .L498 (section: .init.text)
WARNING: modpost: vmlinux: section mismatch in reference: 
bpf_cgroup_link_fill_link_info+0x18 (section: .text) -> .LBE2191 (section: 
.init.text)
WARNING: modpost: vmlinux: section mismatch in reference: 
bpf_map_meta_alloc+0x68 (section: .text) -> .L443 (section: .init.text)
WARNING: modpost: vmlinux: section mismatch in reference: bstr_printf+0x4c 
(section: .text) -> .L443 (section: .init.text)
WARNING: modpost: vmlinux: section mismatch in reference: 
cgroup1_reconfigure+0x6a (section: .text) -> .LBE2191 (section: .init.text)
WARNING: modpost: vmlinux: section mismatch in reference: 
cgroup_bpf_replace+0x18 (section: .text) -> .LBE2191 (section: .init.text)
WARNING: modpost: vmlinux: section mismatch in reference: 
class_srcu_destructor.isra.0+0x44 (section: .text) -> .L443 (section: 
.init.text)
WARNING: modpost: vmlinux: section mismatch in reference: 
cpu_cluster_pm_enter+0x36 (section: .text) -> .LBB2191 (section: .init.text)
WARNING: modpost: vmlinux: section mismatch in reference: dma_direct_mmap+0xf2 
(section: .text) -> .LVL129 (section: .init.text)
WARNING: modpost: vmlinux: section mismatch in reference: 
drm_atomic_helper_check_plane_state+0x80 (section: .text) -> .L443 (section: 
.init.text)
WARNING: modpost: vmlinux: section mismatch in reference: 
drm_crtc_vblank_helper_get_vblank_timestamp_internal+0x228 (section: .text) -> 
.LBE1217 (section: .init.text)
WARNING: modpost: vmlinux: section mismatch in reference: 
drm_of_component_probe+0xec (section: .text) -> .LVL1112 (section: .init.text)
WARNING: modpost: vmlinux: section mismatch in reference: 
drm_test_rect_rotate_inv+0x3c (section: .text) -> .LVL1139 (section: .init.text)
WARNING: modpost: vmlinux: section mismatch in reference: 
dw_hdmi_bridge_atomic_get_output_bus_fmts+0x80 (section: .text) -> .L443 
(section: .init.text)
WARNING: modpost: vmlinux: section mismatch in reference: 
gpiod_direction_input.part.0+0x2a (section: .text) -> .LVL1117 (section: 
.init.text)
WARNING: modpost: vmlinux: section mismatch in reference: 
gpiod_direction_output_raw_commit+0x40 (section: .text) -> .LVL1117 (section: 
.init.text)
WARNING: modpost: vmlinux: section mismatch in reference: 
gpiod_find_and_request+0x4e (section: .text) -> .LVL1117 (section: .init.text)
WARNING: modpost: vmlinux: section mismatch in reference: 
gpiod_get_direction+0x4e (section: .text) -> .L443 (section: .init.text)
WARNING: modpost: vmlinux: section mismatch in reference: gpiod_to_irq+0x48 
(section: .text) -> .L443 (section: .init.text)
WARNING: modpost: vmlinux: section mismatch in reference: 
gpiolib_seq_start+0x32 (section: .text) -> .L443 (section: .init.text)
WARNING: modpost: vmlinux: section mismatch in reference: gpiolib_seq_stop+0x4e 
(section: .text) -> .L443 (section: .init.text)
WARNING: modpost: vmlinux: section mismatch in reference: 
handle_new_recv_msgs+0x23a (section: .text) -> .LVL1117 (section: .init.text)
WARNING: modpost: vmlinux: section mismatch in reference: 
iio_compute_scan_bytes+0x5e (section: .text) -> .LVL1049 (section: .init.text)
WARNING: modpost: vmlinux: section mismatch in reference: 
iio_dev_attr_in_accel_scale_available+0x14 (section: .data) -> .LVL793 
(section: .init.text)
WARNING: modpost: vmlinux: section mismatch in reference: 
ipmi_get_maintenance_mode+0x8a (section: .text) -> .L443 (section: .init.text)
WARNING: modpost: vmlinux: section mismatch in reference: ipmi_get_my_LUN+0x82 
(section: .text) -> .L443 (section: .init.text)
WARNING: modpost: vmlinux: section mismatch in reference: 
ipmi_get_smi_info+0x32 (section: .text) -> .LVL1117 (section: .init.text)
WARNING: modpost: vmlinux: section mismatch in reference: 
ipmi_set_my_address+0x82 (section: .text) -> .L443 (section: .init.text)
WARNING: modpost: vmlinux: section mismatch in reference: ipmi_timeout+0x6c 
(section: .text) -> .LVL1117 (section: .init.text)

[linux-next:master] BUILD REGRESSION f529a6d274b3b8c75899e949649d231298f30a32

2024-04-22 Thread kernel test robot
tree/branch: 
https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
branch HEAD: f529a6d274b3b8c75899e949649d231298f30a32  Add linux-next specific 
files for 20240422

Error/Warning reports:

https://lore.kernel.org/oe-kbuild-all/202404221830.cjqlhldl-...@intel.com

Error/Warning: (recently discovered and may have been fixed)

csky-linux-ld: drivers/net/pse-pd/pse_core.c:220:(.text+0x84): undefined 
reference to `rdev_get_id'
csky-linux-ld: drivers/net/pse-pd/pse_core.c:246:(.text+0x19c): undefined 
reference to `rdev_get_drvdata'
csky-linux-ld: drivers/net/pse-pd/pse_core.c:351:(.text+0x6e8): undefined 
reference to `devm_regulator_register'
drivers/net/pse-pd/pse_core.c:212:(.text+0x70): undefined reference to 
`rdev_get_drvdata'
drivers/net/pse-pd/pse_core.c:308:(.text+0x68a): undefined reference to 
`devm_regulator_register'
nios2-linux-ld: pse_core.c:(.text+0x64): undefined reference to `rdev_get_id'
powerpc-linux-ld: warning: orphan section `.bss..Lubsan_data373' from 
`kernel/ptrace.o' being placed in section `.bss..Lubsan_data373'
pse_core.c:(.text+0x4c): relocation truncated to fit: R_NIOS2_CALL26 against 
`rdev_get_drvdata'
pse_core.c:(.text+0x4c): undefined reference to `rdev_get_drvdata'
pse_core.c:(.text+0x64): relocation truncated to fit: R_NIOS2_CALL26 against 
`rdev_get_id'
pse_core.c:(.text+0xddc): relocation truncated to fit: R_NIOS2_CALL26 against 
`devm_regulator_register'
pse_core.c:(.text+0xddc): undefined reference to `devm_regulator_register'
s390-linux-ld: drivers/net/pse-pd/pse_core.c:220:(.text+0xfa): undefined 
reference to `rdev_get_id'

Unverified Error/Warning (likely false positive, please contact us if 
interested):

WARNING: modpost: "strcat" [lib/string_kunit.ko] has no CRC!
WARNING: modpost: "strncat" [lib/string_kunit.ko] has no CRC!
drivers/spmi/spmi-pmic-arb.c:1782 spmi_pmic_arb_register_buses() error: 
uninitialized symbol 'ret'.
drivers/staging/vc04_services/interface/vchiq_arm/vchiq_arm.c:1109 
service_callback() warn: variable dereferenced before check 'instance' (see 
line 1091)

Error/Warning ids grouped by kconfigs:

gcc_recent_errors
|-- alpha-allyesconfig
|   |-- 
drivers-gpu-drm-imx-ipuv3-imx-ldb.c:error:_sel-directive-output-may-be-truncated-writing-bytes-into-a-region-of-size-between-and
|   `-- 
drivers-gpu-drm-nouveau-nouveau_backlight.c:error:d-directive-output-may-be-truncated-writing-between-and-bytes-into-a-region-of-size
|-- alpha-randconfig-r022-20230114
|   `-- WARNING:modpost:strcat-lib-string_kunit.ko-has-no-CRC
|-- alpha-randconfig-s032-20220304
|   `-- WARNING:modpost:strncat-lib-string_kunit.ko-has-no-CRC
|-- arm-allmodconfig
|   |-- 
drivers-gpu-drm-imx-ipuv3-imx-ldb.c:error:_sel-directive-output-may-be-truncated-writing-bytes-into-a-region-of-size-between-and
|   `-- 
drivers-gpu-drm-nouveau-nouveau_backlight.c:error:d-directive-output-may-be-truncated-writing-between-and-bytes-into-a-region-of-size
|-- arm-allyesconfig
|   |-- 
drivers-gpu-drm-imx-ipuv3-imx-ldb.c:error:_sel-directive-output-may-be-truncated-writing-bytes-into-a-region-of-size-between-and
|   `-- 
drivers-gpu-drm-nouveau-nouveau_backlight.c:error:d-directive-output-may-be-truncated-writing-between-and-bytes-into-a-region-of-size
|-- csky-allmodconfig
|   |-- 
drivers-gpu-drm-imx-ipuv3-imx-ldb.c:error:_sel-directive-output-may-be-truncated-writing-bytes-into-a-region-of-size-between-and
|   `-- 
drivers-gpu-drm-nouveau-nouveau_backlight.c:error:d-directive-output-may-be-truncated-writing-between-and-bytes-into-a-region-of-size
|-- csky-allyesconfig
|   |-- 
drivers-gpu-drm-imx-ipuv3-imx-ldb.c:error:_sel-directive-output-may-be-truncated-writing-bytes-into-a-region-of-size-between-and
|   `-- 
drivers-gpu-drm-nouveau-nouveau_backlight.c:error:d-directive-output-may-be-truncated-writing-between-and-bytes-into-a-region-of-size
|-- csky-buildonly-randconfig-r001-20230308
|   |-- 
csky-linux-ld:drivers-net-pse-pd-pse_core.c:(.text):undefined-reference-to-devm_regulator_register
|   |-- 
csky-linux-ld:drivers-net-pse-pd-pse_core.c:(.text):undefined-reference-to-rdev_get_drvdata
|   |-- 
csky-linux-ld:drivers-net-pse-pd-pse_core.c:(.text):undefined-reference-to-rdev_get_id
|   |-- 
drivers-net-pse-pd-pse_core.c:(.text):undefined-reference-to-devm_regulator_register
|   `-- 
drivers-net-pse-pd-pse_core.c:(.text):undefined-reference-to-rdev_get_drvdata
|-- i386-randconfig-141-20240422
|   `-- 
drivers-gpu-drm-bridge-cadence-cdns-mhdp8546-core.c-cdns_mhdp_atomic_enable()-warn:inconsistent-returns-mhdp-link_mutex-.
|-- loongarch-allmodconfig
|   |-- 
drivers-gpu-drm-imx-ipuv3-imx-ldb.c:error:_sel-directive-output-may-be-truncated-writing-bytes-into-a-region-of-size-between-and
|   `-- 
drivers-gpu-drm-nouveau-nouveau_backlight.c:error:d-directive-output-may-be-truncated-writing-between-and-bytes-into-a-region-of-size
|-- microblaze-allmodconfig
|   |-- 

[linux-next:master] BUILD REGRESSION a35e92ef04c07bd473404b9b73d489aea19a60a8

2024-04-19 Thread kernel test robot
tree/branch: 
https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
branch HEAD: a35e92ef04c07bd473404b9b73d489aea19a60a8  Add linux-next specific 
files for 20240419

Error/Warning: (recently discovered and may have been fixed)

WARNING: modpost: vmlinux: section mismatch in reference: 
__io_uring_register+0x4e (section: .text) -> .L443 (section: .init.text)
WARNING: modpost: vmlinux: section mismatch in reference: add_master_key+0xcc 
(section: .text) -> .L443 (section: .init.text)
WARNING: modpost: vmlinux: section mismatch in reference: address_val+0x172 
(section: .text) -> .L443 (section: .init.text)
WARNING: modpost: vmlinux: section mismatch in reference: affine_move_task+0x7c 
(section: .text) -> .L443 (section: .init.text)
WARNING: modpost: vmlinux: section mismatch in reference: bcma_pmu_init+0x11c 
(section: .text) -> .LBE2162 (section: .init.text)
WARNING: modpost: vmlinux: section mismatch in reference: 
bitmap_list_string.isra.0+0x176 (section: .text) -> .L498 (section: .init.text)
WARNING: modpost: vmlinux: section mismatch in reference: 
bpf_cgroup_link_fill_link_info+0x18 (section: .text) -> .LBE2191 (section: 
.init.text)
WARNING: modpost: vmlinux: section mismatch in reference: 
bpf_map_meta_alloc+0x68 (section: .text) -> .L443 (section: .init.text)
WARNING: modpost: vmlinux: section mismatch in reference: bstr_printf+0x4c 
(section: .text) -> .L443 (section: .init.text)
WARNING: modpost: vmlinux: section mismatch in reference: 
cgroup1_reconfigure+0x6a (section: .text) -> .LBE2191 (section: .init.text)
WARNING: modpost: vmlinux: section mismatch in reference: 
cgroup_bpf_replace+0x18 (section: .text) -> .LBE2191 (section: .init.text)
WARNING: modpost: vmlinux: section mismatch in reference: 
class_srcu_destructor.isra.0+0x44 (section: .text) -> .L443 (section: 
.init.text)
WARNING: modpost: vmlinux: section mismatch in reference: 
cpu_cluster_pm_enter+0x36 (section: .text) -> .LBB2191 (section: .init.text)
WARNING: modpost: vmlinux: section mismatch in reference: dma_direct_mmap+0xf2 
(section: .text) -> .LVL129 (section: .init.text)
WARNING: modpost: vmlinux: section mismatch in reference: 
drm_atomic_helper_check_plane_state+0x80 (section: .text) -> .L443 (section: 
.init.text)
WARNING: modpost: vmlinux: section mismatch in reference: 
drm_crtc_vblank_helper_get_vblank_timestamp_internal+0x228 (section: .text) -> 
.LBE1217 (section: .init.text)
WARNING: modpost: vmlinux: section mismatch in reference: 
drm_of_component_probe+0xec (section: .text) -> .LVL1112 (section: .init.text)
WARNING: modpost: vmlinux: section mismatch in reference: 
drm_test_rect_rotate_inv+0x3c (section: .text) -> .LVL1139 (section: .init.text)
WARNING: modpost: vmlinux: section mismatch in reference: 
dw_hdmi_bridge_atomic_get_output_bus_fmts+0x80 (section: .text) -> .L443 
(section: .init.text)
WARNING: modpost: vmlinux: section mismatch in reference: 
gpiod_direction_input.part.0+0x2a (section: .text) -> .LVL1117 (section: 
.init.text)
WARNING: modpost: vmlinux: section mismatch in reference: 
gpiod_direction_output_raw_commit+0x40 (section: .text) -> .LVL1117 (section: 
.init.text)
WARNING: modpost: vmlinux: section mismatch in reference: 
gpiod_find_and_request+0x4e (section: .text) -> .LVL1117 (section: .init.text)
WARNING: modpost: vmlinux: section mismatch in reference: 
gpiod_get_direction+0x4e (section: .text) -> .L443 (section: .init.text)
WARNING: modpost: vmlinux: section mismatch in reference: gpiod_to_irq+0x48 
(section: .text) -> .L443 (section: .init.text)
WARNING: modpost: vmlinux: section mismatch in reference: 
gpiolib_seq_start+0x32 (section: .text) -> .L443 (section: .init.text)
WARNING: modpost: vmlinux: section mismatch in reference: gpiolib_seq_stop+0x4e 
(section: .text) -> .L443 (section: .init.text)
WARNING: modpost: vmlinux: section mismatch in reference: 
handle_new_recv_msgs+0x23a (section: .text) -> .LVL1117 (section: .init.text)
WARNING: modpost: vmlinux: section mismatch in reference: 
iio_compute_scan_bytes+0x5e (section: .text) -> .LVL1049 (section: .init.text)
WARNING: modpost: vmlinux: section mismatch in reference: 
iio_dev_attr_in_accel_scale_available+0x14 (section: .data) -> .LVL793 
(section: .init.text)
WARNING: modpost: vmlinux: section mismatch in reference: 
ipmi_get_maintenance_mode+0x8a (section: .text) -> .L443 (section: .init.text)
WARNING: modpost: vmlinux: section mismatch in reference: ipmi_get_my_LUN+0x82 
(section: .text) -> .L443 (section: .init.text)
WARNING: modpost: vmlinux: section mismatch in reference: 
ipmi_get_smi_info+0x32 (section: .text) -> .LVL1117 (section: .init.text)
WARNING: modpost: vmlinux: section mismatch in reference: 
ipmi_set_my_address+0x82 (section: .text) -> .L443 (section: .init.text)
WARNING: modpost: vmlinux: section mismatch in reference: ipmi_timeout+0x6c 
(section: .text) -> .LVL1117 (section: .init.text)
WARNING: modpost: vmlinux: section mismatch in reference: 
lm3533_ctrlbank_get_brightness+0x26 

[linux-next:master] BUILD REGRESSION 7b4f2bc91c15fdcf948bb2d9741a9d7d54303f8d

2024-04-18 Thread kernel test robot
tree/branch: 
https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
branch HEAD: 7b4f2bc91c15fdcf948bb2d9741a9d7d54303f8d  Add linux-next specific 
files for 20240418

Error/Warning reports:

https://lore.kernel.org/oe-kbuild-all/202404190103.llm8ltup-...@intel.com

Error/Warning: (recently discovered and may have been fixed)

kismet: WARNING: unmet direct dependencies detected for 
PHY_FSL_SAMSUNG_HDMI_PHY when selected by DRM_IMX8MP_DW_HDMI_BRIDGE

Unverified Error/Warning (likely false positive, please contact us if 
interested):

mseal_test.c:84:59: warning: format specifies type 'char *' but the argument 
has type 'char (*)[5]' [-Wformat]

Error/Warning ids grouped by kconfigs:

gcc_recent_errors
|-- alpha-allyesconfig
|   |-- 
drivers-gpu-drm-imx-ipuv3-imx-ldb.c:error:_sel-directive-output-may-be-truncated-writing-bytes-into-a-region-of-size-between-and
|   `-- 
drivers-gpu-drm-nouveau-nouveau_backlight.c:error:d-directive-output-may-be-truncated-writing-between-and-bytes-into-a-region-of-size
|-- arc-allmodconfig
|   `-- 
arch-arc-include-asm-cmpxchg.h:error:implicit-declaration-of-function-cmpxchg_emu_u8
|-- arc-allnoconfig
|   `-- 
arch-arc-include-asm-cmpxchg.h:error:implicit-declaration-of-function-cmpxchg_emu_u8
|-- arc-allyesconfig
|   `-- 
arch-arc-include-asm-cmpxchg.h:error:implicit-declaration-of-function-cmpxchg_emu_u8
|-- arc-defconfig
|   `-- 
arch-arc-include-asm-cmpxchg.h:error:implicit-declaration-of-function-cmpxchg_emu_u8
|-- arc-randconfig-001-20240418
|   `-- 
arch-arc-include-asm-cmpxchg.h:error:implicit-declaration-of-function-cmpxchg_emu_u8
|-- arc-randconfig-002-20240418
|   `-- 
arch-arc-include-asm-cmpxchg.h:error:implicit-declaration-of-function-cmpxchg_emu_u8
|-- arc-randconfig-r112-20240418
|   `-- 
arch-arc-include-asm-cmpxchg.h:error:implicit-declaration-of-function-cmpxchg_emu_u8
|-- arc-randconfig-r131-20240418
|   `-- 
arch-arc-include-asm-cmpxchg.h:error:implicit-declaration-of-function-cmpxchg_emu_u8
|-- arc-randconfig-r132-20240418
|   `-- 
arch-arc-include-asm-cmpxchg.h:error:implicit-declaration-of-function-cmpxchg_emu_u8
|-- arc-vdk_hs38_smp_defconfig
|   `-- 
arch-arc-include-asm-cmpxchg.h:error:implicit-declaration-of-function-cmpxchg_emu_u8
|-- arm-allmodconfig
|   |-- 
drivers-gpu-drm-imx-ipuv3-imx-ldb.c:error:_sel-directive-output-may-be-truncated-writing-bytes-into-a-region-of-size-between-and
|   `-- 
drivers-gpu-drm-nouveau-nouveau_backlight.c:error:d-directive-output-may-be-truncated-writing-between-and-bytes-into-a-region-of-size
|-- arm-allyesconfig
|   |-- 
drivers-gpu-drm-imx-ipuv3-imx-ldb.c:error:_sel-directive-output-may-be-truncated-writing-bytes-into-a-region-of-size-between-and
|   `-- 
drivers-gpu-drm-nouveau-nouveau_backlight.c:error:d-directive-output-may-be-truncated-writing-between-and-bytes-into-a-region-of-size
|-- csky-allmodconfig
|   |-- 
drivers-gpu-drm-imx-ipuv3-imx-ldb.c:error:_sel-directive-output-may-be-truncated-writing-bytes-into-a-region-of-size-between-and
|   `-- 
drivers-gpu-drm-nouveau-nouveau_backlight.c:error:d-directive-output-may-be-truncated-writing-between-and-bytes-into-a-region-of-size
|-- csky-allyesconfig
|   |-- 
drivers-gpu-drm-imx-ipuv3-imx-ldb.c:error:_sel-directive-output-may-be-truncated-writing-bytes-into-a-region-of-size-between-and
|   `-- 
drivers-gpu-drm-nouveau-nouveau_backlight.c:error:d-directive-output-may-be-truncated-writing-between-and-bytes-into-a-region-of-size
|-- i386-randconfig-141-20240418
|   |-- 
drivers-dma-fsl-edma-main.c-fsl_edma_xlate()-warn:inconsistent-returns-fsl_edma-fsl_edma_mutex-.
|   |-- 
drivers-gpu-drm-bridge-cadence-cdns-mhdp8546-core.c-cdns_mhdp_atomic_enable()-warn:inconsistent-returns-mhdp-link_mutex-.
|   |-- 
drivers-pwm-core.c-pwm_cdev_ioctl()-warn:possible-spectre-second-half.-pwm
|   `-- 
drivers-pwm-core.c-pwm_cdev_ioctl()-warn:potential-spectre-issue-cdata-pwm-r
|-- loongarch-allmodconfig
|   |-- 
drivers-gpu-drm-imx-ipuv3-imx-ldb.c:error:_sel-directive-output-may-be-truncated-writing-bytes-into-a-region-of-size-between-and
|   `-- 
drivers-gpu-drm-nouveau-nouveau_backlight.c:error:d-directive-output-may-be-truncated-writing-between-and-bytes-into-a-region-of-size
|-- loongarch-allyesconfig
|   |-- 
drivers-gpu-drm-imx-ipuv3-imx-ldb.c:error:_sel-directive-output-may-be-truncated-writing-bytes-into-a-region-of-size-between-and
|   `-- 
drivers-gpu-drm-nouveau-nouveau_backlight.c:error:d-directive-output-may-be-truncated-writing-between-and-bytes-into-a-region-of-size
|-- microblaze-allmodconfig
|   |-- 
drivers-gpu-drm-imx-ipuv3-imx-ldb.c:error:_sel-directive-output-may-be-truncated-writing-bytes-into-a-region-of-size-between-and
|   `-- 
drivers-gpu-drm-nouveau-nouveau_backlight.c:error:d-directive-output-may-be-truncated-writing-between-and-bytes-into-a-region-of-size
|-- microblaze-allyesconfig
|   |-- 
drivers-gpu-drm-imx-ipuv3-imx-ldb.c:error:_sel-directive-output-may-be-truncated-writing-bytes-into-a-region-of-size-between-and
|   `-- 

[linux-next:master] BUILD REGRESSION 4eab358930711bbeb85bf5ee267d0d42d3394c2c

2024-04-17 Thread kernel test robot
tree/branch: 
https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
branch HEAD: 4eab358930711bbeb85bf5ee267d0d42d3394c2c  Add linux-next specific 
files for 20240417

Error/Warning reports:

https://lore.kernel.org/oe-kbuild-all/202404171743.hfpscodv-...@intel.com
https://lore.kernel.org/oe-kbuild-all/202404171745.zd13ydca-...@intel.com
https://lore.kernel.org/oe-kbuild-all/202404172024.abf4kjuo-...@intel.com

Error/Warning: (recently discovered and may have been fixed)

arch/xtensa/include/asm/irqflags.h:47:(.text+0xf5c): dangerous relocation: 
windowed longcall crosses 1GB boundary; return may fail: (.xiptext+0x210)
mm/page_table_check.c:192:17: error: use of undeclared identifier 
'SWP_DEVICE_EXCLUSIVE_WRITE'
mm/page_table_check.c:192:24: error: 'SWP_DEVICE_EXCLUSIVE_WRITE' undeclared 
(first use in this function)
mm/page_table_check.c:193:14: error: use of undeclared identifier 
'SWP_MIGRATION_WRITE'
mm/page_table_check.c:194:1: warning: control reaches end of non-void function 
[-Wreturn-type]
xtensa-linux-ld: clk-cv18xx-pll.c:(.text+0x2f8): undefined reference to 
`__udivdi3'
xtensa-linux-ld: clk-cv18xx-pll.c:(.text+0x6c8): undefined reference to 
`__umoddi3'

Unverified Error/Warning (likely false positive, please contact us if 
interested):

fs/9p/vfs_inode.c:513 v9fs_remove() error: uninitialized symbol 'v9fid'.

Error/Warning ids grouped by kconfigs:

gcc_recent_errors
|-- alpha-allyesconfig
|   |-- 
drivers-gpu-drm-imx-ipuv3-imx-ldb.c:error:_sel-directive-output-may-be-truncated-writing-bytes-into-a-region-of-size-between-and
|   `-- 
drivers-gpu-drm-nouveau-nouveau_backlight.c:error:d-directive-output-may-be-truncated-writing-between-and-bytes-into-a-region-of-size
|-- alpha-randconfig-r081-20240417
|   `-- fs-9p-vfs_inode.c-v9fs_remove()-error:uninitialized-symbol-v9fid-.
|-- arc-allmodconfig
|   `-- 
arch-arc-include-asm-cmpxchg.h:error:implicit-declaration-of-function-cmpxchg_emu_u8
|-- arc-allnoconfig
|   `-- 
arch-arc-include-asm-cmpxchg.h:error:implicit-declaration-of-function-cmpxchg_emu_u8
|-- arc-allyesconfig
|   `-- 
arch-arc-include-asm-cmpxchg.h:error:implicit-declaration-of-function-cmpxchg_emu_u8
|-- arc-defconfig
|   `-- 
arch-arc-include-asm-cmpxchg.h:error:implicit-declaration-of-function-cmpxchg_emu_u8
|-- arc-randconfig-001-20240417
|   `-- 
arch-arc-include-asm-cmpxchg.h:error:implicit-declaration-of-function-cmpxchg_emu_u8
|-- arc-randconfig-002-20240417
|   `-- 
arch-arc-include-asm-cmpxchg.h:error:implicit-declaration-of-function-cmpxchg_emu_u8
|-- arc-randconfig-r112-20240417
|   `-- 
arch-arc-include-asm-cmpxchg.h:error:implicit-declaration-of-function-cmpxchg_emu_u8
|-- arm-allmodconfig
|   |-- 
drivers-gpu-drm-imx-ipuv3-imx-ldb.c:error:_sel-directive-output-may-be-truncated-writing-bytes-into-a-region-of-size-between-and
|   `-- 
drivers-gpu-drm-nouveau-nouveau_backlight.c:error:d-directive-output-may-be-truncated-writing-between-and-bytes-into-a-region-of-size
|-- arm-allyesconfig
|   |-- 
drivers-gpu-drm-imx-ipuv3-imx-ldb.c:error:_sel-directive-output-may-be-truncated-writing-bytes-into-a-region-of-size-between-and
|   `-- 
drivers-gpu-drm-nouveau-nouveau_backlight.c:error:d-directive-output-may-be-truncated-writing-between-and-bytes-into-a-region-of-size
|-- arm-randconfig-004-20240417
|   `-- clk-cv18xx-pll.c:(.text):undefined-reference-to-__aeabi_uldivmod
|-- csky-allmodconfig
|   |-- 
drivers-gpu-drm-imx-ipuv3-imx-ldb.c:error:_sel-directive-output-may-be-truncated-writing-bytes-into-a-region-of-size-between-and
|   `-- 
drivers-gpu-drm-nouveau-nouveau_backlight.c:error:d-directive-output-may-be-truncated-writing-between-and-bytes-into-a-region-of-size
|-- csky-allyesconfig
|   |-- 
drivers-gpu-drm-imx-ipuv3-imx-ldb.c:error:_sel-directive-output-may-be-truncated-writing-bytes-into-a-region-of-size-between-and
|   `-- 
drivers-gpu-drm-nouveau-nouveau_backlight.c:error:d-directive-output-may-be-truncated-writing-between-and-bytes-into-a-region-of-size
|-- i386-randconfig-003-20240417
|   |-- 
drivers-net-netdevsim-netdev.c:(.text):undefined-reference-to-page_pool_create
|   `-- 
include-net-page_pool-helpers.h:(.text):undefined-reference-to-page_pool_alloc_pages
|-- loongarch-allmodconfig
|   |-- 
drivers-gpu-drm-imx-ipuv3-imx-ldb.c:error:_sel-directive-output-may-be-truncated-writing-bytes-into-a-region-of-size-between-and
|   `-- 
drivers-gpu-drm-nouveau-nouveau_backlight.c:error:d-directive-output-may-be-truncated-writing-between-and-bytes-into-a-region-of-size
|-- loongarch-allyesconfig
|   |-- 
drivers-gpu-drm-imx-ipuv3-imx-ldb.c:error:_sel-directive-output-may-be-truncated-writing-bytes-into-a-region-of-size-between-and
|   `-- 
drivers-gpu-drm-nouveau-nouveau_backlight.c:error:d-directive-output-may-be-truncated-writing-between-and-bytes-into-a-region-of-size
|-- microblaze-allmodconfig
|   |-- 
drivers-gpu-drm-imx-ipuv3-imx-ldb.c:error:_sel-directive-output-may-be-truncated-writing-bytes-into-a-region-of-size-between-and
|   `-- 

[linux-next:master] BUILD REGRESSION 66e4190e92ce0e4a50b2f6be0e5f5b2e47e072f4

2024-04-16 Thread kernel test robot
tree/branch: 
https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
branch HEAD: 66e4190e92ce0e4a50b2f6be0e5f5b2e47e072f4  Add linux-next specific 
files for 20240416

Error/Warning reports:

https://lore.kernel.org/oe-kbuild-all/202404161933.izfqz32k-...@intel.com
https://lore.kernel.org/oe-kbuild-all/202404170348.thxrbof1-...@intel.com

Error/Warning: (recently discovered and may have been fixed)

arch/arc/include/asm/cmpxchg.h:50:26: error: implicit declaration of function 
'cmpxchg_emu_u8' [-Werror=implicit-function-declaration]
arch/mips/sgi-ip27/ip27-irq.c:280:13: warning: unused variable 'i' 
[-Wunused-variable]
netdev.c:(.text+0x2288): undefined reference to `page_pool_create'
netdev.c:(.text+0x378): undefined reference to `page_pool_alloc_pages'

Error/Warning ids grouped by kconfigs:

gcc_recent_errors
|-- alpha-allyesconfig
|   |-- 
drivers-gpu-drm-imx-ipuv3-imx-ldb.c:error:_sel-directive-output-may-be-truncated-writing-bytes-into-a-region-of-size-between-and
|   `-- 
drivers-gpu-drm-nouveau-nouveau_backlight.c:error:d-directive-output-may-be-truncated-writing-between-and-bytes-into-a-region-of-size
|-- alpha-randconfig-r112-20240416
|   `-- 
kernel-bpf-verifier.c:sparse:sparse:cast-truncates-bits-from-constant-value-(fffc-becomes-)
|-- arc-allmodconfig
|   `-- 
arch-arc-include-asm-cmpxchg.h:error:implicit-declaration-of-function-cmpxchg_emu_u8
|-- arc-allnoconfig
|   `-- 
arch-arc-include-asm-cmpxchg.h:error:implicit-declaration-of-function-cmpxchg_emu_u8
|-- arc-allyesconfig
|   `-- 
arch-arc-include-asm-cmpxchg.h:error:implicit-declaration-of-function-cmpxchg_emu_u8
|-- arc-defconfig
|   `-- 
arch-arc-include-asm-cmpxchg.h:error:implicit-declaration-of-function-cmpxchg_emu_u8
|-- arc-nsimosci_hs_smp_defconfig
|   `-- 
arch-arc-include-asm-cmpxchg.h:error:implicit-declaration-of-function-cmpxchg_emu_u8
|-- arc-randconfig-001-20240416
|   `-- 
arch-arc-include-asm-cmpxchg.h:error:implicit-declaration-of-function-cmpxchg_emu_u8
|-- arc-randconfig-002-20240416
|   `-- 
arch-arc-include-asm-cmpxchg.h:error:implicit-declaration-of-function-cmpxchg_emu_u8
|-- arm-allmodconfig
|   |-- 
drivers-gpu-drm-imx-ipuv3-imx-ldb.c:error:_sel-directive-output-may-be-truncated-writing-bytes-into-a-region-of-size-between-and
|   `-- 
drivers-gpu-drm-nouveau-nouveau_backlight.c:error:d-directive-output-may-be-truncated-writing-between-and-bytes-into-a-region-of-size
|-- arm-allyesconfig
|   |-- 
drivers-gpu-drm-imx-ipuv3-imx-ldb.c:error:_sel-directive-output-may-be-truncated-writing-bytes-into-a-region-of-size-between-and
|   `-- 
drivers-gpu-drm-nouveau-nouveau_backlight.c:error:d-directive-output-may-be-truncated-writing-between-and-bytes-into-a-region-of-size
|-- csky-allmodconfig
|   |-- 
drivers-gpu-drm-imx-ipuv3-imx-ldb.c:error:_sel-directive-output-may-be-truncated-writing-bytes-into-a-region-of-size-between-and
|   `-- 
drivers-gpu-drm-nouveau-nouveau_backlight.c:error:d-directive-output-may-be-truncated-writing-between-and-bytes-into-a-region-of-size
|-- csky-allyesconfig
|   |-- 
drivers-gpu-drm-imx-ipuv3-imx-ldb.c:error:_sel-directive-output-may-be-truncated-writing-bytes-into-a-region-of-size-between-and
|   `-- 
drivers-gpu-drm-nouveau-nouveau_backlight.c:error:d-directive-output-may-be-truncated-writing-between-and-bytes-into-a-region-of-size
|-- i386-randconfig-141-20240416
|   |-- 
drivers-pwm-core.c-pwm_cdev_ioctl()-warn:possible-spectre-second-half.-pwm
|   `-- 
drivers-pwm-core.c-pwm_cdev_ioctl()-warn:potential-spectre-issue-cdata-pwm-r
|-- loongarch-allmodconfig
|   |-- 
drivers-gpu-drm-imx-ipuv3-imx-ldb.c:error:_sel-directive-output-may-be-truncated-writing-bytes-into-a-region-of-size-between-and
|   `-- 
drivers-gpu-drm-nouveau-nouveau_backlight.c:error:d-directive-output-may-be-truncated-writing-between-and-bytes-into-a-region-of-size
|-- loongarch-allyesconfig
|   |-- 
drivers-gpu-drm-imx-ipuv3-imx-ldb.c:error:_sel-directive-output-may-be-truncated-writing-bytes-into-a-region-of-size-between-and
|   `-- 
drivers-gpu-drm-nouveau-nouveau_backlight.c:error:d-directive-output-may-be-truncated-writing-between-and-bytes-into-a-region-of-size
|-- microblaze-allmodconfig
|   |-- 
drivers-gpu-drm-imx-ipuv3-imx-ldb.c:error:_sel-directive-output-may-be-truncated-writing-bytes-into-a-region-of-size-between-and
|   `-- 
drivers-gpu-drm-nouveau-nouveau_backlight.c:error:d-directive-output-may-be-truncated-writing-between-and-bytes-into-a-region-of-size
|-- microblaze-allyesconfig
|   |-- 
drivers-gpu-drm-imx-ipuv3-imx-ldb.c:error:_sel-directive-output-may-be-truncated-writing-bytes-into-a-region-of-size-between-and
|   `-- 
drivers-gpu-drm-nouveau-nouveau_backlight.c:error:d-directive-output-may-be-truncated-writing-between-and-bytes-into-a-region-of-size
|-- mips-ip27_defconfig
|   `-- arch-mips-sgi-ip27-ip27-irq.c:warning:unused-variable-i
|-- openrisc-allyesconfig
|   |-- 

Re: [PATCH 3/8] drm/i915/dpio: Extract bxt_dpio_phy_regs.h

2024-04-15 Thread kernel test robot
Hi Ville,

kernel test robot noticed the following build errors:

[auto build test ERROR on drm-intel/for-linux-next]
[also build test ERROR on drm-intel/for-linux-next-fixes drm-tip/drm-tip 
linus/master v6.9-rc4 next-20240415]
[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/Ville-Syrjala/drm-i915-dpio-Clean-up-bxt-glk-PHY-registers/20240415-095059
base:   git://anongit.freedesktop.org/drm-intel for-linux-next
patch link:
https://lore.kernel.org/r/20240412175818.29217-4-ville.syrjala%40linux.intel.com
patch subject: [PATCH 3/8] drm/i915/dpio: Extract bxt_dpio_phy_regs.h
config: x86_64-rhel-8.3-rust 
(https://download.01.org/0day-ci/archive/20240416/202404160914.qsredydl-...@intel.com/config)
compiler: clang version 17.0.6 (https://github.com/llvm/llvm-project 
6009708b4367171ccdbf4b5905cb6a803753fe18)
reproduce (this is a W=1 build): 
(https://download.01.org/0day-ci/archive/20240416/202404160914.qsredydl-...@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 
| Closes: 
https://lore.kernel.org/oe-kbuild-all/202404160914.qsredydl-...@intel.com/

All errors (new ones prefixed by >>):

>> drivers/gpu/drm/i915/intel_gvt_mmio_table.c:1130:9: error: call to 
>> undeclared function 'BXT_PORT_PLL_ENABLE'; ISO C99 and later do not support 
>> implicit function declarations [-Wimplicit-function-declaration]
1130 | MMIO_D(BXT_PORT_PLL_ENABLE(PORT_A));
 |^
   drivers/gpu/drm/i915/intel_gvt_mmio_table.c:1130:2: error: member reference 
base type 'int' is not a structure or union
1130 | MMIO_D(BXT_PORT_PLL_ENABLE(PORT_A));
 | ^~~
   drivers/gpu/drm/i915/intel_gvt_mmio_table.c:35:21: note: expanded from macro 
'MMIO_D'
  35 | #define MMIO_D(reg) MMIO_F(reg, 4)
 | ^~
   drivers/gpu/drm/i915/intel_gvt_mmio_table.c:30:35: note: expanded from macro 
'MMIO_F'
  30 | ret = iter->handle_mmio_cb(iter, i915_mmio_reg_offset(reg), 
s); \
 |  ^
   drivers/gpu/drm/i915/i915_reg_defs.h:283:31: note: expanded from macro 
'i915_mmio_reg_offset'
 283 | _Generic((r), i915_reg_t: (r).reg, i915_mcr_reg_t: (r).reg)
 |   ~~~^~~~
   drivers/gpu/drm/i915/intel_gvt_mmio_table.c:1130:2: error: member reference 
base type 'int' is not a structure or union
1130 | MMIO_D(BXT_PORT_PLL_ENABLE(PORT_A));
 | ^~~
   drivers/gpu/drm/i915/intel_gvt_mmio_table.c:35:21: note: expanded from macro 
'MMIO_D'
  35 | #define MMIO_D(reg) MMIO_F(reg, 4)
 | ^~
   drivers/gpu/drm/i915/intel_gvt_mmio_table.c:30:35: note: expanded from macro 
'MMIO_F'
  30 | ret = iter->handle_mmio_cb(iter, i915_mmio_reg_offset(reg), 
s); \
 |  ^
   drivers/gpu/drm/i915/i915_reg_defs.h:283:56: note: expanded from macro 
'i915_mmio_reg_offset'
 283 | _Generic((r), i915_reg_t: (r).reg, i915_mcr_reg_t: (r).reg)
 |~~~^~~~
   drivers/gpu/drm/i915/intel_gvt_mmio_table.c:1130:9: error: controlling 
expression type 'int' not compatible with any generic association type
1130 | MMIO_D(BXT_PORT_PLL_ENABLE(PORT_A));
 |^~~
   drivers/gpu/drm/i915/intel_gvt_mmio_table.c:35:28: note: expanded from macro 
'MMIO_D'
  35 | #define MMIO_D(reg) MMIO_F(reg, 4)
 |^~~
   drivers/gpu/drm/i915/intel_gvt_mmio_table.c:30:56: note: expanded from macro 
'MMIO_F'
  30 | ret = iter->handle_mmio_cb(iter, i915_mmio_reg_offset(reg), 
s); \
 |   ^~~
   drivers/gpu/drm/i915/i915_reg_defs.h:283:12: note: expanded from macro 
'i915_mmio_reg_offset'
 283 | _Generic((r), i915_reg_t: (r).reg, i915_mcr_reg_t: (r).reg)
 |   ^
   drivers/gpu/drm/i915/intel_gvt_mmio_table.c:1131:9: error: call to 
undeclared function 'BXT_PORT_PLL_ENABLE'; ISO C99 and later do not support 
implicit function declarations [-Wimplicit-function-declaration]
1131 | MMIO_D(BXT_PORT_PLL_ENABLE(PORT_B));
 |^
   drivers/gpu/drm/i915/intel_gvt_mmio_table.c:1131:2: error: member reference 
base type 'int' is not a structure or union
1131 | 

Re: [PATCH 2/8] drm/i915/dpio: Add per-lane PHY TX register definitons for bxt/glk

2024-04-15 Thread kernel test robot
Hi Ville,

kernel test robot noticed the following build errors:

[auto build test ERROR on drm-intel/for-linux-next]
[also build test ERROR on drm-intel/for-linux-next-fixes drm-tip/drm-tip 
linus/master v6.9-rc4]
[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/Ville-Syrjala/drm-i915-dpio-Clean-up-bxt-glk-PHY-registers/20240415-095059
base:   git://anongit.freedesktop.org/drm-intel for-linux-next
patch link:
https://lore.kernel.org/r/20240412175818.29217-3-ville.syrjala%40linux.intel.com
patch subject: [PATCH 2/8] drm/i915/dpio: Add per-lane PHY TX register 
definitons for bxt/glk
config: x86_64-rhel-8.3-bpf 
(https://download.01.org/0day-ci/archive/20240416/202404160823.pkvhpp3o-...@intel.com/config)
compiler: gcc-13 (Ubuntu 13.2.0-4ubuntu3) 13.2.0
reproduce (this is a W=1 build): 
(https://download.01.org/0day-ci/archive/20240416/202404160823.pkvhpp3o-...@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 
| Closes: 
https://lore.kernel.org/oe-kbuild-all/202404160823.pkvhpp3o-...@intel.com/

All errors (new ones prefixed by >>):

   In file included from 
drivers/gpu/drm/i915/display/intel_display_reg_defs.h:9,
from drivers/gpu/drm/i915/display/intel_audio_regs.h:9,
from drivers/gpu/drm/i915/intel_gvt_mmio_table.c:6:
   drivers/gpu/drm/i915/intel_gvt_mmio_table.c: In function 'iterate_bxt_mmio':
>> drivers/gpu/drm/i915/intel_gvt_mmio_table.c:1158:16: error: implicit 
>> declaration of function 'BXT_PORT_TX_DW2_LN0'; did you mean 
>> 'BXT_PORT_TX_DW2_LN'? [-Werror=implicit-function-declaration]
1158 | MMIO_D(BXT_PORT_TX_DW2_LN0(DPIO_PHY0, DPIO_CH0));
 |^~~
   drivers/gpu/drm/i915/i915_reg_defs.h:283:19: note: in definition of macro 
'i915_mmio_reg_offset'
 283 | _Generic((r), i915_reg_t: (r).reg, i915_mcr_reg_t: (r).reg)
 |   ^
   drivers/gpu/drm/i915/intel_gvt_mmio_table.c:35:21: note: in expansion of 
macro 'MMIO_F'
  35 | #define MMIO_D(reg) MMIO_F(reg, 4)
 | ^~
   drivers/gpu/drm/i915/intel_gvt_mmio_table.c:1158:9: note: in expansion of 
macro 'MMIO_D'
1158 | MMIO_D(BXT_PORT_TX_DW2_LN0(DPIO_PHY0, DPIO_CH0));
 | ^~
>> drivers/gpu/drm/i915/i915_reg_defs.h:283:38: error: request for member 'reg' 
>> in something not a structure or union
 283 | _Generic((r), i915_reg_t: (r).reg, i915_mcr_reg_t: (r).reg)
 |  ^
   drivers/gpu/drm/i915/intel_gvt_mmio_table.c:30:42: note: in expansion of 
macro 'i915_mmio_reg_offset'
  30 | ret = iter->handle_mmio_cb(iter, i915_mmio_reg_offset(reg), 
s); \
 |  ^~~~
   drivers/gpu/drm/i915/intel_gvt_mmio_table.c:35:21: note: in expansion of 
macro 'MMIO_F'
  35 | #define MMIO_D(reg) MMIO_F(reg, 4)
 | ^~
   drivers/gpu/drm/i915/intel_gvt_mmio_table.c:1158:9: note: in expansion of 
macro 'MMIO_D'
1158 | MMIO_D(BXT_PORT_TX_DW2_LN0(DPIO_PHY0, DPIO_CH0));
 | ^~
>> drivers/gpu/drm/i915/intel_gvt_mmio_table.c:1160:16: error: implicit 
>> declaration of function 'BXT_PORT_TX_DW3_LN0'; did you mean 
>> 'BXT_PORT_TX_DW3_LN'? [-Werror=implicit-function-declaration]
1160 | MMIO_D(BXT_PORT_TX_DW3_LN0(DPIO_PHY0, DPIO_CH0));
 |^~~
   drivers/gpu/drm/i915/i915_reg_defs.h:283:19: note: in definition of macro 
'i915_mmio_reg_offset'
 283 | _Generic((r), i915_reg_t: (r).reg, i915_mcr_reg_t: (r).reg)
 |   ^
   drivers/gpu/drm/i915/intel_gvt_mmio_table.c:35:21: note: in expansion of 
macro 'MMIO_F'
  35 | #define MMIO_D(reg) MMIO_F(reg, 4)
 | ^~
   drivers/gpu/drm/i915/intel_gvt_mmio_table.c:1160:9: note: in expansion of 
macro 'MMIO_D'
1160 | MMIO_D(BXT_PORT_TX_DW3_LN0(DPIO_PHY0, DPIO_CH0));
 | ^~
>> drivers/gpu/drm/i915/i915_reg_defs.h:283:38: error: request for member 'reg' 
>> in something not a structure or union
 283 | _Generic((r), i915_reg_t: (r).reg, i915_mcr_reg_t: (r).reg)
 |  ^
   drivers/gpu/drm/i915/intel_gvt_mmio_table.c:30:42: note: in expansion of 
macro 'i915_mmio_reg_offset'
  30 | ret = iter->handle_mmio_cb(iter, i915_mmio_reg_offset(reg), 
s); \
 |  ^~~~
   drivers/gpu/drm/i915/inte

Re: [PATCH 2/8] drm/i915/dpio: Add per-lane PHY TX register definitons for bxt/glk

2024-04-15 Thread kernel test robot
Hi Ville,

kernel test robot noticed the following build errors:

[auto build test ERROR on drm-intel/for-linux-next]
[also build test ERROR on drm-intel/for-linux-next-fixes drm-tip/drm-tip 
linus/master v6.9-rc4 next-20240415]
[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/Ville-Syrjala/drm-i915-dpio-Clean-up-bxt-glk-PHY-registers/20240415-095059
base:   git://anongit.freedesktop.org/drm-intel for-linux-next
patch link:
https://lore.kernel.org/r/20240412175818.29217-3-ville.syrjala%40linux.intel.com
patch subject: [PATCH 2/8] drm/i915/dpio: Add per-lane PHY TX register 
definitons for bxt/glk
config: x86_64-rhel-8.3-rust 
(https://download.01.org/0day-ci/archive/20240416/202404160629.idrgs4do-...@intel.com/config)
compiler: clang version 17.0.6 (https://github.com/llvm/llvm-project 
6009708b4367171ccdbf4b5905cb6a803753fe18)
reproduce (this is a W=1 build): 
(https://download.01.org/0day-ci/archive/20240416/202404160629.idrgs4do-...@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 
| Closes: 
https://lore.kernel.org/oe-kbuild-all/202404160629.idrgs4do-...@intel.com/

All errors (new ones prefixed by >>):

   drivers/gpu/drm/i915/intel_gvt_mmio_table.c:1158:9: error: call to 
undeclared function 'BXT_PORT_TX_DW2_LN0'; ISO C99 and later do not support 
implicit function declarations [-Wimplicit-function-declaration]
1158 | MMIO_D(BXT_PORT_TX_DW2_LN0(DPIO_PHY0, DPIO_CH0));
 |^
>> drivers/gpu/drm/i915/intel_gvt_mmio_table.c:1158:2: error: member reference 
>> base type 'int' is not a structure or union
1158 | MMIO_D(BXT_PORT_TX_DW2_LN0(DPIO_PHY0, DPIO_CH0));
 | ^~~~
   drivers/gpu/drm/i915/intel_gvt_mmio_table.c:35:21: note: expanded from macro 
'MMIO_D'
  35 | #define MMIO_D(reg) MMIO_F(reg, 4)
 | ^~
   drivers/gpu/drm/i915/intel_gvt_mmio_table.c:30:35: note: expanded from macro 
'MMIO_F'
  30 | ret = iter->handle_mmio_cb(iter, i915_mmio_reg_offset(reg), 
s); \
 |  ^
   drivers/gpu/drm/i915/i915_reg_defs.h:283:31: note: expanded from macro 
'i915_mmio_reg_offset'
 283 | _Generic((r), i915_reg_t: (r).reg, i915_mcr_reg_t: (r).reg)
 |   ~~~^~~~
>> drivers/gpu/drm/i915/intel_gvt_mmio_table.c:1158:2: error: member reference 
>> base type 'int' is not a structure or union
1158 | MMIO_D(BXT_PORT_TX_DW2_LN0(DPIO_PHY0, DPIO_CH0));
 | ^~~~
   drivers/gpu/drm/i915/intel_gvt_mmio_table.c:35:21: note: expanded from macro 
'MMIO_D'
  35 | #define MMIO_D(reg) MMIO_F(reg, 4)
 | ^~
   drivers/gpu/drm/i915/intel_gvt_mmio_table.c:30:35: note: expanded from macro 
'MMIO_F'
  30 | ret = iter->handle_mmio_cb(iter, i915_mmio_reg_offset(reg), 
s); \
 |  ^
   drivers/gpu/drm/i915/i915_reg_defs.h:283:56: note: expanded from macro 
'i915_mmio_reg_offset'
 283 | _Generic((r), i915_reg_t: (r).reg, i915_mcr_reg_t: (r).reg)
 |~~~^~~~
>> drivers/gpu/drm/i915/intel_gvt_mmio_table.c:1158:9: error: controlling 
>> expression type 'int' not compatible with any generic association type
1158 | MMIO_D(BXT_PORT_TX_DW2_LN0(DPIO_PHY0, DPIO_CH0));
 |^~~~
   drivers/gpu/drm/i915/intel_gvt_mmio_table.c:35:28: note: expanded from macro 
'MMIO_D'
  35 | #define MMIO_D(reg) MMIO_F(reg, 4)
 |^~~
   drivers/gpu/drm/i915/intel_gvt_mmio_table.c:30:56: note: expanded from macro 
'MMIO_F'
  30 | ret = iter->handle_mmio_cb(iter, i915_mmio_reg_offset(reg), 
s); \
 |   ^~~
   drivers/gpu/drm/i915/i915_reg_defs.h:283:12: note: expanded from macro 
'i915_mmio_reg_offset'
 283 | _Generic((r), i915_reg_t: (r).reg, i915_mcr_reg_t: (r).reg)
 |   ^
   drivers/gpu/drm/i915/intel_gvt_mmio_table.c:1160:9: error: call to 
undeclared function 'BXT_PORT_TX_DW3_LN0'; ISO C99 and later do not support 
implicit function declarations [-Wimplicit-function-declaration]
1160 | MMIO_D(BXT_PORT_TX_DW3_LN0(DPIO_PHY0, DPIO_CH0));
 |^
   drivers/gpu/drm/i915/intel_gvt

[linux-next:master] BUILD REGRESSION 6bd343537461b57f3efe5dfc5fc193a232dfef1e

2024-04-15 Thread kernel test robot
tree/branch: 
https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
branch HEAD: 6bd343537461b57f3efe5dfc5fc193a232dfef1e  Add linux-next specific 
files for 20240415

Error/Warning reports:

https://lore.kernel.org/oe-kbuild-all/202404151720.ha4kzy01-...@intel.com
https://lore.kernel.org/oe-kbuild-all/202404160020.38y5ribw-...@intel.com

Error/Warning: (recently discovered and may have been fixed)

WARNING: modpost: vmlinux: section mismatch in reference: ___se_sys_chroot+0xd0 
(section: .text) -> .L0  (section: .init.text)
WARNING: modpost: vmlinux: section mismatch in reference: 
___se_sys_inotify_add_watch+0x12a (section: .text) -> .L0  (section: .init.text)
WARNING: modpost: vmlinux: section mismatch in reference: 
___se_sys_landlock_add_rule+0x1b0 (section: .text) -> .L0  (section: .init.text)
WARNING: modpost: vmlinux: section mismatch in reference: 
___se_sys_open_by_handle_at+0x1ea (section: .text) -> .L0  (section: .init.text)
WARNING: modpost: vmlinux: section mismatch in reference: 
__dev_queue_xmit+0x1d4 (section: .text) -> .L0  (section: .init.text)
WARNING: modpost: vmlinux: section mismatch in reference: __do_sys_fsmount+0xf2 
(section: .text) -> .L0  (section: .init.text)
WARNING: modpost: vmlinux: section mismatch in reference: 
__do_sys_pivot_root+0x28a (section: .text) -> .L0  (section: .init.text)
WARNING: modpost: vmlinux: section mismatch in reference: 
__hw_addr_del_entry+0x44 (section: .text) -> .L0  (section: .init.text)
WARNING: modpost: vmlinux: section mismatch in reference: __hw_addr_flush+0x48 
(section: .text) -> .L0  (section: .init.text)
WARNING: modpost: vmlinux: section mismatch in reference: 
__u64_stats_update_begin+0x16 (section: .text) -> .L0  (section: .init.text)
WARNING: modpost: vmlinux: section mismatch in reference: 
ahci_platform_get_resources+0x84 (section: .text) -> .L0  (section: .init.text)
WARNING: modpost: vmlinux: section mismatch in reference: altera_msi_probe+0x80 
(section: .text) -> .L0  (section: .init.text)
WARNING: modpost: vmlinux: section mismatch in reference: 
armada8k_pcie_probe+0x144 (section: .text) -> .L0  (section: .init.text)
WARNING: modpost: vmlinux: section mismatch in reference: atmel_sha_probe+0x36a 
(section: .text) -> .L0  (section: .init.text)
WARNING: modpost: vmlinux: section mismatch in reference: 
btrfs_init_new_device+0x14e (section: .text) -> .L0  (section: .init.text)
WARNING: modpost: vmlinux: section mismatch in reference: cqhci_pltfm_init+0x1a 
(section: .text) -> .L0  (section: .init.text)
WARNING: modpost: vmlinux: section mismatch in reference: 
default_device_exit_net+0x128 (section: .text) -> .L0  (section: .init.text)
WARNING: modpost: vmlinux: section mismatch in reference: do_coredump+0x454 
(section: .text) -> .L0  (section: .init.text)
WARNING: modpost: vmlinux: section mismatch in reference: do_utimes+0xea 
(section: .text) -> .L0  (section: .init.text)
WARNING: modpost: vmlinux: section mismatch in reference: dpm_suspend+0xa2 
(section: .text) -> .L0  (section: .init.text)
WARNING: modpost: vmlinux: section mismatch in reference: dpm_suspend_late+0x86 
(section: .text) -> .L0  (section: .init.text)
WARNING: modpost: vmlinux: section mismatch in reference: 
dpm_suspend_noirq+0xa2 (section: .text) -> .L0  (section: .init.text)
WARNING: modpost: vmlinux: section mismatch in reference: edma_probe+0xf2 
(section: .text) -> .L0  (section: .init.text)
WARNING: modpost: vmlinux: section mismatch in reference: 
free_filters_list+0x3c (section: .text) -> .L0  (section: .init.text)
WARNING: modpost: vmlinux: section mismatch in reference: img_hash_probe+0x3a0 
(section: .text) -> .L0  (section: .init.text)
WARNING: modpost: vmlinux: section mismatch in reference: ipv6_icmp_error+0x20 
(section: .text) -> .L0  (section: .init.text)
WARNING: modpost: vmlinux: section mismatch in reference: 
kernel_read_file_from_path_initns+0xe6 (section: .text) -> .L0  (section: 
.init.text)
WARNING: modpost: vmlinux: section mismatch in reference: 
kmb_ocs_aes_probe+0x1c2 (section: .text) -> .L0  (section: .init.text)
WARNING: modpost: vmlinux: section mismatch in reference: 
kmb_ocs_ecc_probe+0x172 (section: .text) -> .L0  (section: .init.text)
WARNING: modpost: vmlinux: section mismatch in reference: ks_pcie_probe+0xb0 
(section: .text) -> .L0  (section: .init.text)
WARNING: modpost: vmlinux: section mismatch in reference: 
lpc18xx_eeprom_probe+0x3e (section: .text) -> .L0  (section: .init.text)
WARNING: modpost: vmlinux: section mismatch in reference: mntns_install+0xd4 
(section: .text) -> .L0  (section: .init.text)
WARNING: modpost: vmlinux: section mismatch in reference: 
mobiveil_pcie_host_probe+0x36 (section: .text) -> .L0  (section: .init.text)
WARNING: modpost: vmlinux: section mismatch in reference: 
mptcp_pm_nl_get_addr+0x112 (section: .text) -> .L0  (section: .init.text)
WARNING: modpost: vmlinux: section mismatch in reference: mtk_iommu_probe+0x30c 
(section: .text) -> .L0  (section: .init.text)

[linux-next:master] BUILD REGRESSION 9ed46da14b9b9b2ad4edb3b0c545b6dbe5c00d39

2024-04-12 Thread kernel test robot
tree/branch: 
https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
branch HEAD: 9ed46da14b9b9b2ad4edb3b0c545b6dbe5c00d39  Add linux-next specific 
files for 20240412

Unverified Error/Warning (likely false positive, please contact us if 
interested):

{standard input}:1011: Error: expected comma after name `mp' in .size directive
{standard input}:897: Warning: overflow in branch to .L148; converted into 
longer instruction sequence
{standard input}:908: Warning: overflow in branch to .L150; converted into 
longer instruction sequence

Error/Warning ids grouped by kconfigs:

gcc_recent_errors
|-- alpha-allyesconfig
|   |-- 
drivers-gpu-drm-imx-ipuv3-imx-ldb.c:error:_sel-directive-output-may-be-truncated-writing-bytes-into-a-region-of-size-between-and
|   `-- 
drivers-gpu-drm-nouveau-nouveau_backlight.c:error:d-directive-output-may-be-truncated-writing-between-and-bytes-into-a-region-of-size
|-- arm-allmodconfig
|   |-- 
drivers-gpu-drm-imx-ipuv3-imx-ldb.c:error:_sel-directive-output-may-be-truncated-writing-bytes-into-a-region-of-size-between-and
|   `-- 
drivers-gpu-drm-nouveau-nouveau_backlight.c:error:d-directive-output-may-be-truncated-writing-between-and-bytes-into-a-region-of-size
|-- arm-allyesconfig
|   |-- 
drivers-gpu-drm-imx-ipuv3-imx-ldb.c:error:_sel-directive-output-may-be-truncated-writing-bytes-into-a-region-of-size-between-and
|   `-- 
drivers-gpu-drm-nouveau-nouveau_backlight.c:error:d-directive-output-may-be-truncated-writing-between-and-bytes-into-a-region-of-size
|-- arm-randconfig-001-20240412
|   `-- 
WARNING:modpost:lib-test_user_copy:section-mismatch-in-reference:(unknown)-(section:.text.fixup)-(section:.init.text)
|-- csky-allmodconfig
|   |-- 
drivers-gpu-drm-imx-ipuv3-imx-ldb.c:error:_sel-directive-output-may-be-truncated-writing-bytes-into-a-region-of-size-between-and
|   `-- 
drivers-gpu-drm-nouveau-nouveau_backlight.c:error:d-directive-output-may-be-truncated-writing-between-and-bytes-into-a-region-of-size
|-- csky-allyesconfig
|   |-- 
drivers-gpu-drm-imx-ipuv3-imx-ldb.c:error:_sel-directive-output-may-be-truncated-writing-bytes-into-a-region-of-size-between-and
|   `-- 
drivers-gpu-drm-nouveau-nouveau_backlight.c:error:d-directive-output-may-be-truncated-writing-between-and-bytes-into-a-region-of-size
|-- i386-randconfig-141-20240412
|   |-- 
drivers-pwm-core.c-pwm_cdev_ioctl()-warn:possible-spectre-second-half.-pwm
|   `-- 
drivers-pwm-core.c-pwm_cdev_ioctl()-warn:potential-spectre-issue-cdata-pwm-r
|-- loongarch-allmodconfig
|   |-- 
drivers-gpu-drm-imx-ipuv3-imx-ldb.c:error:_sel-directive-output-may-be-truncated-writing-bytes-into-a-region-of-size-between-and
|   `-- 
drivers-gpu-drm-nouveau-nouveau_backlight.c:error:d-directive-output-may-be-truncated-writing-between-and-bytes-into-a-region-of-size
|-- loongarch-allyesconfig
|   |-- 
drivers-gpu-drm-imx-ipuv3-imx-ldb.c:error:_sel-directive-output-may-be-truncated-writing-bytes-into-a-region-of-size-between-and
|   `-- 
drivers-gpu-drm-nouveau-nouveau_backlight.c:error:d-directive-output-may-be-truncated-writing-between-and-bytes-into-a-region-of-size
|-- microblaze-allmodconfig
|   |-- 
drivers-gpu-drm-imx-ipuv3-imx-ldb.c:error:_sel-directive-output-may-be-truncated-writing-bytes-into-a-region-of-size-between-and
|   `-- 
drivers-gpu-drm-nouveau-nouveau_backlight.c:error:d-directive-output-may-be-truncated-writing-between-and-bytes-into-a-region-of-size
|-- microblaze-allyesconfig
|   |-- 
drivers-gpu-drm-imx-ipuv3-imx-ldb.c:error:_sel-directive-output-may-be-truncated-writing-bytes-into-a-region-of-size-between-and
|   `-- 
drivers-gpu-drm-nouveau-nouveau_backlight.c:error:d-directive-output-may-be-truncated-writing-between-and-bytes-into-a-region-of-size
|-- openrisc-allyesconfig
|   |-- 
drivers-gpu-drm-imx-ipuv3-imx-ldb.c:error:_sel-directive-output-may-be-truncated-writing-bytes-into-a-region-of-size-between-and
|   `-- 
drivers-gpu-drm-nouveau-nouveau_backlight.c:error:d-directive-output-may-be-truncated-writing-between-and-bytes-into-a-region-of-size
|-- parisc-allmodconfig
|   |-- 
drivers-gpu-drm-imx-ipuv3-imx-ldb.c:error:_sel-directive-output-may-be-truncated-writing-bytes-into-a-region-of-size-between-and
|   |-- 
drivers-gpu-drm-nouveau-nouveau_backlight.c:error:d-directive-output-may-be-truncated-writing-between-and-bytes-into-a-region-of-size
|   `-- 
drivers-gpu-drm-nouveau-nvif-object.c:error:memcpy-accessing-or-more-bytes-at-offsets-and-overlaps-bytes-at-offset
|-- parisc-allyesconfig
|   |-- 
drivers-gpu-drm-imx-ipuv3-imx-ldb.c:error:_sel-directive-output-may-be-truncated-writing-bytes-into-a-region-of-size-between-and
|   |-- 
drivers-gpu-drm-nouveau-nouveau_backlight.c:error:d-directive-output-may-be-truncated-writing-between-and-bytes-into-a-region-of-size
|   `-- 
drivers-gpu-drm-nouveau-nvif-object.c:error:memcpy-accessing-or-more-bytes-at-offsets-and-overlaps-bytes-at-offset
|-- powerpc-allmodconfig
|   |-- 

[linux-next:master] BUILD REGRESSION 4118d9533ff3a5d16efb476a0d00afceecd92cf5

2024-04-11 Thread kernel test robot
tree/branch: 
https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
branch HEAD: 4118d9533ff3a5d16efb476a0d00afceecd92cf5  Add linux-next specific 
files for 20240411

Error/Warning reports:

https://lore.kernel.org/oe-kbuild-all/202404120101.daqbazh3-...@intel.com

Error/Warning: (recently discovered and may have been fixed)

huge_memory.c:(.text+0x1778): undefined reference to `mthp_stats'
memory.c:(.text+0xee0): undefined reference to `mthp_stats'
sparc64-linux-ld: memory.c:(.text+0xee4): undefined reference to `mthp_stats'
sparc64-linux-ld: vmscan.c:(.text+0x4dc0): undefined reference to `mthp_stats'
vmscan.c:(.text+0x4db8): undefined reference to `mthp_stats'

Error/Warning ids grouped by kconfigs:

gcc_recent_errors
|-- alpha-allyesconfig
|   |-- 
drivers-gpu-drm-imx-ipuv3-imx-ldb.c:error:_sel-directive-output-may-be-truncated-writing-bytes-into-a-region-of-size-between-and
|   `-- 
drivers-gpu-drm-nouveau-nouveau_backlight.c:error:d-directive-output-may-be-truncated-writing-between-and-bytes-into-a-region-of-size
|-- arm-allmodconfig
|   |-- 
drivers-gpu-drm-imx-ipuv3-imx-ldb.c:error:_sel-directive-output-may-be-truncated-writing-bytes-into-a-region-of-size-between-and
|   `-- 
drivers-gpu-drm-nouveau-nouveau_backlight.c:error:d-directive-output-may-be-truncated-writing-between-and-bytes-into-a-region-of-size
|-- arm-allyesconfig
|   |-- 
drivers-gpu-drm-imx-ipuv3-imx-ldb.c:error:_sel-directive-output-may-be-truncated-writing-bytes-into-a-region-of-size-between-and
|   `-- 
drivers-gpu-drm-nouveau-nouveau_backlight.c:error:d-directive-output-may-be-truncated-writing-between-and-bytes-into-a-region-of-size
|-- csky-allmodconfig
|   |-- 
drivers-gpu-drm-imx-ipuv3-imx-ldb.c:error:_sel-directive-output-may-be-truncated-writing-bytes-into-a-region-of-size-between-and
|   |-- 
drivers-gpu-drm-nouveau-nouveau_backlight.c:error:d-directive-output-may-be-truncated-writing-between-and-bytes-into-a-region-of-size
|   |-- lib-..-mm-internal.h:warning:suggest-parentheses-around-in-operand-of
|   |-- mm-damon-..-internal.h:warning:suggest-parentheses-around-in-operand-of
|   `-- mm-internal.h:warning:suggest-parentheses-around-in-operand-of
|-- csky-allnoconfig
|   |-- lib-..-mm-internal.h:warning:suggest-parentheses-around-in-operand-of
|   `-- mm-internal.h:warning:suggest-parentheses-around-in-operand-of
|-- csky-allyesconfig
|   |-- 
drivers-gpu-drm-imx-ipuv3-imx-ldb.c:error:_sel-directive-output-may-be-truncated-writing-bytes-into-a-region-of-size-between-and
|   |-- 
drivers-gpu-drm-nouveau-nouveau_backlight.c:error:d-directive-output-may-be-truncated-writing-between-and-bytes-into-a-region-of-size
|   |-- lib-..-mm-internal.h:warning:suggest-parentheses-around-in-operand-of
|   |-- mm-damon-..-internal.h:warning:suggest-parentheses-around-in-operand-of
|   `-- mm-internal.h:warning:suggest-parentheses-around-in-operand-of
|-- csky-defconfig
|   |-- lib-..-mm-internal.h:warning:suggest-parentheses-around-in-operand-of
|   `-- mm-internal.h:warning:suggest-parentheses-around-in-operand-of
|-- csky-randconfig-001-20240411
|   |-- lib-..-mm-internal.h:warning:suggest-parentheses-around-in-operand-of
|   `-- mm-internal.h:warning:suggest-parentheses-around-in-operand-of
|-- csky-randconfig-002-20240411
|   |-- lib-..-mm-internal.h:warning:suggest-parentheses-around-in-operand-of
|   `-- mm-internal.h:warning:suggest-parentheses-around-in-operand-of
|-- i386-randconfig-141-20240411
|   |-- 
drivers-dma-fsl-edma-main.c-fsl_edma_xlate()-warn:inconsistent-returns-fsl_edma-fsl_edma_mutex-.
|   |-- 
drivers-pwm-core.c-pwm_cdev_ioctl()-warn:possible-spectre-second-half.-pwm
|   `-- 
drivers-pwm-core.c-pwm_cdev_ioctl()-warn:potential-spectre-issue-cdata-pwm-r
|-- loongarch-allmodconfig
|   |-- 
drivers-gpu-drm-imx-ipuv3-imx-ldb.c:error:_sel-directive-output-may-be-truncated-writing-bytes-into-a-region-of-size-between-and
|   `-- 
drivers-gpu-drm-nouveau-nouveau_backlight.c:error:d-directive-output-may-be-truncated-writing-between-and-bytes-into-a-region-of-size
|-- loongarch-allyesconfig
|   |-- 
drivers-gpu-drm-imx-ipuv3-imx-ldb.c:error:_sel-directive-output-may-be-truncated-writing-bytes-into-a-region-of-size-between-and
|   `-- 
drivers-gpu-drm-nouveau-nouveau_backlight.c:error:d-directive-output-may-be-truncated-writing-between-and-bytes-into-a-region-of-size
|-- microblaze-allmodconfig
|   |-- 
drivers-gpu-drm-imx-ipuv3-imx-ldb.c:error:_sel-directive-output-may-be-truncated-writing-bytes-into-a-region-of-size-between-and
|   `-- 
drivers-gpu-drm-nouveau-nouveau_backlight.c:error:d-directive-output-may-be-truncated-writing-between-and-bytes-into-a-region-of-size
|-- microblaze-allyesconfig
|   |-- 
drivers-gpu-drm-imx-ipuv3-imx-ldb.c:error:_sel-directive-output-may-be-truncated-writing-bytes-into-a-region-of-size-between-and
|   `-- 
drivers-gpu-drm-nouveau-nouveau_backlight.c:error:d-directive-output-may-be-truncated-writing-between-and-bytes-into-a-region-of-size
|-- openrisc-allyesconfig
|  

[linux-next:master] BUILD REGRESSION 6ebf211bb11dfc004a2ff73a9de5386fa309c430

2024-04-10 Thread kernel test robot
tree/branch: 
https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
branch HEAD: 6ebf211bb11dfc004a2ff73a9de5386fa309c430  Add linux-next specific 
files for 20240410

Error/Warning reports:

https://lore.kernel.org/oe-kbuild-all/202404102353.cv1gujk3-...@intel.com

Error/Warning: (recently discovered and may have been fixed)

WARNING: modpost: vmlinux: section mismatch in reference: bitmap_read+0x128 
(section: .text.unlikely) -> __setup_str_initcall_blacklist (section: 
.init.rodata)
drivers/gpu/drm/drm_mm.c:614:20: error: function 'drm_mm_node_scanned_block' is 
not needed and will not be emitted [-Werror,-Wunneeded-internal-declaration]

Unverified Error/Warning (likely false positive, please contact us if 
interested):

fs/exfat/file.c:554 exfat_extend_valid_size() error: uninitialized symbol 'err'.

Error/Warning ids grouped by kconfigs:

gcc_recent_errors
|-- alpha-allyesconfig
|   |-- 
drivers-gpu-drm-imx-ipuv3-imx-ldb.c:error:_sel-directive-output-may-be-truncated-writing-bytes-into-a-region-of-size-between-and
|   `-- 
drivers-gpu-drm-nouveau-nouveau_backlight.c:error:d-directive-output-may-be-truncated-writing-between-and-bytes-into-a-region-of-size
|-- arm-allmodconfig
|   |-- 
drivers-gpu-drm-imx-ipuv3-imx-ldb.c:error:_sel-directive-output-may-be-truncated-writing-bytes-into-a-region-of-size-between-and
|   `-- 
drivers-gpu-drm-nouveau-nouveau_backlight.c:error:d-directive-output-may-be-truncated-writing-between-and-bytes-into-a-region-of-size
|-- arm-allyesconfig
|   |-- 
drivers-gpu-drm-imx-ipuv3-imx-ldb.c:error:_sel-directive-output-may-be-truncated-writing-bytes-into-a-region-of-size-between-and
|   `-- 
drivers-gpu-drm-nouveau-nouveau_backlight.c:error:d-directive-output-may-be-truncated-writing-between-and-bytes-into-a-region-of-size
|-- csky-alldefconfig
|   |-- lib-..-mm-internal.h:warning:suggest-parentheses-around-in-operand-of
|   `-- mm-internal.h:warning:suggest-parentheses-around-in-operand-of
|-- csky-allmodconfig
|   |-- 
drivers-gpu-drm-imx-ipuv3-imx-ldb.c:error:_sel-directive-output-may-be-truncated-writing-bytes-into-a-region-of-size-between-and
|   |-- 
drivers-gpu-drm-nouveau-nouveau_backlight.c:error:d-directive-output-may-be-truncated-writing-between-and-bytes-into-a-region-of-size
|   |-- lib-..-mm-internal.h:warning:suggest-parentheses-around-in-operand-of
|   |-- mm-damon-..-internal.h:warning:suggest-parentheses-around-in-operand-of
|   `-- mm-internal.h:warning:suggest-parentheses-around-in-operand-of
|-- csky-allnoconfig
|   |-- lib-..-mm-internal.h:warning:suggest-parentheses-around-in-operand-of
|   `-- mm-internal.h:warning:suggest-parentheses-around-in-operand-of
|-- csky-allyesconfig
|   |-- 
drivers-gpu-drm-imx-ipuv3-imx-ldb.c:error:_sel-directive-output-may-be-truncated-writing-bytes-into-a-region-of-size-between-and
|   |-- 
drivers-gpu-drm-nouveau-nouveau_backlight.c:error:d-directive-output-may-be-truncated-writing-between-and-bytes-into-a-region-of-size
|   |-- lib-..-mm-internal.h:warning:suggest-parentheses-around-in-operand-of
|   |-- mm-damon-..-internal.h:warning:suggest-parentheses-around-in-operand-of
|   `-- mm-internal.h:warning:suggest-parentheses-around-in-operand-of
|-- csky-defconfig
|   |-- lib-..-mm-internal.h:warning:suggest-parentheses-around-in-operand-of
|   `-- mm-internal.h:warning:suggest-parentheses-around-in-operand-of
|-- csky-randconfig-001-20240410
|   |-- lib-..-mm-internal.h:warning:suggest-parentheses-around-in-operand-of
|   `-- mm-internal.h:warning:suggest-parentheses-around-in-operand-of
|-- csky-randconfig-002-20240410
|   |-- lib-..-mm-internal.h:warning:suggest-parentheses-around-in-operand-of
|   `-- mm-internal.h:warning:suggest-parentheses-around-in-operand-of
|-- csky-randconfig-r054-20240410
|   |-- lib-..-mm-internal.h:warning:suggest-parentheses-around-in-operand-of
|   `-- mm-internal.h:warning:suggest-parentheses-around-in-operand-of
|-- i386-randconfig-141-20240410
|   `-- 
fs-exfat-file.c-exfat_extend_valid_size()-error:uninitialized-symbol-err-.
|-- loongarch-allmodconfig
|   |-- 
drivers-gpu-drm-imx-ipuv3-imx-ldb.c:error:_sel-directive-output-may-be-truncated-writing-bytes-into-a-region-of-size-between-and
|   `-- 
drivers-gpu-drm-nouveau-nouveau_backlight.c:error:d-directive-output-may-be-truncated-writing-between-and-bytes-into-a-region-of-size
|-- loongarch-allyesconfig
|   |-- 
drivers-gpu-drm-imx-ipuv3-imx-ldb.c:error:_sel-directive-output-may-be-truncated-writing-bytes-into-a-region-of-size-between-and
|   `-- 
drivers-gpu-drm-nouveau-nouveau_backlight.c:error:d-directive-output-may-be-truncated-writing-between-and-bytes-into-a-region-of-size
|-- microblaze-allmodconfig
|   |-- 
drivers-gpu-drm-imx-ipuv3-imx-ldb.c:error:_sel-directive-output-may-be-truncated-writing-bytes-into-a-region-of-size-between-and
|   `-- 
drivers-gpu-drm-nouveau-nouveau_backlight.c:error:d-directive-output-may-be-truncated-writing-between-and-bytes-into-a-region-of-size
|-- microblaze-allyesconfig
|   

[linux-next:master] BUILD REGRESSION a053fd3ca5d1b927a8655f239c84b0d790218fda

2024-04-09 Thread kernel test robot
tree/branch: 
https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
branch HEAD: a053fd3ca5d1b927a8655f239c84b0d790218fda  Add linux-next specific 
files for 20240409

Error/Warning reports:

https://lore.kernel.org/oe-kbuild-all/202404091516.9h8idamm-...@intel.com
https://lore.kernel.org/oe-kbuild-all/202404091749.scnpj8j4-...@intel.com
https://lore.kernel.org/oe-kbuild-all/202404091959.he2hjvyl-...@intel.com

Error/Warning: (recently discovered and may have been fixed)

WARNING: modpost: vmlinux: section mismatch in reference: (unknown)+0x14d0 
(section: __ex_table) -> .LASF112 (section: .debug_str)
WARNING: modpost: vmlinux: section mismatch in reference: (unknown)+0x14d4 
(section: __ex_table) -> .LASF114 (section: .debug_str)
WARNING: modpost: vmlinux: section mismatch in reference: (unknown)+0x14dc 
(section: __ex_table) -> .LASF116 (section: .debug_str)
WARNING: modpost: vmlinux: section mismatch in reference: (unknown)+0x14e0 
(section: __ex_table) -> .LASF118 (section: .debug_str)
WARNING: modpost: vmlinux: section mismatch in reference: ___se_sys_chroot+0xd0 
(section: .text) -> .L0  (section: .init.text)
WARNING: modpost: vmlinux: section mismatch in reference: 
___se_sys_inotify_add_watch+0x12a (section: .text) -> .L0  (section: .init.text)
WARNING: modpost: vmlinux: section mismatch in reference: 
___se_sys_landlock_add_rule+0x1b0 (section: .text) -> .L0  (section: .init.text)
WARNING: modpost: vmlinux: section mismatch in reference: 
___se_sys_open_by_handle_at+0x1ea (section: .text) -> .L0  (section: .init.text)
WARNING: modpost: vmlinux: section mismatch in reference: 
__dev_queue_xmit+0x1d4 (section: .text) -> .L0  (section: .init.text)
WARNING: modpost: vmlinux: section mismatch in reference: __do_sys_fsmount+0xf2 
(section: .text) -> .L0  (section: .init.text)
WARNING: modpost: vmlinux: section mismatch in reference: 
__do_sys_pivot_root+0x28a (section: .text) -> .L0  (section: .init.text)
WARNING: modpost: vmlinux: section mismatch in reference: 
__hw_addr_del_entry+0x44 (section: .text) -> .L0  (section: .init.text)
WARNING: modpost: vmlinux: section mismatch in reference: __hw_addr_flush+0x48 
(section: .text) -> .L0  (section: .init.text)
WARNING: modpost: vmlinux: section mismatch in reference: 
__u64_stats_update_begin+0x16 (section: .text) -> .L0  (section: .init.text)
WARNING: modpost: vmlinux: section mismatch in reference: 
ahci_platform_get_resources+0x84 (section: .text) -> .L0  (section: .init.text)
WARNING: modpost: vmlinux: section mismatch in reference: altera_msi_probe+0x80 
(section: .text) -> .L0  (section: .init.text)
WARNING: modpost: vmlinux: section mismatch in reference: 
armada8k_pcie_probe+0x144 (section: .text) -> .L0  (section: .init.text)
WARNING: modpost: vmlinux: section mismatch in reference: atmel_sha_probe+0x36a 
(section: .text) -> .L0  (section: .init.text)
WARNING: modpost: vmlinux: section mismatch in reference: 
btrfs_init_new_device+0x14e (section: .text) -> .L0  (section: .init.text)
WARNING: modpost: vmlinux: section mismatch in reference: cqhci_pltfm_init+0x1a 
(section: .text) -> .L0  (section: .init.text)
WARNING: modpost: vmlinux: section mismatch in reference: 
default_device_exit_net+0x128 (section: .text) -> .L0  (section: .init.text)
WARNING: modpost: vmlinux: section mismatch in reference: do_coredump+0x454 
(section: .text) -> .L0  (section: .init.text)
WARNING: modpost: vmlinux: section mismatch in reference: do_utimes+0xea 
(section: .text) -> .L0  (section: .init.text)
WARNING: modpost: vmlinux: section mismatch in reference: dpm_suspend+0xa2 
(section: .text) -> .L0  (section: .init.text)
WARNING: modpost: vmlinux: section mismatch in reference: dpm_suspend_late+0x86 
(section: .text) -> .L0  (section: .init.text)
WARNING: modpost: vmlinux: section mismatch in reference: 
dpm_suspend_noirq+0xa2 (section: .text) -> .L0  (section: .init.text)
WARNING: modpost: vmlinux: section mismatch in reference: edma_probe+0xf2 
(section: .text) -> .L0  (section: .init.text)
WARNING: modpost: vmlinux: section mismatch in reference: 
free_filters_list+0x3c (section: .text) -> .L0  (section: .init.text)
WARNING: modpost: vmlinux: section mismatch in reference: img_hash_probe+0x3a0 
(section: .text) -> .L0  (section: .init.text)
WARNING: modpost: vmlinux: section mismatch in reference: ipv6_icmp_error+0x20 
(section: .text) -> .L0  (section: .init.text)
WARNING: modpost: vmlinux: section mismatch in reference: 
kernel_read_file_from_path_initns+0xe6 (section: .text) -> .L0  (section: 
.init.text)
WARNING: modpost: vmlinux: section mismatch in reference: 
kmb_ocs_aes_probe+0x1c2 (section: .text) -> .L0  (section: .init.text)
WARNING: modpost: vmlinux: section mismatch in reference: 
kmb_ocs_ecc_probe+0x172 (section: .text) -> .L0  (section: .init.text)
WARNING: modpost: vmlinux: section mismatch in reference: ks_pcie_probe+0xb0 
(section: .text) -> .L0  (section: .init.text)
WARNING: modpost: vmlinux: section mismatch in 

[linux-next:master] BUILD REGRESSION 11cb68ad52ac78c81e33b806b531f097e68edfa2

2024-04-08 Thread kernel test robot
tree/branch: 
https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
branch HEAD: 11cb68ad52ac78c81e33b806b531f097e68edfa2  Add linux-next specific 
files for 20240408

Error/Warning: (recently discovered and may have been fixed)

drivers/gpu/drm/drm_mm.c:152:1: error: unused function 
'drm_mm_interval_tree_insert' [-Werror,-Wunused-function]
drivers/gpu/drm/drm_mm.c:152:1: error: unused function 
'drm_mm_interval_tree_iter_next' [-Werror,-Wunused-function]
drivers/gpu/drm/lima/lima_drv.c:387:13: error: cast to smaller integer type 
'enum lima_gpu_id' from 'const void *' [-Werror,-Wvoid-pointer-to-enum-cast]
drivers/gpu/drm/pl111/pl111_versatile.c:488:24: error: cast to smaller integer 
type 'enum versatile_clcd' from 'const void *' 
[-Werror,-Wvoid-pointer-to-enum-cast]

Error/Warning ids grouped by kconfigs:

gcc_recent_errors
|-- alpha-allyesconfig
|   |-- 
drivers-gpu-drm-imx-ipuv3-imx-ldb.c:error:_sel-directive-output-may-be-truncated-writing-bytes-into-a-region-of-size-between-and
|   `-- 
drivers-gpu-drm-nouveau-nouveau_backlight.c:error:d-directive-output-may-be-truncated-writing-between-and-bytes-into-a-region-of-size
|-- arm-allmodconfig
|   |-- 
drivers-gpu-drm-imx-ipuv3-imx-ldb.c:error:_sel-directive-output-may-be-truncated-writing-bytes-into-a-region-of-size-between-and
|   `-- 
drivers-gpu-drm-nouveau-nouveau_backlight.c:error:d-directive-output-may-be-truncated-writing-between-and-bytes-into-a-region-of-size
|-- arm-allyesconfig
|   |-- 
drivers-gpu-drm-imx-ipuv3-imx-ldb.c:error:_sel-directive-output-may-be-truncated-writing-bytes-into-a-region-of-size-between-and
|   `-- 
drivers-gpu-drm-nouveau-nouveau_backlight.c:error:d-directive-output-may-be-truncated-writing-between-and-bytes-into-a-region-of-size
|-- csky-allmodconfig
|   |-- 
drivers-gpu-drm-imx-ipuv3-imx-ldb.c:error:_sel-directive-output-may-be-truncated-writing-bytes-into-a-region-of-size-between-and
|   `-- 
drivers-gpu-drm-nouveau-nouveau_backlight.c:error:d-directive-output-may-be-truncated-writing-between-and-bytes-into-a-region-of-size
|-- csky-allyesconfig
|   |-- 
drivers-gpu-drm-imx-ipuv3-imx-ldb.c:error:_sel-directive-output-may-be-truncated-writing-bytes-into-a-region-of-size-between-and
|   `-- 
drivers-gpu-drm-nouveau-nouveau_backlight.c:error:d-directive-output-may-be-truncated-writing-between-and-bytes-into-a-region-of-size
|-- loongarch-allmodconfig
|   |-- 
drivers-gpu-drm-imx-ipuv3-imx-ldb.c:error:_sel-directive-output-may-be-truncated-writing-bytes-into-a-region-of-size-between-and
|   `-- 
drivers-gpu-drm-nouveau-nouveau_backlight.c:error:d-directive-output-may-be-truncated-writing-between-and-bytes-into-a-region-of-size
|-- microblaze-allmodconfig
|   |-- 
drivers-gpu-drm-imx-ipuv3-imx-ldb.c:error:_sel-directive-output-may-be-truncated-writing-bytes-into-a-region-of-size-between-and
|   `-- 
drivers-gpu-drm-nouveau-nouveau_backlight.c:error:d-directive-output-may-be-truncated-writing-between-and-bytes-into-a-region-of-size
|-- microblaze-allyesconfig
|   |-- 
drivers-gpu-drm-imx-ipuv3-imx-ldb.c:error:_sel-directive-output-may-be-truncated-writing-bytes-into-a-region-of-size-between-and
|   `-- 
drivers-gpu-drm-nouveau-nouveau_backlight.c:error:d-directive-output-may-be-truncated-writing-between-and-bytes-into-a-region-of-size
|-- openrisc-allyesconfig
|   |-- 
drivers-gpu-drm-imx-ipuv3-imx-ldb.c:error:_sel-directive-output-may-be-truncated-writing-bytes-into-a-region-of-size-between-and
|   `-- 
drivers-gpu-drm-nouveau-nouveau_backlight.c:error:d-directive-output-may-be-truncated-writing-between-and-bytes-into-a-region-of-size
|-- parisc-allmodconfig
|   |-- 
drivers-gpu-drm-imx-ipuv3-imx-ldb.c:error:_sel-directive-output-may-be-truncated-writing-bytes-into-a-region-of-size-between-and
|   |-- 
drivers-gpu-drm-nouveau-nouveau_backlight.c:error:d-directive-output-may-be-truncated-writing-between-and-bytes-into-a-region-of-size
|   `-- 
drivers-gpu-drm-nouveau-nvif-object.c:error:memcpy-accessing-or-more-bytes-at-offsets-and-overlaps-bytes-at-offset
|-- parisc-allyesconfig
|   |-- 
drivers-gpu-drm-imx-ipuv3-imx-ldb.c:error:_sel-directive-output-may-be-truncated-writing-bytes-into-a-region-of-size-between-and
|   |-- 
drivers-gpu-drm-nouveau-nouveau_backlight.c:error:d-directive-output-may-be-truncated-writing-between-and-bytes-into-a-region-of-size
|   `-- 
drivers-gpu-drm-nouveau-nvif-object.c:error:memcpy-accessing-or-more-bytes-at-offsets-and-overlaps-bytes-at-offset
|-- powerpc-allmodconfig
|   |-- 
drivers-gpu-drm-imx-ipuv3-imx-ldb.c:error:_sel-directive-output-may-be-truncated-writing-bytes-into-a-region-of-size-between-and
|   `-- 
drivers-gpu-drm-nouveau-nouveau_backlight.c:error:d-directive-output-may-be-truncated-writing-between-and-bytes-into-a-region-of-size
|-- s390-allyesconfig
|   |-- 
drivers-gpu-drm-imx-ipuv3-imx-ldb.c:error:_sel-directive-output-may-be-truncated-writing-bytes-into-a-region-of-size-between-and
|   `-- 

Re: [PATCH 06/12] drm/client: Constify modes

2024-04-06 Thread kernel test robot
Hi Ville,

kernel test robot noticed the following build errors:

[auto build test ERROR on drm-misc/drm-misc-next]
[also build test ERROR on drm-intel/for-linux-next 
drm-intel/for-linux-next-fixes drm-tip/drm-tip linus/master v6.9-rc2 
next-20240405]
[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/Ville-Syrjala/drm-client-Fully-protect-modes-with-dev-mode_config-mutex/20240405-043540
base:   git://anongit.freedesktop.org/drm/drm-misc drm-misc-next
patch link:
https://lore.kernel.org/r/20240404203336.10454-7-ville.syrjala%40linux.intel.com
patch subject: [PATCH 06/12] drm/client: Constify modes
config: hexagon-allyesconfig 
(https://download.01.org/0day-ci/archive/20240407/202404070528.ngbakkh3-...@intel.com/config)
compiler: clang version 19.0.0git (https://github.com/llvm/llvm-project 
546dc2245ffc4cccd0b05b58b7a5955e355a3b27)
reproduce (this is a W=1 build): 
(https://download.01.org/0day-ci/archive/20240407/202404070528.ngbakkh3-...@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 
| Closes: 
https://lore.kernel.org/oe-kbuild-all/202404070528.ngbakkh3-...@intel.com/

All errors (new ones prefixed by >>):

   In file included from drivers/gpu/drm/drm_client_modeset.c:16:
   In file included from include/drm/drm_atomic.h:31:
   In file included from include/drm/drm_crtc.h:32:
   In file included from include/drm/drm_modes.h:33:
   In file included from include/drm/drm_connector.h:32:
   In file included from include/drm/drm_util.h:35:
   In file included from include/linux/interrupt.h:11:
   In file included from include/linux/hardirq.h:11:
   In file included from ./arch/hexagon/include/generated/asm/hardirq.h:1:
   In file included from include/asm-generic/hardirq.h:17:
   In file included from include/linux/irq.h:20:
   In file included from include/linux/io.h:13:
   In file included from arch/hexagon/include/asm/io.h:328:
   include/asm-generic/io.h:547:31: error: performing pointer arithmetic on a 
null pointer has undefined behavior [-Werror,-Wnull-pointer-arithmetic]
 547 | val = __raw_readb(PCI_IOBASE + addr);
 |   ~~ ^
   include/asm-generic/io.h:560:61: error: performing pointer arithmetic on a 
null pointer has undefined behavior [-Werror,-Wnull-pointer-arithmetic]
 560 | val = __le16_to_cpu((__le16 __force)__raw_readw(PCI_IOBASE + 
addr));
 | ~~ ^
   include/uapi/linux/byteorder/little_endian.h:37:51: note: expanded from 
macro '__le16_to_cpu'
  37 | #define __le16_to_cpu(x) ((__force __u16)(__le16)(x))
 |   ^
   In file included from drivers/gpu/drm/drm_client_modeset.c:16:
   In file included from include/drm/drm_atomic.h:31:
   In file included from include/drm/drm_crtc.h:32:
   In file included from include/drm/drm_modes.h:33:
   In file included from include/drm/drm_connector.h:32:
   In file included from include/drm/drm_util.h:35:
   In file included from include/linux/interrupt.h:11:
   In file included from include/linux/hardirq.h:11:
   In file included from ./arch/hexagon/include/generated/asm/hardirq.h:1:
   In file included from include/asm-generic/hardirq.h:17:
   In file included from include/linux/irq.h:20:
   In file included from include/linux/io.h:13:
   In file included from arch/hexagon/include/asm/io.h:328:
   include/asm-generic/io.h:573:61: error: performing pointer arithmetic on a 
null pointer has undefined behavior [-Werror,-Wnull-pointer-arithmetic]
 573 | val = __le32_to_cpu((__le32 __force)__raw_readl(PCI_IOBASE + 
addr));
 | ~~ ^
   include/uapi/linux/byteorder/little_endian.h:35:51: note: expanded from 
macro '__le32_to_cpu'
  35 | #define __le32_to_cpu(x) ((__force __u32)(__le32)(x))
 |   ^
   In file included from drivers/gpu/drm/drm_client_modeset.c:16:
   In file included from include/drm/drm_atomic.h:31:
   In file included from include/drm/drm_crtc.h:32:
   In file included from include/drm/drm_modes.h:33:
   In file included from include/drm/drm_connector.h:32:
   In file included from include/drm/drm_util.h:35:
   In file included from include/linux/interrupt.h:11:
   In file included from include/linux/hardirq.h:11:
   In file included from ./arch/hexagon/include/generated/asm/hardirq.h:1:
   In file included from include/asm-generic/hardirq.h:17:
   In file included from include/linux/irq.h:20:
   In file included from include/linux/io.h:13:
   In file in

[linux-next:master] BUILD REGRESSION 8568bb2ccc278f344e6ac44af6ed010a90aa88dc

2024-04-05 Thread kernel test robot
tree/branch: 
https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
branch HEAD: 8568bb2ccc278f344e6ac44af6ed010a90aa88dc  Add linux-next specific 
files for 20240405

Error/Warning reports:

https://lore.kernel.org/oe-kbuild-all/202404051333.7und7ppw-...@intel.com
https://lore.kernel.org/oe-kbuild-all/202404051423.eiaxlwhx-...@intel.com
https://lore.kernel.org/oe-kbuild-all/202404051659.aawukguq-...@intel.com
https://lore.kernel.org/oe-kbuild-all/202404052022.cwf2ilbp-...@intel.com

Error/Warning: (recently discovered and may have been fixed)

aarch64-linux-ld: kernel/bpf/verifier.c:20223:(.text+0xdbb4): undefined 
reference to `__SCK__perf_snapshot_branch_stack'
aarch64-linux-ld: verifier.c:(.text+0x17c3c): undefined reference to 
`__SCK__perf_snapshot_branch_stack'
drivers/i2c/busses/i2c-i801.c:1407:(.text+0x1d2ef4a): undefined reference to 
`i2c_root_adapter'
kernel/bpf/verifier.c:20223:(.text+0xdba4): dangerous relocation: unsupported 
relocation
loongarch64-linux-ld: kernel/bpf/verifier.c:20223:(.text+0xa818): undefined 
reference to `__SCK__perf_snapshot_branch_stack'
loongarch64-linux-ld: verifier.c:(.text+0xa964): undefined reference to 
`__SCK__perf_snapshot_branch_stack'
mips64el-linux-ld: verifier.c:(.text.do_misc_fixups+0xd9c): undefined reference 
to `__SCK__perf_snapshot_branch_stack'
riscv32-linux-ld: section .data LMA [00369000,00907967] overlaps section .text 
LMA [0007899c,01a6a6af]
s390-linux-ld: verifier.c:(.text+0x13038): undefined reference to 
`__SCK__perf_snapshot_branch_stack'
verifier.c:(.text+0x17c14): relocation truncated to fit: 
R_AARCH64_ADR_PREL_PG_HI21 against undefined symbol 
`__SCK__perf_snapshot_branch_stack'
verifier.c:(.text+0xa960): undefined reference to 
`__SCK__perf_snapshot_branch_stack'
verifier.c:(.text+0xadd0): dangerous relocation: unsupported relocation
verifier.c:(.text.do_misc_fixups+0xd98): undefined reference to 
`__SCK__perf_snapshot_branch_stack'

Unverified Error/Warning (likely false positive, please contact us if 
interested):

lib/alloc_tag.c:142 alloc_tag_init() warn: passing zero to 'PTR_ERR'

Error/Warning ids grouped by kconfigs:

gcc_recent_errors
|-- alpha-allyesconfig
|   |-- 
drivers-gpu-drm-imx-ipuv3-imx-ldb.c:error:_sel-directive-output-may-be-truncated-writing-bytes-into-a-region-of-size-between-and
|   `-- 
drivers-gpu-drm-nouveau-nouveau_backlight.c:error:d-directive-output-may-be-truncated-writing-between-and-bytes-into-a-region-of-size
|-- alpha-randconfig-r123-20240405
|   `-- 
kernel-bpf-verifier.c:sparse:sparse:cast-truncates-bits-from-constant-value-(fffc-becomes-)
|-- arm-allmodconfig
|   |-- 
drivers-gpu-drm-imx-ipuv3-imx-ldb.c:error:_sel-directive-output-may-be-truncated-writing-bytes-into-a-region-of-size-between-and
|   `-- 
drivers-gpu-drm-nouveau-nouveau_backlight.c:error:d-directive-output-may-be-truncated-writing-between-and-bytes-into-a-region-of-size
|-- arm-allyesconfig
|   |-- 
drivers-gpu-drm-imx-ipuv3-imx-ldb.c:error:_sel-directive-output-may-be-truncated-writing-bytes-into-a-region-of-size-between-and
|   `-- 
drivers-gpu-drm-nouveau-nouveau_backlight.c:error:d-directive-output-may-be-truncated-writing-between-and-bytes-into-a-region-of-size
|-- arm-hisi_defconfig
|   |-- 
drm_dp_mst_topology.c:(.text):undefined-reference-to-__drm_atomic_helper_private_obj_duplicate_state
|   `-- 
drm_dp_mst_topology.c:(.text):undefined-reference-to-drm_kms_helper_hotplug_event
|-- arm64-randconfig-c041-20221104
|   |-- 
aarch64-linux-ld:kernel-bpf-verifier.c:(.text):undefined-reference-to-__SCK__perf_snapshot_branch_stack
|   `-- 
kernel-bpf-verifier.c:(.text):dangerous-relocation:unsupported-relocation
|-- arm64-randconfig-r013-20230703
|   |-- 
aarch64-linux-ld:verifier.c:(.text):undefined-reference-to-__SCK__perf_snapshot_branch_stack
|   `-- 
verifier.c:(.text):relocation-truncated-to-fit:R_AARCH64_ADR_PREL_PG_HI21-against-undefined-symbol-__SCK__perf_snapshot_branch_stack
|-- arm64-randconfig-r032-20220702
|   `-- verifier.c:(.text):dangerous-relocation:unsupported-relocation
|-- csky-allmodconfig
|   |-- 
drivers-gpu-drm-imx-ipuv3-imx-ldb.c:error:_sel-directive-output-may-be-truncated-writing-bytes-into-a-region-of-size-between-and
|   `-- 
drivers-gpu-drm-nouveau-nouveau_backlight.c:error:d-directive-output-may-be-truncated-writing-between-and-bytes-into-a-region-of-size
|-- csky-allyesconfig
|   |-- 
drivers-gpu-drm-imx-ipuv3-imx-ldb.c:error:_sel-directive-output-may-be-truncated-writing-bytes-into-a-region-of-size-between-and
|   `-- 
drivers-gpu-drm-nouveau-nouveau_backlight.c:error:d-directive-output-may-be-truncated-writing-between-and-bytes-into-a-region-of-size
|-- loongarch-allmodconfig
|   |-- 
drivers-gpu-drm-imx-ipuv3-imx-ldb.c:error:_sel-directive-output-may-be-truncated-writing-bytes-into-a-region-of-size-between-and
|   `-- 
drivers-gpu-drm-nouveau-nouveau_backlight.c:error:d-directive-output-may-be-truncated-writing-between-and-bytes-into-a-region-of-size
|-- 

Re: [PATCH 06/12] drm/client: Constify modes

2024-04-05 Thread kernel test robot
Hi Ville,

kernel test robot noticed the following build warnings:

[auto build test WARNING on drm-misc/drm-misc-next]
[also build test WARNING on drm-intel/for-linux-next 
drm-intel/for-linux-next-fixes drm-tip/drm-tip linus/master v6.9-rc2 
next-20240405]
[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/Ville-Syrjala/drm-client-Fully-protect-modes-with-dev-mode_config-mutex/20240405-043540
base:   git://anongit.freedesktop.org/drm/drm-misc drm-misc-next
patch link:
https://lore.kernel.org/r/20240404203336.10454-7-ville.syrjala%40linux.intel.com
patch subject: [PATCH 06/12] drm/client: Constify modes
config: i386-randconfig-012-20240405 
(https://download.01.org/0day-ci/archive/20240405/202404051422.bpyvk6tp-...@intel.com/config)
compiler: gcc-7 (Ubuntu 7.5.0-6ubuntu2) 7.5.0
reproduce (this is a W=1 build): 
(https://download.01.org/0day-ci/archive/20240405/202404051422.bpyvk6tp-...@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 
| Closes: 
https://lore.kernel.org/oe-kbuild-all/202404051422.bpyvk6tp-...@intel.com/

All warnings (new ones prefixed by >>):

   In file included from drivers/gpu/drm/drm_client_modeset.c:1241:0:
   drivers/gpu/drm/tests/drm_client_modeset_test.c: In function 
'drm_test_pick_cmdline_res_1920_1080_60':
>> drivers/gpu/drm/tests/drm_client_modeset_test.c:108:7: warning: assignment 
>> discards 'const' qualifier from pointer target type [-Wdiscarded-qualifiers]
 mode = drm_connector_pick_cmdline_mode(connector);
  ^


vim +/const +108 drivers/gpu/drm/tests/drm_client_modeset_test.c

8fc0380f6ba7e9 Maxime Ripard 2022-11-14   84  
8fc0380f6ba7e9 Maxime Ripard 2022-11-14   85  static void 
drm_test_pick_cmdline_res_1920_1080_60(struct kunit *test)
8fc0380f6ba7e9 Maxime Ripard 2022-11-14   86  {
8fc0380f6ba7e9 Maxime Ripard 2022-11-14   87struct 
drm_client_modeset_test_priv *priv = test->priv;
8fc0380f6ba7e9 Maxime Ripard 2022-11-14   88struct drm_device *drm = 
priv->drm;
8fc0380f6ba7e9 Maxime Ripard 2022-11-14   89struct drm_connector *connector 
= >connector;
8fc0380f6ba7e9 Maxime Ripard 2022-11-14   90struct drm_cmdline_mode 
*cmdline_mode = >cmdline_mode;
8fc0380f6ba7e9 Maxime Ripard 2022-11-14   91struct drm_display_mode 
*expected_mode, *mode;
8fc0380f6ba7e9 Maxime Ripard 2022-11-14   92const char *cmdline = 
"1920x1080@60";
8fc0380f6ba7e9 Maxime Ripard 2022-11-14   93int ret;
8fc0380f6ba7e9 Maxime Ripard 2022-11-14   94  
8fc0380f6ba7e9 Maxime Ripard 2022-11-14   95expected_mode = 
drm_mode_find_dmt(priv->drm, 1920, 1080, 60, false);
8fc0380f6ba7e9 Maxime Ripard 2022-11-14   96KUNIT_ASSERT_NOT_NULL(test, 
expected_mode);
8fc0380f6ba7e9 Maxime Ripard 2022-11-14   97  
8fc0380f6ba7e9 Maxime Ripard 2022-11-14   98KUNIT_ASSERT_TRUE(test,
8fc0380f6ba7e9 Maxime Ripard 2022-11-14   99  
drm_mode_parse_command_line_for_connector(cmdline,
8fc0380f6ba7e9 Maxime Ripard 2022-11-14  100
connector,
8fc0380f6ba7e9 Maxime Ripard 2022-11-14  101
cmdline_mode));
8fc0380f6ba7e9 Maxime Ripard 2022-11-14  102  
8fc0380f6ba7e9 Maxime Ripard 2022-11-14  103
mutex_lock(>mode_config.mutex);
8fc0380f6ba7e9 Maxime Ripard 2022-11-14  104ret = 
drm_helper_probe_single_connector_modes(connector, 1920, 1080);
8fc0380f6ba7e9 Maxime Ripard 2022-11-14  105
mutex_unlock(>mode_config.mutex);
8fc0380f6ba7e9 Maxime Ripard 2022-11-14  106KUNIT_ASSERT_GT(test, ret, 0);
8fc0380f6ba7e9 Maxime Ripard 2022-11-14  107  
8fc0380f6ba7e9 Maxime Ripard 2022-11-14 @108mode = 
drm_connector_pick_cmdline_mode(connector);
8fc0380f6ba7e9 Maxime Ripard 2022-11-14  109KUNIT_ASSERT_NOT_NULL(test, 
mode);
8fc0380f6ba7e9 Maxime Ripard 2022-11-14  110  
8fc0380f6ba7e9 Maxime Ripard 2022-11-14  111KUNIT_EXPECT_TRUE(test, 
drm_mode_equal(expected_mode, mode));
8fc0380f6ba7e9 Maxime Ripard 2022-11-14  112  }
8fc0380f6ba7e9 Maxime Ripard 2022-11-14  113  

-- 
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki


[linux-next:master] BUILD REGRESSION 2b3d5988ae2cb5cd945ddbc653f0a71706231fdd

2024-04-04 Thread kernel test robot
tree/branch: 
https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
branch HEAD: 2b3d5988ae2cb5cd945ddbc653f0a71706231fdd  Add linux-next specific 
files for 20240404

Error/Warning reports:

https://lore.kernel.org/oe-kbuild-all/202404041707.4bl4ifti-...@intel.com
https://lore.kernel.org/oe-kbuild-all/202404041832.tmsatkyb-...@intel.com
https://lore.kernel.org/oe-kbuild-all/202404042206.mjaqc32x-...@intel.com
https://lore.kernel.org/oe-kbuild-all/202404042327.jrpt81kp-...@intel.com

Error/Warning: (recently discovered and may have been fixed)

ERROR: modpost: "__aeabi_d2ulz" [drivers/gpu/drm/amd/amdgpu/amdgpu.ko] 
undefined!
ERROR: modpost: "__aeabi_l2d" [drivers/gpu/drm/amd/amdgpu/amdgpu.ko] undefined!
drivers/input/serio/parkbd.c:168:10: error: '__section__' attribute only 
applies to functions, global variables, Objective-C methods, and Objective-C 
properties
drivers/input/serio/parkbd.c:168:10: error: 'section' attribute only applies to 
functions, global variables, Objective-C methods, and Objective-C properties
drivers/input/serio/parkbd.c:168:10: error: non-extern declaration of 
'__pcpu_unique__alloc_tag_cntr' follows extern declaration
drivers/input/serio/ps2-gpio.c:408:10: error: '__section__' attribute only 
applies to functions, global variables, Objective-C methods, and Objective-C 
properties
drivers/input/serio/ps2-gpio.c:408:10: error: 'section' attribute only applies 
to functions, global variables, Objective-C methods, and Objective-C properties
drivers/input/serio/ps2-gpio.c:408:10: error: non-extern declaration of 
'__pcpu_unique__alloc_tag_cntr' follows extern declaration
drivers/input/serio/ps2mult.c:130:10: error: '__section__' attribute only 
applies to functions, global variables, Objective-C methods, and Objective-C 
properties
drivers/input/serio/ps2mult.c:130:10: error: 'section' attribute only applies 
to functions, global variables, Objective-C methods, and Objective-C properties
drivers/input/serio/ps2mult.c:130:10: error: non-extern declaration of 
'__pcpu_unique__alloc_tag_cntr' follows extern declaration
drivers/input/serio/serio_raw.c:95:11: error: '__section__' attribute only 
applies to functions, global variables, Objective-C methods, and Objective-C 
properties
drivers/input/serio/serio_raw.c:95:11: error: 'section' attribute only applies 
to functions, global variables, Objective-C methods, and Objective-C properties
drivers/input/serio/serio_raw.c:95:11: error: non-extern declaration of 
'__pcpu_unique__alloc_tag_cntr' follows extern declaration
include/linux/mempool.h:105:9: error: '__section__' attribute only applies to 
functions, global variables, Objective-C methods, and Objective-C properties
include/linux/mempool.h:105:9: error: 'section' attribute only applies to 
functions, global variables, Objective-C methods, and Objective-C properties
include/linux/mempool.h:105:9: error: non-extern declaration of 
'__pcpu_unique__alloc_tag_cntr' follows extern declaration
include/linux/mempool.h:105:9: error: non-extern declaration of 
'_alloc_tag_cntr' follows extern declaration
include/linux/mempool.h:105:9: error: weak declaration cannot have internal 
linkage
ld.lld: error: undefined symbol: i2c_root_adapter
powerpc64-linux-ld: warning: orphan section `.bss..Lubsan_data249' from 
`kernel/ptrace.o' being placed in section `.bss..Lubsan_data249'

Unverified Error/Warning (likely false positive, please contact us if 
interested):

include/linux/mm_types.h:1175:17: error: '__section__' attribute only applies 
to functions, global variables, Objective-C methods, and Objective-C properties
include/linux/mm_types.h:1175:17: error: 'section' attribute only applies to 
functions, global variables, Objective-C methods, and Objective-C properties
include/linux/mm_types.h:1175:17: error: non-extern declaration of 
'__pcpu_unique__alloc_tag_cntr' follows extern declaration
include/linux/mm_types.h:1175:17: error: non-extern declaration of 
'_alloc_tag_cntr' follows extern declaration
include/linux/mm_types.h:1175:17: error: weak declaration cannot have internal 
linkage
{standard input}:722: Warning: overflow in branch to .L153; converted into 
longer instruction sequence
{standard input}:733: Warning: overflow in branch to .L155; converted into 
longer instruction sequence

Error/Warning ids grouped by kconfigs:

gcc_recent_errors
|-- alpha-allnoconfig
|   |-- 
mm-mempool.c:warning:Function-parameter-or-struct-member-gfp_mask-not-described-in-mempool_create_node
|   `-- 
mm-mempool.c:warning:Function-parameter-or-struct-member-node_id-not-described-in-mempool_create_node
|-- alpha-allyesconfig
|   |-- 
drivers-gpu-drm-imx-ipuv3-imx-ldb.c:error:_sel-directive-output-may-be-truncated-writing-bytes-into-a-region-of-size-between-and
|   |-- 
drivers-gpu-drm-nouveau-nouveau_backlight.c:error:d-directive-output-may-be-truncated-writing-between-and-bytes-into-a-region-of-size
|   |-- 

[linux-next:master] BUILD REGRESSION 727900b675b749c40ba1f6669c7ae5eb7eb8e837

2024-04-03 Thread kernel test robot
tree/branch: 
https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
branch HEAD: 727900b675b749c40ba1f6669c7ae5eb7eb8e837  Add linux-next specific 
files for 20240403

Error/Warning reports:

https://lore.kernel.org/oe-kbuild-all/202404031246.aq5yr5ko-...@intel.com
https://lore.kernel.org/oe-kbuild-all/202404031346.wpihnpyf-...@intel.com
https://lore.kernel.org/oe-kbuild-all/202404032101.skzrxcwh-...@intel.com

Error/Warning: (recently discovered and may have been fixed)

fs/smb/client/file.c:728:12: warning: variable 'rc' is used uninitialized 
whenever 'if' condition is false [-Wsometimes-uninitialized]
mm/kasan/hw_tags.c:280:14: warning: assignment to 'struct vm_struct *' from 
'int' makes pointer from integer without a cast [-Wint-conversion]
mm/kasan/hw_tags.c:280:16: error: implicit declaration of function 
'find_vm_area'; did you mean 'find_vma_prev'? 
[-Werror=implicit-function-declaration]
mm/kasan/hw_tags.c:284:29: error: invalid use of undefined type 'struct 
vm_struct'
riscv32-linux-ld: section .data LMA [001f9000,009465d7] overlaps section .text 
LMA [000a7e84,0177d68b]

Unverified Error/Warning (likely false positive, please contact us if 
interested):

fs/smb/client/file.c:619 serverclose_work() error: uninitialized symbol 'rc'.
fs/smb/client/file.c:732 _cifsFileInfo_put() error: uninitialized symbol 'rc'.

Error/Warning ids grouped by kconfigs:

gcc_recent_errors
|-- alpha-allnoconfig
|   |-- 
mm-mempool.c:warning:Function-parameter-or-struct-member-gfp_mask-not-described-in-mempool_create_node
|   `-- 
mm-mempool.c:warning:Function-parameter-or-struct-member-node_id-not-described-in-mempool_create_node
|-- alpha-allyesconfig
|   |-- 
drivers-gpu-drm-imx-ipuv3-imx-ldb.c:error:_sel-directive-output-may-be-truncated-writing-bytes-into-a-region-of-size-between-and
|   |-- 
drivers-gpu-drm-nouveau-nouveau_backlight.c:error:d-directive-output-may-be-truncated-writing-between-and-bytes-into-a-region-of-size
|   |-- 
mm-mempool.c:warning:Function-parameter-or-struct-member-gfp_mask-not-described-in-mempool_create_node
|   `-- 
mm-mempool.c:warning:Function-parameter-or-struct-member-node_id-not-described-in-mempool_create_node
|-- alpha-defconfig
|   |-- 
mm-mempool.c:warning:Function-parameter-or-struct-member-gfp_mask-not-described-in-mempool_create_node
|   `-- 
mm-mempool.c:warning:Function-parameter-or-struct-member-node_id-not-described-in-mempool_create_node
|-- arm-allmodconfig
|   |-- 
drivers-gpu-drm-imx-ipuv3-imx-ldb.c:error:_sel-directive-output-may-be-truncated-writing-bytes-into-a-region-of-size-between-and
|   |-- 
drivers-gpu-drm-nouveau-nouveau_backlight.c:error:d-directive-output-may-be-truncated-writing-between-and-bytes-into-a-region-of-size
|   |-- 
mm-mempool.c:warning:Function-parameter-or-struct-member-gfp_mask-not-described-in-mempool_create_node
|   `-- 
mm-mempool.c:warning:Function-parameter-or-struct-member-node_id-not-described-in-mempool_create_node
|-- arm-allyesconfig
|   |-- 
drivers-gpu-drm-imx-ipuv3-imx-ldb.c:error:_sel-directive-output-may-be-truncated-writing-bytes-into-a-region-of-size-between-and
|   |-- 
drivers-gpu-drm-nouveau-nouveau_backlight.c:error:d-directive-output-may-be-truncated-writing-between-and-bytes-into-a-region-of-size
|   |-- 
mm-mempool.c:warning:Function-parameter-or-struct-member-gfp_mask-not-described-in-mempool_create_node
|   `-- 
mm-mempool.c:warning:Function-parameter-or-struct-member-node_id-not-described-in-mempool_create_node
|-- arm-aspeed_g5_defconfig
|   |-- 
mm-mempool.c:warning:Function-parameter-or-struct-member-gfp_mask-not-described-in-mempool_create_node
|   `-- 
mm-mempool.c:warning:Function-parameter-or-struct-member-node_id-not-described-in-mempool_create_node
|-- arm-randconfig-001-20240403
|   |-- 
mm-mempool.c:warning:Function-parameter-or-struct-member-gfp_mask-not-described-in-mempool_create_node
|   `-- 
mm-mempool.c:warning:Function-parameter-or-struct-member-node_id-not-described-in-mempool_create_node
|-- arm-randconfig-002-20240403
|   |-- 
mm-mempool.c:warning:Function-parameter-or-struct-member-gfp_mask-not-described-in-mempool_create_node
|   `-- 
mm-mempool.c:warning:Function-parameter-or-struct-member-node_id-not-described-in-mempool_create_node
|-- arm-randconfig-004-20240403
|   |-- 
mm-mempool.c:warning:Function-parameter-or-struct-member-gfp_mask-not-described-in-mempool_create_node
|   `-- 
mm-mempool.c:warning:Function-parameter-or-struct-member-node_id-not-described-in-mempool_create_node
|-- arm-randconfig-r061-20240403
|   |-- 
mm-mempool.c:warning:Function-parameter-or-struct-member-gfp_mask-not-described-in-mempool_create_node
|   `-- 
mm-mempool.c:warning:Function-parameter-or-struct-member-node_id-not-described-in-mempool_create_node
|-- arm64-allnoconfig
|   |-- 
mm-mempool.c:warning:Function-parameter-or-struct-member-gfp_mask-not-described-in-mempool_create_node
|   `-- 

[linux-next:master] BUILD REGRESSION c0b832517f627ead3388c6f0c74e8ac10ad5774b

2024-04-02 Thread kernel test robot
tree/branch: 
https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
branch HEAD: c0b832517f627ead3388c6f0c74e8ac10ad5774b  Add linux-next specific 
files for 20240402

Error/Warning reports:

https://lore.kernel.org/oe-kbuild-all/202404021504.ytp51bl3-...@intel.com
https://lore.kernel.org/oe-kbuild-all/202404021556.0jvcnc13-...@intel.com
https://lore.kernel.org/oe-kbuild-all/202404021638.qkhbdq4e-...@intel.com
https://lore.kernel.org/oe-kbuild-all/202404021700.lbyyzgfd-...@intel.com
https://lore.kernel.org/oe-kbuild-all/202404022106.mywpypit-...@intel.com

Error/Warning: (recently discovered and may have been fixed)

ERROR: modpost: "__drm_atomic_helper_private_obj_duplicate_state" 
[drivers/gpu/drm/display/drm_display_helper.ko] undefined!
ERROR: modpost: "drm_kms_helper_hotplug_event" 
[drivers/gpu/drm/display/drm_display_helper.ko] undefined!
arch/csky/include/asm/cmpxchg.h:138:25: error: implicit declaration of function 
'cmpxchg_emu_u8' [-Werror=implicit-function-declaration]
arch/csky/include/asm/cmpxchg.h:141:25: error: implicit declaration of function 
'cmpxchg_emu_u16' [-Werror=implicit-function-declaration]
arch/riscv/include/asm/cmpxchg.h:329:23: warning: assignment to 'const struct 
gre_protocol *' from 'uintptr_t' {aka 'long unsigned int'} makes pointer from 
integer without a cast [-Wint-conversion]
arch/riscv/include/asm/cmpxchg.h:329:23: warning: assignment to 'struct 
bdi_writeback *' from 'uintptr_t' {aka 'long unsigned int'} makes pointer from 
integer without a cast [-Wint-conversion]
arch/riscv/include/asm/cmpxchg.h:329:23: warning: assignment to 'struct 
rtrs_clt_path *' from 'uintptr_t' {aka 'long unsigned int'} makes pointer from 
integer without a cast [-Wint-conversion]
arch/riscv/include/asm/cmpxchg.h:329:23: warning: assignment to 'struct 
tty_struct *' from 'uintptr_t' {aka 'long unsigned int'} makes pointer from 
integer without a cast [-Wint-conversion]
arch/riscv/include/asm/cmpxchg.h:329:23: warning: assignment to 
'z_erofs_next_pcluster_t' {aka 'void *'} from 'uintptr_t' {aka 'long unsigned 
int'} makes pointer from integer without a cast [-Wint-conversion]
cfi_probe.c:(.xiptext+0xdb): dangerous relocation: windowed longcall crosses 
1GB boundary; return may fail: __kmalloc_noprof
cfi_util.c:(.xiptext+0x40b): dangerous relocation: windowed longcall crosses 
1GB boundary; return may fail: __kmalloc_noprof
drivers/gpu/drm/display/drm_dp_mst_topology.c:5074:(.text+0x4da0): undefined 
reference to `drm_kms_helper_hotplug_event'
drivers/gpu/drm/display/drm_dp_mst_topology.c:5088:(.text+0x40a8): undefined 
reference to `__drm_atomic_helper_private_obj_duplicate_state'
drivers/gpu/drm/lima/lima_drv.c:387:13: error: cast to smaller integer type 
'enum lima_gpu_id' from 'const void *' [-Werror,-Wvoid-pointer-to-enum-cast]
drivers/gpu/drm/panthor/panthor_sched.c:2048:6: error: variable 'csg_mod_mask' 
set but not used [-Werror,-Wunused-but-set-variable]
drivers/gpu/drm/pl111/pl111_versatile.c:488:24: error: cast to smaller integer 
type 'enum versatile_clcd' from 'const void *' 
[-Werror,-Wvoid-pointer-to-enum-cast]
drivers/gpu/drm/qxl/qxl_cmd.c:424:6: error: variable 'count' set but not used 
[-Werror,-Wunused-but-set-variable]
drivers/gpu/drm/qxl/qxl_ioctl.c:148:14: error: variable 'num_relocs' set but 
not used [-Werror,-Wunused-but-set-variable]
drivers/s390/char/hmcdrv_cache.c:221:13: error: '__section__' attribute only 
applies to functions, global variables, Objective-C methods, and Objective-C 
properties
drivers/s390/char/hmcdrv_cache.c:221:13: error: 'section' attribute only 
applies to functions, global variables, Objective-C methods, and Objective-C 
properties
drivers/s390/char/hmcdrv_cache.c:221:13: error: non-extern declaration of 
'__pcpu_unique__alloc_tag_cntr' follows extern declaration
drivers/s390/char/hmcdrv_ftp.c:196:21: error: '__section__' attribute only 
applies to functions, global variables, Objective-C methods, and Objective-C 
properties
drivers/s390/char/hmcdrv_ftp.c:196:21: error: 'section' attribute only applies 
to functions, global variables, Objective-C methods, and Objective-C properties
drivers/s390/char/hmcdrv_ftp.c:196:21: error: non-extern declaration of 
'__pcpu_unique__alloc_tag_cntr' follows extern declaration
drivers/s390/char/hmcdrv_ftp.c:196:21: error: non-extern declaration of 
'_alloc_tag_cntr' follows extern declaration
drivers/s390/char/hmcdrv_ftp.c:196:21: error: weak declaration cannot have 
internal linkage
drm_dp_helper.c:(.text+0x36e8): undefined reference to 
`devm_backlight_device_register'
drm_dp_mst_topology.c:(.text+0x350c): undefined reference to 
`__drm_atomic_helper_private_obj_duplicate_state'
drm_dp_mst_topology.c:(.text+0x3f00): undefined reference to 
`drm_kms_helper_hotplug_event'
include/asm-generic/io.h:547:31: error: performing pointer arithmetic on a null 
pointer has undefined behavior [-Werror,-Wnull-pointer-arithmetic]
include/linux/alloc_tag.h:43:2: error: "Memory allocation profiling 

Re: [PATCH 2/2] drm/i915/hdcp: Fix get remote hdcp capability function

2024-04-01 Thread kernel test robot
Hi Suraj,

kernel test robot noticed the following build warnings:

[auto build test WARNING on drm-intel/for-linux-next]
[also build test WARNING on drm-intel/for-linux-next-fixes drm-tip/drm-tip 
linus/master v6.9-rc2 next-20240328]
[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/Suraj-Kandpal/drm-i915-display-Initialize-capability-variables/20240401-110451
base:   git://anongit.freedesktop.org/drm-intel for-linux-next
patch link:
https://lore.kernel.org/r/20240401030106.274787-3-suraj.kandpal%40intel.com
patch subject: [PATCH 2/2] drm/i915/hdcp: Fix get remote hdcp capability 
function
config: arm-randconfig-001-20240401 
(https://download.01.org/0day-ci/archive/20240401/202404011741.3ktdulwv-...@intel.com/config)
compiler: clang version 14.0.6 (https://github.com/llvm/llvm-project.git 
f28c006a5895fc0e329fe15fead81e37457cb1d1)
reproduce (this is a W=1 build): 
(https://download.01.org/0day-ci/archive/20240401/202404011741.3ktdulwv-...@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 
| Closes: 
https://lore.kernel.org/oe-kbuild-all/202404011741.3ktdulwv-...@intel.com/

All warnings (new ones prefixed by >>):

>> drivers/gpu/drm/i915/display/intel_dp_hdcp.c:697:17: warning: expression 
>> which evaluates to zero treated as a null pointer constant of type 'bool *' 
>> (aka '_Bool *') [-Wnon-literal-null-conversion]
   hdcp_capable = false;
  ^
   drivers/gpu/drm/i915/display/intel_dp_hdcp.c:698:18: warning: expression 
which evaluates to zero treated as a null pointer constant of type 'bool *' 
(aka '_Bool *') [-Wnon-literal-null-conversion]
   hdcp2_capable = false;
   ^
   2 warnings generated.


vim +697 drivers/gpu/drm/i915/display/intel_dp_hdcp.c

   683  
   684  static
   685  int intel_dp_hdcp_get_remote_capability(struct intel_connector 
*connector,
   686  bool *hdcp_capable,
   687  bool *hdcp2_capable)
   688  {
   689  struct drm_i915_private *i915 = to_i915(connector->base.dev);
   690  struct drm_dp_aux *aux = >port->aux;
   691  u8 bcaps;
   692  int ret;
   693  
   694  if (!intel_encoder_is_mst(connector->encoder))
   695  return -EINVAL;
   696  
 > 697  hdcp_capable = false;
   698  hdcp2_capable = false;
   699  ret =  _intel_dp_hdcp2_get_capability(aux, hdcp2_capable);
   700  if (ret)
   701  drm_dbg_kms(>drm,
   702  "HDCP2 DPCD capability read failed err: 
%d\n", ret);
   703  
   704  ret = intel_dp_hdcp_read_bcaps(aux, i915, );
   705  if (ret)
   706  return ret;
   707  
   708  *hdcp_capable = bcaps & DP_BCAPS_HDCP_CAPABLE;
   709  
   710  return 0;
   711  }
   712  

-- 
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki


[drm-tip:drm-tip 4/11] drivers/gpu/drm/amd/amdgpu/amdgpu_vcn.c:105:73: error: '.bin' directive output may be truncated writing 4 bytes into a region of size between 2 and 31

2024-03-23 Thread kernel test robot
tree:   git://anongit.freedesktop.org/drm/drm-tip drm-tip
head:   657dd8fcd2f1d1205c6f98fdb8b60915228991d1
commit: 0885186926a13c697d78f5af03f32445414b6ad5 [4/11] Merge remote-tracking 
branch 'drm-misc/drm-misc-next' into drm-tip
config: microblaze-allmodconfig 
(https://download.01.org/0day-ci/archive/20240324/202403240115.1lao588s-...@intel.com/config)
compiler: microblaze-linux-gcc (GCC) 13.2.0
reproduce (this is a W=1 build): 
(https://download.01.org/0day-ci/archive/20240324/202403240115.1lao588s-...@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 
| Closes: 
https://lore.kernel.org/oe-kbuild-all/202403240115.1lao588s-...@intel.com/

All errors (new ones prefixed by >>):

   drivers/gpu/drm/amd/amdgpu/amdgpu_vcn.c: In function 'amdgpu_vcn_early_init':
   drivers/gpu/drm/amd/amdgpu/amdgpu_vcn.c:102:66: error: 'snprintf' output may 
be truncated before the last format character [-Werror=format-truncation=]
 102 | snprintf(fw_name, sizeof(fw_name), "amdgpu/%s.bin", 
ucode_prefix);
 |  ^
   drivers/gpu/drm/amd/amdgpu/amdgpu_vcn.c:102:17: note: 'snprintf' output 
between 12 and 41 bytes into a destination of size 40
 102 | snprintf(fw_name, sizeof(fw_name), "amdgpu/%s.bin", 
ucode_prefix);
 | 
^
>> drivers/gpu/drm/amd/amdgpu/amdgpu_vcn.c:105:73: error: '.bin' directive 
>> output may be truncated writing 4 bytes into a region of size between 2 and 
>> 31 [-Werror=format-truncation=]
 105 | snprintf(fw_name, sizeof(fw_name), 
"amdgpu/%s_%d.bin", ucode_prefix, i);
 |  
   ^~~~
   drivers/gpu/drm/amd/amdgpu/amdgpu_vcn.c:105:25: note: 'snprintf' output 
between 14 and 43 bytes into a destination of size 40
 105 | snprintf(fw_name, sizeof(fw_name), 
"amdgpu/%s_%d.bin", ucode_prefix, i);
 | 
^~~
   cc1: all warnings being treated as errors


vim +105 drivers/gpu/drm/amd/amdgpu/amdgpu_vcn.c

95d0906f850655 Leo Liu2016-12-21   93  
69939009bde70c Mario Limonciello  2022-12-28   94  int 
amdgpu_vcn_early_init(struct amdgpu_device *adev)
69939009bde70c Mario Limonciello  2022-12-28   95  {
69939009bde70c Mario Limonciello  2022-12-28   96   char ucode_prefix[30];
69939009bde70c Mario Limonciello  2022-12-28   97   char fw_name[40];
6a7cbbc267c0ca Saleemkhan Jamadar 2024-03-06   98   int r, i;
69939009bde70c Mario Limonciello  2022-12-28   99  
6a7cbbc267c0ca Saleemkhan Jamadar 2024-03-06  100   for (i = 0; i < 
adev->vcn.num_vcn_inst; i++) {
69939009bde70c Mario Limonciello  2022-12-28  101   
amdgpu_ucode_ip_version_decode(adev, UVD_HWIP, ucode_prefix, 
sizeof(ucode_prefix));
69939009bde70c Mario Limonciello  2022-12-28 @102   
snprintf(fw_name, sizeof(fw_name), "amdgpu/%s.bin", ucode_prefix);
6a7cbbc267c0ca Saleemkhan Jamadar 2024-03-06  103   if 
(amdgpu_ip_version(adev, UVD_HWIP, 0) ==  IP_VERSION(4, 0, 6) &&
6a7cbbc267c0ca Saleemkhan Jamadar 2024-03-06  104   i == 1) 
{
6a7cbbc267c0ca Saleemkhan Jamadar 2024-03-06 @105   
snprintf(fw_name, sizeof(fw_name), "amdgpu/%s_%d.bin", ucode_prefix, i);
6a7cbbc267c0ca Saleemkhan Jamadar 2024-03-06  106   }
69939009bde70c Mario Limonciello  2022-12-28  107  
6a7cbbc267c0ca Saleemkhan Jamadar 2024-03-06  108   r = 
amdgpu_ucode_request(adev, >vcn.fw[i], fw_name);
6a7cbbc267c0ca Saleemkhan Jamadar 2024-03-06  109   if (r) {
6a7cbbc267c0ca Saleemkhan Jamadar 2024-03-06  110   
amdgpu_ucode_release(>vcn.fw[i]);
6a7cbbc267c0ca Saleemkhan Jamadar 2024-03-06  111   return 
r;
6a7cbbc267c0ca Saleemkhan Jamadar 2024-03-06  112   }
6a7cbbc267c0ca Saleemkhan Jamadar 2024-03-06  113   }
69939009bde70c Mario Limonciello  2022-12-28  114   return r;
69939009bde70c Mario Limonciello  2022-12-28  115  }
69939009bde70c Mario Limonciello  2022-12-28  116  

:: The code at line 105 was first introduced by commit
:: 6a7cbbc267c0cafa2b027983a40276deb673c066 drm/amdgpu/vcn: enable vcn1 fw 
load for VCN 4_0_6

:: TO: Saleemkhan Jamadar 
:: CC: Alex Deucher 

-- 
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki


Re: [PATCH v3 1/2] drm: Introduce plane SIZE_HINTS property

2024-03-19 Thread kernel test robot
Hi Ville,

kernel test robot noticed the following build warnings:

[auto build test WARNING on drm-misc/drm-misc-next]
[also build test WARNING on drm-intel/for-linux-next 
drm-intel/for-linux-next-fixes drm-tip/drm-tip linus/master v6.8 next-20240319]
[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/Ville-Syrjala/drm-Introduce-plane-SIZE_HINTS-property/20240319-044605
base:   git://anongit.freedesktop.org/drm/drm-misc drm-misc-next
patch link:
https://lore.kernel.org/r/20240318204408.9687-2-ville.syrjala%40linux.intel.com
patch subject: [PATCH v3 1/2] drm: Introduce plane SIZE_HINTS property
config: x86_64-defconfig 
(https://download.01.org/0day-ci/archive/20240319/202403191412.utjldbq9-...@intel.com/config)
compiler: gcc-11 (Debian 11.3.0-12) 11.3.0
reproduce (this is a W=1 build): 
(https://download.01.org/0day-ci/archive/20240319/202403191412.utjldbq9-...@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 
| Closes: 
https://lore.kernel.org/oe-kbuild-all/202403191412.utjldbq9-...@intel.com/

All warnings (new ones prefixed by >>):

>> drivers/gpu/drm/drm_plane.c:1767: warning: expecting prototype for 
>> drm_plane_add_size_hint_property(). Prototype was for 
>> drm_plane_add_size_hints_property() instead


vim +1767 drivers/gpu/drm/drm_plane.c

  1751  
  1752  /**
  1753   * drm_plane_add_size_hint_property - create a size hint property
  1754   *
  1755   * @plane: drm plane
  1756   * @hints: size hints
  1757   * @num_hints: number of size hints
  1758   *
  1759   * Create a size hints property for the plane.
  1760   *
  1761   * RETURNS:
  1762   * Zero for success or -errno
  1763   */
  1764  int drm_plane_add_size_hints_property(struct drm_plane *plane,
  1765const struct drm_plane_size_hint 
*hints,
  1766int num_hints)
> 1767  {

-- 
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki


[linux-next:master] BUILD REGRESSION dad309222e4c3fc7f88b20ce725ce1e0eea07cc7

2024-03-13 Thread kernel test robot
tree/branch: 
https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
branch HEAD: dad309222e4c3fc7f88b20ce725ce1e0eea07cc7  Add linux-next specific 
files for 20240313

Error/Warning reports:

https://lore.kernel.org/oe-kbuild-all/202403131859.szdcjzfy-...@intel.com

Error/Warning: (recently discovered and may have been fixed)

ERROR: modpost: "__aeabi_uldivmod" [drivers/gpu/drm/sun4i/sun4i-drm-hdmi.ko] 
undefined!
drivers/gpu/drm/xe/xe_hw_engine_class_sysfs.c:574:33: error: unused function 
'pdev_to_xe_device' [-Werror,-Wunused-function]
drivers/gpu/drm/xe/xe_hw_engine_class_sysfs.c:579:33: error: unused function 
'to_xe_device' [-Werror,-Wunused-function]
include/linux/of.h:946:(.text+0x2be): undefined reference to `__udivdi3'
ld.lld: error: undefined symbol: __aeabi_uldivmod
powerpc-linux-ld: warning: orphan section `.bss..Lubsan_data772' from 
`kernel/ptrace.o' being placed in section `.bss..Lubsan_data772'

Unverified Error/Warning (likely false positive, please contact us if 
interested):

drivers/accessibility/speakup/devsynth.c:110:1: error: label at end of compound 
statement

Error/Warning ids grouped by kconfigs:

gcc_recent_errors
|-- alpha-allyesconfig
|   `-- 
fs-ubifs-journal.c:warning:expecting-prototype-for-wake_up_reservation().-Prototype-was-for-add_or_start_queue()-instead
|-- arc-allmodconfig
|   |-- 
drivers-gpu-drm-i915-display-intel_bios.c:error:implicit-declaration-of-function-intel_opregion_vbt_present
|   `-- 
fs-ubifs-journal.c:warning:expecting-prototype-for-wake_up_reservation().-Prototype-was-for-add_or_start_queue()-instead
|-- arc-allyesconfig
|   `-- 
fs-ubifs-journal.c:warning:expecting-prototype-for-wake_up_reservation().-Prototype-was-for-add_or_start_queue()-instead
|-- arc-randconfig-002-20240313
|   `-- 
fs-ubifs-journal.c:warning:expecting-prototype-for-wake_up_reservation().-Prototype-was-for-add_or_start_queue()-instead
|-- arm-allmodconfig
|   |-- 
arch-arm-mach-omap2-prm33xx.c:warning:expecting-prototype-for-am33xx_prm_global_warm_sw_reset().-Prototype-was-for-am33xx_prm_global_sw_reset()-instead
|   |-- 
drivers-gpu-drm-i915-display-intel_bios.c:error:implicit-declaration-of-function-intel_opregion_vbt_present
|   `-- 
fs-ubifs-journal.c:warning:expecting-prototype-for-wake_up_reservation().-Prototype-was-for-add_or_start_queue()-instead
|-- arm-allyesconfig
|   |-- 
arch-arm-mach-omap2-prm33xx.c:warning:expecting-prototype-for-am33xx_prm_global_warm_sw_reset().-Prototype-was-for-am33xx_prm_global_sw_reset()-instead
|   `-- 
fs-ubifs-journal.c:warning:expecting-prototype-for-wake_up_reservation().-Prototype-was-for-add_or_start_queue()-instead
|-- arm64-defconfig
|   `-- 
fs-ubifs-journal.c:warning:expecting-prototype-for-wake_up_reservation().-Prototype-was-for-add_or_start_queue()-instead
|-- csky-allmodconfig
|   |-- 
drivers-gpu-drm-i915-display-intel_bios.c:error:implicit-declaration-of-function-intel_opregion_vbt_present
|   `-- 
fs-ubifs-journal.c:warning:expecting-prototype-for-wake_up_reservation().-Prototype-was-for-add_or_start_queue()-instead
|-- csky-allyesconfig
|   `-- 
fs-ubifs-journal.c:warning:expecting-prototype-for-wake_up_reservation().-Prototype-was-for-add_or_start_queue()-instead
|-- csky-randconfig-001-20240313
|   `-- 
fs-ubifs-journal.c:warning:expecting-prototype-for-wake_up_reservation().-Prototype-was-for-add_or_start_queue()-instead
|-- csky-randconfig-r122-20240313
|   `-- io_uring-io_uring.c:sparse:sparse:cast-to-restricted-io_req_flags_t
|-- i386-allmodconfig
|   `-- 
fs-ubifs-journal.c:warning:expecting-prototype-for-wake_up_reservation().-Prototype-was-for-add_or_start_queue()-instead
|-- i386-allyesconfig
|   `-- 
fs-ubifs-journal.c:warning:expecting-prototype-for-wake_up_reservation().-Prototype-was-for-add_or_start_queue()-instead
|-- i386-buildonly-randconfig-006-20240313
|   `-- 
drivers-gpu-drm-i915-display-intel_bios.c:error:implicit-declaration-of-function-intel_opregion_vbt_present
|-- i386-randconfig-141-20240313
|   |-- 
drivers-mtd-devices-mchp48l640.c-mchp48l640_read_page()-warn:Please-consider-using-kzalloc-instead-of-kmalloc
|   |-- 
drivers-mtd-devices-mchp48l640.c-mchp48l640_write_page()-warn:Please-consider-using-kzalloc-instead-of-kmalloc
|   |-- 
drivers-usb-dwc2-hcd.c-dwc2_alloc_split_dma_aligned_buf()-warn:Please-consider-using-kmem_cache_zalloc-instead-of-kmem_cache_alloc
|   |-- 
drivers-usb-typec-tcpm-tcpm.c-tcpm_pd_svdm()-error:uninitialized-symbol-modep_prime-.
|   `-- 
fs-ubifs-journal.c:warning:expecting-prototype-for-wake_up_reservation().-Prototype-was-for-add_or_start_queue()-instead
|-- loongarch-allmodconfig
|   `-- 
fs-ubifs-journal.c:warning:expecting-prototype-for-wake_up_reservation().-Prototype-was-for-add_or_start_queue()-instead
|-- loongarch-defconfig
|   `-- 
fs-ubifs-journal.c:warning:expecting-prototype-for-wake_up_reservation().-Prototype-was-for-add_or_start_queue()-instead
|-- m68k-allmodconfig
|   `-- 

[linux-next:master] BUILD REGRESSION a1184cae56bcb96b86df3ee0377cec507a3f56e0

2024-03-12 Thread kernel test robot
tree/branch: 
https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
branch HEAD: a1184cae56bcb96b86df3ee0377cec507a3f56e0  Add linux-next specific 
files for 20240312

Error/Warning reports:

https://lore.kernel.org/oe-kbuild-all/202403121924.e3xrqdss-...@intel.com

Error/Warning: (recently discovered and may have been fixed)

drivers/gpu/drm/i915/display/intel_bios.c:3417:10: error: call to undeclared 
function 'intel_opregion_vbt_present'; ISO C99 and later do not support 
implicit function declarations [-Wimplicit-function-declaration]

Error/Warning ids grouped by kconfigs:

gcc_recent_errors
|-- alpha-allyesconfig
|   `-- 
fs-ubifs-journal.c:warning:expecting-prototype-for-wake_up_reservation().-Prototype-was-for-add_or_start_queue()-instead
|-- arc-allmodconfig
|   `-- 
fs-ubifs-journal.c:warning:expecting-prototype-for-wake_up_reservation().-Prototype-was-for-add_or_start_queue()-instead
|-- arc-allyesconfig
|   `-- 
fs-ubifs-journal.c:warning:expecting-prototype-for-wake_up_reservation().-Prototype-was-for-add_or_start_queue()-instead
|-- arm-allmodconfig
|   |-- 
arch-arm-mach-omap2-prm33xx.c:warning:expecting-prototype-for-am33xx_prm_global_warm_sw_reset().-Prototype-was-for-am33xx_prm_global_sw_reset()-instead
|   `-- 
fs-ubifs-journal.c:warning:expecting-prototype-for-wake_up_reservation().-Prototype-was-for-add_or_start_queue()-instead
|-- arm-allyesconfig
|   |-- 
arch-arm-mach-omap2-prm33xx.c:warning:expecting-prototype-for-am33xx_prm_global_warm_sw_reset().-Prototype-was-for-am33xx_prm_global_sw_reset()-instead
|   `-- 
fs-ubifs-journal.c:warning:expecting-prototype-for-wake_up_reservation().-Prototype-was-for-add_or_start_queue()-instead
|-- arm-randconfig-002-20240312
|   |-- 
arch-arm-mach-omap2-prm33xx.c:warning:expecting-prototype-for-am33xx_prm_global_warm_sw_reset().-Prototype-was-for-am33xx_prm_global_sw_reset()-instead
|   `-- 
fs-ubifs-journal.c:warning:expecting-prototype-for-wake_up_reservation().-Prototype-was-for-add_or_start_queue()-instead
|-- arm-randconfig-003-20240312
|   `-- 
fs-ubifs-journal.c:warning:expecting-prototype-for-wake_up_reservation().-Prototype-was-for-add_or_start_queue()-instead
|-- arm64-defconfig
|   `-- 
fs-ubifs-journal.c:warning:expecting-prototype-for-wake_up_reservation().-Prototype-was-for-add_or_start_queue()-instead
|-- arm64-randconfig-001-20240312
|   `-- 
fs-ubifs-journal.c:warning:expecting-prototype-for-wake_up_reservation().-Prototype-was-for-add_or_start_queue()-instead
|-- csky-allmodconfig
|   `-- 
fs-ubifs-journal.c:warning:expecting-prototype-for-wake_up_reservation().-Prototype-was-for-add_or_start_queue()-instead
|-- csky-allyesconfig
|   `-- 
fs-ubifs-journal.c:warning:expecting-prototype-for-wake_up_reservation().-Prototype-was-for-add_or_start_queue()-instead
|-- csky-randconfig-002-20240312
|   `-- 
fs-ubifs-journal.c:warning:expecting-prototype-for-wake_up_reservation().-Prototype-was-for-add_or_start_queue()-instead
|-- i386-allmodconfig
|   `-- 
fs-ubifs-journal.c:warning:expecting-prototype-for-wake_up_reservation().-Prototype-was-for-add_or_start_queue()-instead
|-- i386-allyesconfig
|   `-- 
fs-ubifs-journal.c:warning:expecting-prototype-for-wake_up_reservation().-Prototype-was-for-add_or_start_queue()-instead
|-- i386-randconfig-001-20240312
|   `-- 
fs-ubifs-journal.c:warning:expecting-prototype-for-wake_up_reservation().-Prototype-was-for-add_or_start_queue()-instead
|-- i386-randconfig-011-20240312
|   `-- 
fs-ubifs-journal.c:warning:expecting-prototype-for-wake_up_reservation().-Prototype-was-for-add_or_start_queue()-instead
|-- i386-randconfig-061-20240312
|   |-- io_uring-io_uring.c:sparse:sparse:cast-to-restricted-io_req_flags_t
|   |-- 
kernel-power-energy_model.c:sparse:sparse:incorrect-type-in-argument-(different-address-spaces)-expected-struct-em_perf_state-table-got-struct-em_perf_state-noderef-__rcu
|   |-- 
kernel-power-energy_model.c:sparse:sparse:incorrect-type-in-argument-(different-address-spaces)-expected-struct-kref-kref-got-struct-kref-noderef-__rcu
|   |-- 
kernel-power-energy_model.c:sparse:sparse:incorrect-type-in-argument-(different-address-spaces)-expected-void-const-objp-got-struct-em_perf_table-noderef-__rcu-assigned-em_table
|   `-- 
kernel-power-energy_model.c:sparse:sparse:incorrect-type-in-assignment-(different-address-spaces)-expected-struct-em_perf_state-new_ps-got-struct-em_perf_state-noderef-__rcu
|-- i386-randconfig-063-20240312
|   `-- io_uring-io_uring.c:sparse:sparse:cast-to-restricted-io_req_flags_t
|-- loongarch-allmodconfig
|   `-- 
fs-ubifs-journal.c:warning:expecting-prototype-for-wake_up_reservation().-Prototype-was-for-add_or_start_queue()-instead
|-- loongarch-defconfig
|   `-- 
fs-ubifs-journal.c:warning:expecting-prototype-for-wake_up_reservation().-Prototype-was-for-add_or_start_queue()-instead
|-- m68k-allmodconfig
|   `-- 
fs-ubifs-journal.c:warning:expecting-prototype-for-wake_up_reservation().-Prototype-was-for-add_or_start_queue()-instead
|-- 

[drm-intel:for-linux-next 4/6] drivers/gpu/drm/i915/display/intel_bios.c:3417:24: error: implicit declaration of function 'intel_opregion_vbt_present'; did you mean 'intel_opregion_asle_present'?

2024-03-11 Thread kernel test robot
tree:   git://anongit.freedesktop.org/drm-intel for-linux-next
head:   0e7dd6fe96020e6b7f5e068bf1c66078e0b145d3
commit: 9d9bb71f3e115b75ec5e38f087e159a87fc0413a [4/6] drm/i915: Extract 
opregion vbt presence check
config: sparc64-allmodconfig 
(https://download.01.org/0day-ci/archive/20240312/202403120756.jtkghcip-...@intel.com/config)
compiler: sparc64-linux-gcc (GCC) 13.2.0
reproduce (this is a W=1 build): 
(https://download.01.org/0day-ci/archive/20240312/202403120756.jtkghcip-...@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 
| Closes: 
https://lore.kernel.org/oe-kbuild-all/202403120756.jtkghcip-...@intel.com/

All errors (new ones prefixed by >>):

   drivers/gpu/drm/i915/display/intel_bios.c: In function 
'intel_bios_is_lvds_present':
>> drivers/gpu/drm/i915/display/intel_bios.c:3417:24: error: implicit 
>> declaration of function 'intel_opregion_vbt_present'; did you mean 
>> 'intel_opregion_asle_present'? [-Werror=implicit-function-declaration]
3417 | return intel_opregion_vbt_present(i915);
 |^~
 |intel_opregion_asle_present
   cc1: some warnings being treated as errors


vim +3417 drivers/gpu/drm/i915/display/intel_bios.c

  3374  
  3375  /**
  3376   * intel_bios_is_lvds_present - is LVDS present in VBT
  3377   * @i915:   i915 device instance
  3378   * @i2c_pin:i2c pin for LVDS if present
  3379   *
  3380   * Return true if LVDS is present. If no child devices were parsed from 
VBT,
  3381   * assume LVDS is present.
  3382   */
  3383  bool intel_bios_is_lvds_present(struct drm_i915_private *i915, u8 
*i2c_pin)
  3384  {
  3385  const struct intel_bios_encoder_data *devdata;
  3386  
  3387  if (list_empty(>display.vbt.display_devices))
  3388  return true;
  3389  
  3390  list_for_each_entry(devdata, 
>display.vbt.display_devices, node) {
  3391  const struct child_device_config *child = 
>child;
  3392  
  3393  /* If the device type is not LFP, continue.
  3394   * We have to check both the new identifiers as well as 
the
  3395   * old for compatibility with some BIOSes.
  3396   */
  3397  if (child->device_type != DEVICE_TYPE_INT_LFP &&
  3398  child->device_type != DEVICE_TYPE_LFP)
  3399  continue;
  3400  
  3401  if (intel_gmbus_is_valid_pin(i915, child->i2c_pin))
  3402  *i2c_pin = child->i2c_pin;
  3403  
  3404  /* However, we cannot trust the BIOS writers to populate
  3405   * the VBT correctly.  Since LVDS requires additional
  3406   * information from AIM blocks, a non-zero addin offset 
is
  3407   * a good indicator that the LVDS is actually present.
  3408   */
  3409  if (child->addin_offset)
  3410  return true;
  3411  
  3412  /* But even then some BIOS writers perform some black 
magic
  3413   * and instantiate the device without reference to any
  3414   * additional data.  Trust that if the VBT was written 
into
  3415   * the OpRegion then they have validated the LVDS's 
existence.
  3416   */
> 3417  return intel_opregion_vbt_present(i915);
  3418  }
  3419  
  3420  return false;
  3421  }
  3422  

-- 
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki


Re: [PATCH 22/22] drm: ensure drm headers are self-contained and pass kernel-doc

2024-03-07 Thread kernel test robot
Hi Jani,

kernel test robot noticed the following build warnings:

[auto build test WARNING on drm-misc/drm-misc-next]
[cannot apply to drm/drm-next drm-intel/for-linux-next 
drm-intel/for-linux-next-fixes linus/master v6.8-rc7 next-20240307]
[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/Jani-Nikula/drm-crtc-make-drm_crtc_internal-h-self-contained/20240307-023603
base:   git://anongit.freedesktop.org/drm/drm-misc drm-misc-next
patch link:
https://lore.kernel.org/r/e22ab28836ee1689ea4781ed53fd2e4e4f84728e.1709749576.git.jani.nikula%40intel.com
patch subject: [PATCH 22/22] drm: ensure drm headers are self-contained and 
pass kernel-doc
config: hexagon-allmodconfig 
(https://download.01.org/0day-ci/archive/20240307/202403072259.eec2vf1x-...@intel.com/config)
compiler: clang version 19.0.0git (https://github.com/llvm/llvm-project 
325f51237252e6dab8e4e1ea1fa7acbb4faee1cd)
reproduce (this is a W=1 build): 
(https://download.01.org/0day-ci/archive/20240307/202403072259.eec2vf1x-...@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 
| Closes: 
https://lore.kernel.org/oe-kbuild-all/202403072259.eec2vf1x-...@intel.com/

All warnings (new ones prefixed by >>):

   In file included from :4:
>> include/drm/ttm/ttm_pool.h:89:52: warning: declaration of 'struct seq_file' 
>> will not be visible outside of this function [-Wvisibility]
  89 | int ttm_pool_debugfs(struct ttm_pool *pool, struct seq_file *m);
 |^
   1 warning generated.


vim +89 include/drm/ttm/ttm_pool.h

d099fc8f540add Christian König 2020-10-22  88  
d099fc8f540add Christian König 2020-10-22 @89  int ttm_pool_debugfs(struct 
ttm_pool *pool, struct seq_file *m);
d099fc8f540add Christian König 2020-10-22  90  

-- 
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki


Re: [PATCH 22/22] drm: ensure drm headers are self-contained and pass kernel-doc

2024-03-06 Thread kernel test robot
Hi Jani,

kernel test robot noticed the following build errors:

[auto build test ERROR on drm-misc/drm-misc-next]
[cannot apply to drm/drm-next drm-intel/for-linux-next 
drm-intel/for-linux-next-fixes linus/master v6.8-rc7 next-20240306]
[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/Jani-Nikula/drm-crtc-make-drm_crtc_internal-h-self-contained/20240307-023603
base:   git://anongit.freedesktop.org/drm/drm-misc drm-misc-next
patch link:
https://lore.kernel.org/r/e22ab28836ee1689ea4781ed53fd2e4e4f84728e.1709749576.git.jani.nikula%40intel.com
patch subject: [PATCH 22/22] drm: ensure drm headers are self-contained and 
pass kernel-doc
config: m68k-allmodconfig 
(https://download.01.org/0day-ci/archive/20240307/202403071317.uow18zr3-...@intel.com/config)
compiler: m68k-linux-gcc (GCC) 13.2.0
reproduce (this is a W=1 build): 
(https://download.01.org/0day-ci/archive/20240307/202403071317.uow18zr3-...@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 
| Closes: 
https://lore.kernel.org/oe-kbuild-all/202403071317.uow18zr3-...@intel.com/

All error/warnings (new ones prefixed by >>):

   In file included from include/asm-generic/pgtable-nopud.h:7,
from arch/m68k/include/asm/pgtable_mm.h:9,
from arch/m68k/include/asm/pgtable.h:8,
from include/linux/pgtable.h:6,
from include/drm/ttm/ttm_caching.h:28,
from :
>> include/asm-generic/pgtable-nop4d.h:9:18: error: unknown type name 'pgd_t'
   9 | typedef struct { pgd_t pgd; } p4d_t;
 |  ^
   include/asm-generic/pgtable-nop4d.h:21:28: error: unknown type name 'pgd_t'; 
did you mean 'p4d_t'?
  21 | static inline int pgd_none(pgd_t pgd)   { return 0; }
 |^
 |p4d_t
   include/asm-generic/pgtable-nop4d.h:22:27: error: unknown type name 'pgd_t'; 
did you mean 'p4d_t'?
  22 | static inline int pgd_bad(pgd_t pgd){ return 0; }
 |   ^
 |   p4d_t
   include/asm-generic/pgtable-nop4d.h:23:31: error: unknown type name 'pgd_t'; 
did you mean 'p4d_t'?
  23 | static inline int pgd_present(pgd_t pgd){ return 1; }
 |   ^
 |   p4d_t
   include/asm-generic/pgtable-nop4d.h:24:30: error: unknown type name 'pgd_t'; 
did you mean 'p4d_t'?
  24 | static inline void pgd_clear(pgd_t *pgd){ }
 |  ^
 |  p4d_t
   include/asm-generic/pgtable-nop4d.h:35:33: error: unknown type name 'pgd_t'; 
did you mean 'p4d_t'?
  35 | static inline p4d_t *p4d_offset(pgd_t *pgd, unsigned long address)
 | ^
 | p4d_t
   In file included from arch/m68k/include/asm/thread_info.h:6,
from include/linux/thread_info.h:60,
from include/asm-generic/preempt.h:5,
from ./arch/m68k/include/generated/asm/preempt.h:1,
from include/linux/preempt.h:79,
from arch/m68k/include/asm/processor.h:11,
from arch/m68k/include/asm/pgtable_mm.h:15:
   arch/m68k/include/asm/motorola_pgtable.h: In function 'pud_set':
>> arch/m68k/include/asm/page.h:46:29: error: request for member 'pgd' in 
>> something not a structure or union
  46 | #define pgd_val(x)  ((x).pgd)
 | ^
   include/asm-generic/pgtable-nop4d.h:40:50: note: in expansion of macro 
'pgd_val'
  40 | #define p4d_val(x)  (pgd_val((x).pgd))
 |  ^~~
   include/asm-generic/pgtable-nopud.h:48:50: note: in expansion of macro 
'p4d_val'
  48 | #define pud_val(x)  (p4d_val((x).p4d))
 |  ^~~
   arch/m68k/include/asm/motorola_pgtable.h:103:9: note: in expansion of macro 
'pud_val'
 103 | pud_val(*pudp) = _PAGE_TABLE | _PAGE_ACCESSED | __pa(pmdp);
 | ^~~
   include/linux/pgtable.h: In function 'pmd_offset':
>> arch/m68k/include/asm/page.h:46:29: error: request for member 'pgd' in 
>> something not a structure or union
  46 | #define pgd_val(x)  ((x).pgd)
 | ^
   include/asm-generic/pgtable-nop4d.h:40:50: note: in expansion of macro 
'p

Re: [PATCH 22/22] drm: ensure drm headers are self-contained and pass kernel-doc

2024-03-06 Thread kernel test robot
Hi Jani,

kernel test robot noticed the following build errors:

[auto build test ERROR on drm-misc/drm-misc-next]
[cannot apply to drm/drm-next drm-intel/for-linux-next 
drm-intel/for-linux-next-fixes linus/master v6.8-rc7 next-20240306]
[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/Jani-Nikula/drm-crtc-make-drm_crtc_internal-h-self-contained/20240307-023603
base:   git://anongit.freedesktop.org/drm/drm-misc drm-misc-next
patch link:
https://lore.kernel.org/r/e22ab28836ee1689ea4781ed53fd2e4e4f84728e.1709749576.git.jani.nikula%40intel.com
patch subject: [PATCH 22/22] drm: ensure drm headers are self-contained and 
pass kernel-doc
config: sh-allmodconfig 
(https://download.01.org/0day-ci/archive/20240307/202403071204.gjtmneoq-...@intel.com/config)
compiler: sh4-linux-gcc (GCC) 13.2.0
reproduce (this is a W=1 build): 
(https://download.01.org/0day-ci/archive/20240307/202403071204.gjtmneoq-...@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 
| Closes: 
https://lore.kernel.org/oe-kbuild-all/202403071204.gjtmneoq-...@intel.com/

All errors (new ones prefixed by >>):

   In file included from :
   drivers/gpu/drm/./drm_crtc_internal.h: In function 'drm_edid_load_firmware':
>> drivers/gpu/drm/./drm_crtc_internal.h:304:16: error: implicit declaration of 
>> function 'ERR_PTR' [-Werror=implicit-function-declaration]
 304 | return ERR_PTR(-ENOENT);
 |^~~
>> drivers/gpu/drm/./drm_crtc_internal.h:304:25: error: 'ENOENT' undeclared 
>> (first use in this function)
 304 | return ERR_PTR(-ENOENT);
 | ^~
   drivers/gpu/drm/./drm_crtc_internal.h:304:25: note: each undeclared 
identifier is reported only once for each function it appears in
   In file included from :
   drivers/gpu/drm/./drm_crtc_internal.h: At top level:
>> drivers/gpu/drm/./drm_crtc_internal.h:302:1: error: redefinition of 
>> 'drm_edid_load_firmware'
 302 | drm_edid_load_firmware(struct drm_connector *connector)
 | ^~
   drivers/gpu/drm/./drm_crtc_internal.h:302:1: note: previous definition of 
'drm_edid_load_firmware' with type 'const struct drm_edid *(struct 
drm_connector *)'
 302 | drm_edid_load_firmware(struct drm_connector *connector)
 | ^~
   drivers/gpu/drm/./drm_crtc_internal.h: In function 'drm_edid_load_firmware':
>> drivers/gpu/drm/./drm_crtc_internal.h:304:25: error: 'ENOENT' undeclared 
>> (first use in this function)
 304 | return ERR_PTR(-ENOENT);
 | ^~
   cc1: all warnings being treated as errors


vim +/ERR_PTR +304 drivers/gpu/drm/./drm_crtc_internal.h

5f2d0ed49036a0 Jani Nikula 2022-10-24  296  
5f2d0ed49036a0 Jani Nikula 2022-10-24  297  /* drm_edid_load.c */
5f2d0ed49036a0 Jani Nikula 2022-10-24  298  #ifdef CONFIG_DRM_LOAD_EDID_FIRMWARE
5f2d0ed49036a0 Jani Nikula 2022-10-24  299  const struct drm_edid 
*drm_edid_load_firmware(struct drm_connector *connector);
5f2d0ed49036a0 Jani Nikula 2022-10-24  300  #else
5f2d0ed49036a0 Jani Nikula 2022-10-24  301  static inline const struct drm_edid 
*
5f2d0ed49036a0 Jani Nikula 2022-10-24 @302  drm_edid_load_firmware(struct 
drm_connector *connector)
5f2d0ed49036a0 Jani Nikula 2022-10-24  303  {
5f2d0ed49036a0 Jani Nikula 2022-10-24 @304  return ERR_PTR(-ENOENT);

-- 
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki


Re: [PATCH v3 3/5] drm/i915/psr: Calculate IO wake and fast wake lines for DISPLAY_VER < 12

2024-03-05 Thread kernel test robot
Hi Jouni,

kernel test robot noticed the following build warnings:

[auto build test WARNING on drm-intel/for-linux-next]
[also build test WARNING on drm-tip/drm-tip next-20240305]
[cannot apply to drm-intel/for-linux-next-fixes linus/master v6.8-rc7]
[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/Jouni-H-gander/drm-i915-display-Make-intel_dp_aux_fw_sync_len-available-for-PSR-code/20240305-200753
base:   git://anongit.freedesktop.org/drm-intel for-linux-next
patch link:
https://lore.kernel.org/r/20240305120458.1275218-4-jouni.hogander%40intel.com
patch subject: [PATCH v3 3/5] drm/i915/psr: Calculate IO wake and fast wake 
lines for DISPLAY_VER < 12
config: s390-allmodconfig 
(https://download.01.org/0day-ci/archive/20240306/202403061144.nxw1e72o-...@intel.com/config)
compiler: clang version 19.0.0git (https://github.com/llvm/llvm-project 
325f51237252e6dab8e4e1ea1fa7acbb4faee1cd)
reproduce (this is a W=1 build): 
(https://download.01.org/0day-ci/archive/20240306/202403061144.nxw1e72o-...@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 
| Closes: 
https://lore.kernel.org/oe-kbuild-all/202403061144.nxw1e72o-...@intel.com/

All warnings (new ones prefixed by >>):

   In file included from include/linux/elf.h:6:
   In file included from arch/s390/include/asm/elf.h:173:
   In file included from arch/s390/include/asm/mmu_context.h:11:
   In file included from arch/s390/include/asm/pgalloc.h:18:
   In file included from include/linux/mm.h:2188:
   include/linux/vmstat.h:508:43: warning: arithmetic between different 
enumeration types ('enum zone_stat_item' and 'enum numa_stat_item') 
[-Wenum-enum-conversion]
 508 | return vmstat_text[NR_VM_ZONE_STAT_ITEMS +
 |~ ^
 509 |item];
 |
   include/linux/vmstat.h:515:43: warning: arithmetic between different 
enumeration types ('enum zone_stat_item' and 'enum numa_stat_item') 
[-Wenum-enum-conversion]
 515 | return vmstat_text[NR_VM_ZONE_STAT_ITEMS +
 |~ ^
 516 |NR_VM_NUMA_EVENT_ITEMS +
 |~~
   include/linux/vmstat.h:522:36: warning: arithmetic between different 
enumeration types ('enum node_stat_item' and 'enum lru_list') 
[-Wenum-enum-conversion]
 522 | return node_stat_name(NR_LRU_BASE + lru) + 3; // skip "nr_"
 |   ~~~ ^ ~~~
   include/linux/vmstat.h:527:43: warning: arithmetic between different 
enumeration types ('enum zone_stat_item' and 'enum numa_stat_item') 
[-Wenum-enum-conversion]
 527 | return vmstat_text[NR_VM_ZONE_STAT_ITEMS +
 |~ ^
 528 |NR_VM_NUMA_EVENT_ITEMS +
 |~~
   include/linux/vmstat.h:536:43: warning: arithmetic between different 
enumeration types ('enum zone_stat_item' and 'enum numa_stat_item') 
[-Wenum-enum-conversion]
 536 | return vmstat_text[NR_VM_ZONE_STAT_ITEMS +
 |~ ^
 537 |NR_VM_NUMA_EVENT_ITEMS +
 |~~
   In file included from drivers/gpu/drm/i915/display/intel_psr.c:28:
   In file included from drivers/gpu/drm/xe/compat-i915-headers/i915_drv.h:15:
   In file included from 
drivers/gpu/drm/xe/compat-i915-headers/gem/i915_gem_object.h:11:
   In file included from drivers/gpu/drm/xe/xe_bo.h:11:
   In file included from drivers/gpu/drm/xe/xe_bo_types.h:9:
   In file included from include/linux/iosys-map.h:10:
   In file included from include/linux/io.h:13:
   In file included from arch/s390/include/asm/io.h:78:
   include/asm-generic/io.h:547:31: warning: performing pointer arithmetic on a 
null pointer has undefined behavior [-Wnull-pointer-arithmetic]
 547 | val = __raw_readb(PCI_IOBASE + addr);
 |   ~~ ^
   include/asm-generic/io.h:560:61: warning: performing pointer arithmetic on a 
null pointer has undefined behavior [-Wnull-pointer-arithmetic]
 560 | val = __le16_to_cpu((__le16 __force)__raw_readw(PCI_IOBASE + 
addr));
 | ~~ ^
   include/uapi/linux/byteorder/big_endian.h:37:59: note: expanded from macro 
'__le16_to_cpu'
  37 | #define __le16_to_cpu(x) __swab16((__for

Re: [PATCH v3 3/4] drm/ttm, drm/amdgpu, drm/xe: Consider hitch moves within bulk sublist moves

2024-03-05 Thread kernel test robot
Hi Thomas,

kernel test robot noticed the following build warnings:

[auto build test WARNING on drm-misc/drm-misc-next]
[also build test WARNING on drm-intel/for-linux-next drm-tip/drm-tip]
[cannot apply to drm-intel/for-linux-next-fixes linus/master v6.8-rc7 
next-20240305]
[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/Thomas-Hellstr-m/drm-ttm-Allow-TTM-LRU-list-nodes-of-different-types/20240306-000453
base:   git://anongit.freedesktop.org/drm/drm-misc drm-misc-next
patch link:
https://lore.kernel.org/r/20240305160202.3555-4-thomas.hellstrom%40linux.intel.com
patch subject: [PATCH v3 3/4] drm/ttm, drm/amdgpu, drm/xe: Consider hitch moves 
within bulk sublist moves
config: arm-defconfig 
(https://download.01.org/0day-ci/archive/20240306/202403060640.zcxpvobi-...@intel.com/config)
compiler: clang version 14.0.6 (https://github.com/llvm/llvm-project.git 
f28c006a5895fc0e329fe15fead81e37457cb1d1)
reproduce (this is a W=1 build): 
(https://download.01.org/0day-ci/archive/20240306/202403060640.zcxpvobi-...@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 
| Closes: 
https://lore.kernel.org/oe-kbuild-all/202403060640.zcxpvobi-...@intel.com/

All warnings (new ones prefixed by >>):

   In file included from drivers/gpu/drm/drm_gem_ttm_helper.c:5:
   In file included from include/drm/drm_gem_ttm_helper.h:10:
   In file included from include/drm/ttm/ttm_bo.h:39:
>> include/drm/ttm/ttm_device.h:286:31: warning: variable 'old' set but not 
>> used [-Wunused-but-set-variable]
   struct ttm_resource_manager *old;
^
   1 warning generated.


vim +/old +286 include/drm/ttm/ttm_device.h

   282  
   283  static inline void ttm_set_driver_manager(struct ttm_device *bdev, int 
type,
   284struct ttm_resource_manager 
*manager)
   285  {
 > 286  struct ttm_resource_manager *old;
   287  
   288  BUILD_BUG_ON(__builtin_constant_p(type) && type >= 
TTM_NUM_MEM_TYPES);
   289  old = bdev->man_drv[type];
   290  bdev->man_drv[type] = manager;
   291  if (manager)
   292  manager->mem_type = type;
   293  }
   294  

-- 
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki


Re: [PATCH 2/3] drm/i915/psr: Improve fast and IO wake lines calculation

2024-02-21 Thread kernel test robot
Hi Jouni,

kernel test robot noticed the following build warnings:

[auto build test WARNING on drm-intel/for-linux-next]
[also build test WARNING on drm-tip/drm-tip next-20240221]
[cannot apply to drm-intel/for-linux-next-fixes linus/master v6.8-rc5]
[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/Jouni-H-gander/drm-i915-display-Add-aux-function-pointer-for-fast-wake-sync-pulse-count/20240221-160220
base:   git://anongit.freedesktop.org/drm-intel for-linux-next
patch link:
https://lore.kernel.org/r/20240221075322.2764209-3-jouni.hogander%40intel.com
patch subject: [PATCH 2/3] drm/i915/psr: Improve fast and IO wake lines 
calculation
config: s390-allmodconfig 
(https://download.01.org/0day-ci/archive/20240222/202402220859.k3osmrci-...@intel.com/config)
compiler: clang version 19.0.0git (https://github.com/llvm/llvm-project 
36adfec155de366d722f2bac8ff9162289dcf06c)
reproduce (this is a W=1 build): 
(https://download.01.org/0day-ci/archive/20240222/202402220859.k3osmrci-...@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 
| Closes: 
https://lore.kernel.org/oe-kbuild-all/202402220859.k3osmrci-...@intel.com/

All warnings (new ones prefixed by >>):

   In file included from drivers/gpu/drm/i915/display/intel_psr.c:28:
   In file included from drivers/gpu/drm/xe/compat-i915-headers/i915_drv.h:15:
   In file included from 
drivers/gpu/drm/xe/compat-i915-headers/gem/i915_gem_object.h:11:
   In file included from drivers/gpu/drm/xe/xe_bo.h:11:
   In file included from drivers/gpu/drm/xe/xe_bo_types.h:9:
   In file included from include/linux/iosys-map.h:10:
   In file included from include/linux/io.h:13:
   In file included from arch/s390/include/asm/io.h:78:
   include/asm-generic/io.h:547:31: warning: performing pointer arithmetic on a 
null pointer has undefined behavior [-Wnull-pointer-arithmetic]
 547 | val = __raw_readb(PCI_IOBASE + addr);
 |   ~~ ^
   include/asm-generic/io.h:560:61: warning: performing pointer arithmetic on a 
null pointer has undefined behavior [-Wnull-pointer-arithmetic]
 560 | val = __le16_to_cpu((__le16 __force)__raw_readw(PCI_IOBASE + 
addr));
 | ~~ ^
   include/uapi/linux/byteorder/big_endian.h:37:59: note: expanded from macro 
'__le16_to_cpu'
  37 | #define __le16_to_cpu(x) __swab16((__force __u16)(__le16)(x))
 |   ^
   include/uapi/linux/swab.h:102:54: note: expanded from macro '__swab16'
 102 | #define __swab16(x) (__u16)__builtin_bswap16((__u16)(x))
 |  ^
   In file included from drivers/gpu/drm/i915/display/intel_psr.c:28:
   In file included from drivers/gpu/drm/xe/compat-i915-headers/i915_drv.h:15:
   In file included from 
drivers/gpu/drm/xe/compat-i915-headers/gem/i915_gem_object.h:11:
   In file included from drivers/gpu/drm/xe/xe_bo.h:11:
   In file included from drivers/gpu/drm/xe/xe_bo_types.h:9:
   In file included from include/linux/iosys-map.h:10:
   In file included from include/linux/io.h:13:
   In file included from arch/s390/include/asm/io.h:78:
   include/asm-generic/io.h:573:61: warning: performing pointer arithmetic on a 
null pointer has undefined behavior [-Wnull-pointer-arithmetic]
 573 | val = __le32_to_cpu((__le32 __force)__raw_readl(PCI_IOBASE + 
addr));
 | ~~ ^
   include/uapi/linux/byteorder/big_endian.h:35:59: note: expanded from macro 
'__le32_to_cpu'
  35 | #define __le32_to_cpu(x) __swab32((__force __u32)(__le32)(x))
 |   ^
   include/uapi/linux/swab.h:115:54: note: expanded from macro '__swab32'
 115 | #define __swab32(x) (__u32)__builtin_bswap32((__u32)(x))
 |  ^
   In file included from drivers/gpu/drm/i915/display/intel_psr.c:28:
   In file included from drivers/gpu/drm/xe/compat-i915-headers/i915_drv.h:15:
   In file included from 
drivers/gpu/drm/xe/compat-i915-headers/gem/i915_gem_object.h:11:
   In file included from drivers/gpu/drm/xe/xe_bo.h:11:
   In file included from drivers/gpu/drm/xe/xe_bo_types.h:9:
   In file included from include/linux/iosys-map.h:10:
   In file included from include/linux/io.h:13:
   In file included from arch/s390/include/asm/io.h:78:
   include/asm-generic/io.h:584:33: warning: performing pointer arithmetic on a 
null pointer has undefined behavior [-Wnull-pointer-arit

Re: [PATCH v2 5/6] drm/i915/psr: Enable ALPM for eDP Panel replay

2024-02-21 Thread kernel test robot
Hi Jouni,

kernel test robot noticed the following build warnings:

[auto build test WARNING on drm-intel/for-linux-next]
[also build test WARNING on drm-tip/drm-tip drm/drm-next next-20240221]
[cannot apply to drm-intel/for-linux-next-fixes linus/master v6.8-rc5]
[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/Jouni-H-gander/drm-display-Add-missing-aux-less-alpm-wake-related-bits/20240220-201356
base:   git://anongit.freedesktop.org/drm-intel for-linux-next
patch link:
https://lore.kernel.org/r/20240220121045.2156004-6-jouni.hogander%40intel.com
patch subject: [PATCH v2 5/6] drm/i915/psr: Enable ALPM for eDP Panel replay
config: riscv-allmodconfig 
(https://download.01.org/0day-ci/archive/20240222/202402220225.2evin531-...@intel.com/config)
compiler: clang version 19.0.0git (https://github.com/llvm/llvm-project 
36adfec155de366d722f2bac8ff9162289dcf06c)
reproduce (this is a W=1 build): 
(https://download.01.org/0day-ci/archive/20240222/202402220225.2evin531-...@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 
| Closes: 
https://lore.kernel.org/oe-kbuild-all/202402220225.2evin531-...@intel.com/

All warnings (new ones prefixed by >>):

>> drivers/gpu/drm/i915/display/intel_psr.c:1705:3: warning: variable 
>> 'alpm_ctl' is uninitialized when used here [-Wuninitialized]
1705 | alpm_ctl |= ALPM_CTL_ALPM_ENABLE |
 | ^~~~
   drivers/gpu/drm/i915/display/intel_psr.c:1699:14: note: initialize the 
variable 'alpm_ctl' to silence this warning
1699 | u32 alpm_ctl;
 | ^
 |  = 0
   1 warning generated.


vim +/alpm_ctl +1705 drivers/gpu/drm/i915/display/intel_psr.c

  1693  
  1694  static void lnl_alpm_configure(struct intel_dp *intel_dp)
  1695  {
  1696  struct drm_i915_private *dev_priv = dp_to_i915(intel_dp);
  1697  enum transcoder cpu_transcoder = intel_dp->psr.transcoder;
  1698  struct intel_psr *psr = _dp->psr;
  1699  u32 alpm_ctl;
  1700  
  1701  if (DISPLAY_VER(dev_priv) < 20)
  1702  return;
  1703  
  1704  if (intel_dp->psr.panel_replay_enabled && 
intel_dp_is_edp(intel_dp)) {
> 1705  alpm_ctl |= ALPM_CTL_ALPM_ENABLE |
  1706  ALPM_CTL_ALPM_AUX_LESS_ENABLE |
  1707  ALPM_CTL_AUX_LESS_SLEEP_HOLD_TIME_50_SYMBOLS;
  1708  
  1709  intel_de_write(dev_priv, PORT_ALPM_CTL(cpu_transcoder),
  1710 PORT_ALPM_CTL_ALPM_AUX_LESS_ENABLE |
  1711 PORT_ALPM_CTL_MAX_PHY_SWING_SETUP(15) |
  1712 PORT_ALPM_CTL_MAX_PHY_SWING_HOLD(0) |
  1713 PORT_ALPM_CTL_SILENCE_PERIOD(
  1714 
psr->alpm_parameters.silence_period_sym_clocks));
  1715  
  1716  intel_de_write(dev_priv, 
PORT_ALPM_LFPS_CTL(cpu_transcoder),
  1717 PORT_ALPM_LFPS_CTL_LFPS_CYCLE_COUNT(10) |
  1718 
PORT_ALPM_LFPS_CTL_LFPS_HALF_CYCLE_DURATION(
  1719 
psr->alpm_parameters.lfps_half_cycle_num_of_syms) |
  1720 
PORT_ALPM_LFPS_CTL_FIRST_LFPS_HALF_CYCLE_DURATION(
  1721 
psr->alpm_parameters.lfps_half_cycle_num_of_syms) |
  1722 
PORT_ALPM_LFPS_CTL_LAST_LFPS_HALF_CYCLE_DURATION(
  1723 
psr->alpm_parameters.lfps_half_cycle_num_of_syms));
  1724  } else {
  1725  alpm_ctl = ALPM_CTL_EXTENDED_FAST_WAKE_ENABLE |
  1726  
ALPM_CTL_EXTENDED_FAST_WAKE_TIME(psr->alpm_parameters.fast_wake_lines);
  1727  }
  1728  
  1729  alpm_ctl |= 
ALPM_CTL_ALPM_ENTRY_CHECK(psr->alpm_parameters.check_entry_lines);
  1730  
  1731  intel_de_write(dev_priv, ALPM_CTL(cpu_transcoder), alpm_ctl);
  1732  }
  1733  

-- 
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki


Re: [PATCH 01/28] [NOT FOR REVIEW] drm: color pipeline base work

2024-02-17 Thread kernel test robot
Hi Uma,

kernel test robot noticed the following build warnings:

[auto build test WARNING on drm-misc/drm-misc-next]
[also build test WARNING on drm/drm-next next-20240216]
[cannot apply to drm-intel/for-linux-next drm-intel/for-linux-next-fixes 
linus/master v6.8-rc4]
[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/Uma-Shankar/drm-color-pipeline-base-work/20240213-144544
base:   git://anongit.freedesktop.org/drm/drm-misc drm-misc-next
patch link:
https://lore.kernel.org/r/20240213064835.139464-2-uma.shankar%40intel.com
patch subject: [PATCH 01/28] [NOT FOR REVIEW] drm: color pipeline base work
config: x86_64-randconfig-161-20240213 
(https://download.01.org/0day-ci/archive/20240218/202402180051.37wkwgmx-...@intel.com/config)
compiler: gcc-12 (Debian 12.2.0-14) 12.2.0

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 
| Closes: 
https://lore.kernel.org/oe-kbuild-all/202402180051.37wkwgmx-...@intel.com/

smatch warnings:
drivers/gpu/drm/drm_atomic.c:825 drm_atomic_plane_print_state() warn: 
inconsistent indenting

vim +825 drivers/gpu/drm/drm_atomic.c

   799  
   800  static void drm_atomic_plane_print_state(struct drm_printer *p,
   801  const struct drm_plane_state *state)
   802  {
   803  struct drm_plane *plane = state->plane;
   804  struct drm_rect src  = drm_plane_state_src(state);
   805  struct drm_rect dest = drm_plane_state_dest(state);
   806  
   807  drm_printf(p, "plane[%u]: %s\n", plane->base.id, plane->name);
   808  drm_printf(p, "\tcrtc=%s\n", state->crtc ? state->crtc->name : 
"(null)");
   809  drm_printf(p, "\tfb=%u\n", state->fb ? state->fb->base.id : 0);
   810  if (state->fb)
   811  drm_framebuffer_print_info(p, 2, state->fb);
   812  drm_printf(p, "\tcrtc-pos=" DRM_RECT_FMT "\n", 
DRM_RECT_ARG());
   813  drm_printf(p, "\tsrc-pos=" DRM_RECT_FP_FMT "\n", 
DRM_RECT_FP_ARG());
   814  drm_printf(p, "\trotation=%x\n", state->rotation);
   815  drm_printf(p, "\tnormalized-zpos=%x\n", state->normalized_zpos);
   816  drm_printf(p, "\tcolor-encoding=%s\n",
   817 drm_get_color_encoding_name(state->color_encoding));
   818  drm_printf(p, "\tcolor-range=%s\n",
   819 drm_get_color_range_name(state->color_range));
   820  drm_printf(p, "\tcolor_mgmt_changed=%d\n", 
state->color_mgmt_changed);
   821  #if 0
   822 drm_printf(p, "\tcolor-pipeline=%s\n",
   823drm_get_color_pipeline_name(state->color_pipeline));
   824  #else
 > 825 drm_printf(p, "\tcolor-pipeline=%d\n",
   826state->color_pipeline ? 
state->color_pipeline->base.id : 0);
   827  #endif
   828  
   829  
   830  if (plane->funcs->atomic_print_state)
   831  plane->funcs->atomic_print_state(p, state);
   832  }
   833  

-- 
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki


Re: [PATCH 3/4] drm/ttm: Consider hitch moves within bulk sublist moves

2024-02-17 Thread kernel test robot
Hi Thomas,

kernel test robot noticed the following build warnings:

[auto build test WARNING on drm-misc/drm-misc-next]
[also build test WARNING on drm-tip/drm-tip next-20240216]
[cannot apply to drm-intel/for-linux-next drm-intel/for-linux-next-fixes 
linus/master v6.8-rc4]
[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/Thomas-Hellstr-m/drm-ttm-Allow-TTM-LRU-list-nodes-of-different-types/20240216-211801
base:   git://anongit.freedesktop.org/drm/drm-misc drm-misc-next
patch link:
https://lore.kernel.org/r/20240216131446.101961-4-thomas.hellstrom%40linux.intel.com
patch subject: [PATCH 3/4] drm/ttm: Consider hitch moves within bulk sublist 
moves
config: x86_64-randconfig-121-20240217 
(https://download.01.org/0day-ci/archive/20240218/202402180043.xvwojqs2-...@intel.com/config)
compiler: gcc-12 (Debian 12.2.0-14) 12.2.0
reproduce (this is a W=1 build): 
(https://download.01.org/0day-ci/archive/20240218/202402180043.xvwojqs2-...@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 
| Closes: 
https://lore.kernel.org/oe-kbuild-all/202402180043.xvwojqs2-...@intel.com/

sparse warnings: (new ones prefixed by >>)
>> drivers/gpu/drm/ttm/ttm_resource.c:545:34: sparse: sparse: incorrect type in 
>> assignment (different base types) @@ expected unsigned long long 
>> [usertype] bulk_age @@ got unsigned long long * @@
   drivers/gpu/drm/ttm/ttm_resource.c:545:34: sparse: expected unsigned 
long long [usertype] bulk_age
   drivers/gpu/drm/ttm/ttm_resource.c:545:34: sparse: got unsigned long 
long *
>> drivers/gpu/drm/ttm/ttm_resource.c:551:30: sparse: sparse: incompatible 
>> types for operation (==):
   drivers/gpu/drm/ttm/ttm_resource.c:551:30: sparse:unsigned long long 
[usertype] bulk_age
   drivers/gpu/drm/ttm/ttm_resource.c:551:30: sparse:unsigned long long *
   drivers/gpu/drm/ttm/ttm_resource.c: note: in included file (through 
include/linux/fwnode.h, include/linux/logic_pio.h, include/asm-generic/io.h, 
...):
   include/linux/list.h:83:21: sparse: sparse: self-comparison always evaluates 
to true
   include/linux/list.h:83:21: sparse: sparse: self-comparison always evaluates 
to true
   include/linux/list.h:83:21: sparse: sparse: self-comparison always evaluates 
to true
   include/linux/list.h:83:21: sparse: sparse: self-comparison always evaluates 
to true
   include/linux/list.h:83:21: sparse: sparse: self-comparison always evaluates 
to true
   include/linux/list.h:83:21: sparse: sparse: self-comparison always evaluates 
to true
   include/linux/list.h:83:21: sparse: sparse: self-comparison always evaluates 
to true
   include/linux/list.h:83:21: sparse: sparse: self-comparison always evaluates 
to true
   include/linux/list.h:83:21: sparse: sparse: self-comparison always evaluates 
to true
   include/linux/list.h:83:21: sparse: sparse: self-comparison always evaluates 
to true
   include/linux/list.h:83:21: sparse: sparse: self-comparison always evaluates 
to true

vim +545 drivers/gpu/drm/ttm/ttm_resource.c

   517  
   518  /* Adjust to a bulk sublist being bumped while traversing it.*/
   519  static bool
   520  ttm_resource_cursor_check_bulk(struct ttm_resource_cursor *cursor,
   521 struct ttm_lru_item *next_lru)
   522  {
   523  struct ttm_resource *next = ttm_lru_item_to_res(next_lru);
   524  struct ttm_lru_bulk_move *bulk = NULL;
   525  struct ttm_buffer_object *bo = next->bo;
   526  
   527  lockdep_assert_held(>man->bdev->lru_lock);
   528  if (bo && bo->resource == next)
   529  bulk = bo->bulk_move;
   530  
   531  if (!bulk) {
   532  ttm_resource_cursor_clear_bulk(cursor);
   533  return false;
   534  }
   535  
   536  /*
   537   * We encountered a bulk sublist. Record its age and
   538   * set a hitch after the sublist.
   539   */
   540  if (cursor->bulk != bulk) {
   541  struct ttm_lru_bulk_move_pos *pos =
   542  ttm_lru_bulk_move_pos(bulk, next);
   543  
   544  cursor->bulk = bulk;
 > 545  cursor->bulk_age = >age;
   546  list_move(>bulk_hitch.link, 
>last->lru.link);
   547  return false;
   548  }
   549  
   550  /* Continue iterating down the bulk sublist */
 > 551  if (cursor->bulk_age == >age)
   552  return false;
   553  
   554  /*
   555   * The bulk sublist in w

Re: [PATCH v6 1/5] drm: Stop using `select ACPI_VIDEO` in all drivers

2024-02-17 Thread kernel test robot
Hi Mario,

kernel test robot noticed the following build warnings:

[auto build test WARNING on drm-misc/drm-misc-next]
[also build test WARNING on drm-intel/for-linux-next-fixes drm-tip/drm-tip 
linus/master v6.8-rc4 next-20240216]
[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/Mario-Limonciello/drm-Stop-using-select-ACPI_VIDEO-in-all-drivers/20240215-055936
base:   git://anongit.freedesktop.org/drm/drm-misc drm-misc-next
patch link:
https://lore.kernel.org/r/20240214215756.6530-2-mario.limonciello%40amd.com
patch subject: [PATCH v6 1/5] drm: Stop using `select ACPI_VIDEO` in all drivers
config: alpha-kismet-CONFIG_FB_BACKLIGHT-CONFIG_HT16K33-0-0 
(https://download.01.org/0day-ci/archive/20240217/202402171727.maolcpxi-...@intel.com/config)
reproduce: 
(https://download.01.org/0day-ci/archive/20240217/202402171727.maolcpxi-...@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 
| Closes: 
https://lore.kernel.org/oe-kbuild-all/202402171727.maolcpxi-...@intel.com/

kismet warnings: (new ones prefixed by >>)
>> kismet: WARNING: unmet direct dependencies detected for FB_BACKLIGHT when 
>> selected by HT16K33
   .config:210:warning: symbol value 'n' invalid for INPUT_MOUSEDEV_SCREEN_Y
   .config:243:warning: symbol value 'n' invalid for SATA_MOBILE_LPM_POLICY
   .config:338:warning: symbol value 'n' invalid for PSTORE_BLK_MAX_REASON
   .config:435:warning: symbol value 'n' invalid for KFENCE_SAMPLE_INTERVAL
   .config:437:warning: symbol value 'n' invalid for AIC79XX_DEBUG_MASK
   .config:521:warning: symbol value 'n' invalid for 
USB_GADGET_STORAGE_NUM_BUFFERS
   .config:618:warning: symbol value 'n' invalid for DRM_XE_JOB_TIMEOUT_MIN
   .config:632:warning: symbol value 'n' invalid for CRYPTO_DEV_QCE_SW_MAX_LEN
   .config:739:warning: symbol value 'n' invalid for PANEL_LCD_CHARSET
   .config:759:warning: symbol value 'n' invalid for SERIAL_ALTERA_UART_BAUDRATE
   .config:771:warning: symbol value 'n' invalid for SCSI_MESH_RESET_DELAY_MS
   .config:796:warning: symbol value 'n' invalid for SND_AC97_POWER_SAVE_DEFAULT
   .config:834:warning: symbol value 'n' invalid for MAGIC_SYSRQ_DEFAULT_ENABLE
   .config:851:warning: symbol value 'n' invalid for 
DRM_I915_MAX_REQUEST_BUSYWAIT
   .config:890:warning: symbol value 'n' invalid for SND_AT73C213_TARGET_BITRATE
   .config:892:warning: symbol value 'n' invalid for AIC79XX_CMDS_PER_DEVICE
   .config:907:warning: symbol value 'n' invalid for DRM_XE_PREEMPT_TIMEOUT_MIN
   .config:913:warning: symbol value 'n' invalid for NET_EMATCH_STACK
   .config:915:warning: symbol value 'n' invalid for VMCP_CMA_SIZE
   .config:973:warning: symbol value 'n' invalid for PANEL_LCD_PIN_SDA
   .config:1006:warning: symbol value 'n' invalid for PANEL_LCD_PIN_E
   .config:1142:warning: symbol value 'n' invalid for RCU_CPU_STALL_TIMEOUT
   .config:1170:warning: symbol value 'n' invalid for MTDRAM_ERASE_SIZE
   .config:1431:warning: symbol value 'n' invalid for LEGACY_PTY_COUNT
   .config:1581:warning: symbol value 'n' invalid for WATCHDOG_OPEN_TIMEOUT
   .config:1588:warning: symbol value 'n' invalid for AIC7XXX_RESET_DELAY_MS
   .config:1752:warning: symbol value 'n' invalid for IBM_EMAC_POLL_WEIGHT
   .config:1867:warning: symbol value 'n' invalid for DRM_I915_STOP_TIMEOUT
   .config:2098:warning: symbol value 'n' invalid for AIC79XX_RESET_DELAY_MS
   .config:2129:warning: symbol value 'n' invalid for SND_HDA_PREALLOC_SIZE
   .config:2176:warning: symbol value 'n' invalid for RCU_FANOUT_LEAF
   .config:2186:warning: symbol value 'n' invalid for KCOV_IRQ_AREA_SIZE
   .config:2307:warning: symbol value 'n' invalid for DRM_XE_TIMESLICE_MAX
   .config:2321:warning: symbol value 'n' invalid for PANEL_LCD_BWIDTH
   .config:2386:warning: symbol value 'n' invalid for XEN_MEMORY_HOTPLUG_LIMIT
   .config:2439:warning: symbol value 'n' invalid for VERBOSE_MCHECK_ON
   .config:2559:warning: symbol value 'n' invalid for PANEL_PARPORT
   .config:2645:warning: symbol value 'n' invalid for NOUVEAU_DEBUG_DEFAULT
   .config:2744:warning: symbol value 'n' invalid for 
MTD_REDBOOT_DIRECTORY_BLOCK
   .config:2803:warning: symbol value 'n' invalid for 
SND_SOC_SOF_DEBUG_IPC_FLOOD_TEST_NUM
   .config:2831:warning: symbol value 'n' invalid for KCSAN_REPORT_ONCE_IN_MS
   .config:2928:warning: symbol value 'n' invalid for KCSAN_UDELAY_INTERRUPT
   .config:2952:warning: symbol value 'n' invalid for PANEL_LCD_PIN_BL
   .config:2969:warning: symbol value 'n' invalid for 
DEBUG_OBJECTS_ENABLE_DEFAULT
   .config:2977:warning: symbol value 'n' invalid for INITRAMFS_ROOT_GID
   .config:3081:warning: symbol value 'n' invalid for ATM_FORE200E_TX_RET

Re: [PATCH v6 1/5] drm: Stop using `select ACPI_VIDEO` in all drivers

2024-02-16 Thread kernel test robot
Hi Mario,

kernel test robot noticed the following build warnings:

[auto build test WARNING on drm-misc/drm-misc-next]
[also build test WARNING on drm-intel/for-linux-next-fixes drm-tip/drm-tip 
linus/master v6.8-rc4 next-20240216]
[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/Mario-Limonciello/drm-Stop-using-select-ACPI_VIDEO-in-all-drivers/20240215-055936
base:   git://anongit.freedesktop.org/drm/drm-misc drm-misc-next
patch link:
https://lore.kernel.org/r/20240214215756.6530-2-mario.limonciello%40amd.com
patch subject: [PATCH v6 1/5] drm: Stop using `select ACPI_VIDEO` in all drivers
config: alpha-kismet-CONFIG_FB_BACKLIGHT-CONFIG_FB_TFT-0-0 
(https://download.01.org/0day-ci/archive/20240217/202402171302.hkl1cpkb-...@intel.com/config)
reproduce: 
(https://download.01.org/0day-ci/archive/20240217/202402171302.hkl1cpkb-...@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 
| Closes: 
https://lore.kernel.org/oe-kbuild-all/202402171302.hkl1cpkb-...@intel.com/

kismet warnings: (new ones prefixed by >>)
>> kismet: WARNING: unmet direct dependencies detected for FB_BACKLIGHT when 
>> selected by FB_TFT
   .config:262:warning: symbol value 'n' invalid for SATA_MOBILE_LPM_POLICY
   .config:360:warning: symbol value 'n' invalid for PSTORE_BLK_MAX_REASON
   .config:445:warning: symbol value 'n' invalid for KFENCE_SAMPLE_INTERVAL
   .config:599:warning: symbol value 'n' invalid for AIC79XX_DEBUG_MASK
   .config:634:warning: symbol value 'n' invalid for AIC79XX_RESET_DELAY_MS
   .config:638:warning: symbol value 'n' invalid for DRM_XE_JOB_TIMEOUT_MIN
   .config:680:warning: symbol value 'n' invalid for CRYPTO_DEV_QCE_SW_MAX_LEN
   .config:780:warning: symbol value 'n' invalid for PANEL_LCD_CHARSET
   .config:820:warning: symbol value 'n' invalid for SND_AC97_POWER_SAVE_DEFAULT
   .config:881:warning: symbol value 'n' invalid for MAGIC_SYSRQ_DEFAULT_ENABLE
   .config:894:warning: symbol value 'n' invalid for 
DRM_I915_MAX_REQUEST_BUSYWAIT
   .config:928:warning: symbol value 'n' invalid for DRM_XE_PREEMPT_TIMEOUT_MIN
   .config:939:warning: symbol value 'n' invalid for SND_AT73C213_TARGET_BITRATE
   .config:940:warning: symbol value 'n' invalid for NET_EMATCH_STACK
   .config:942:warning: symbol value 'n' invalid for VMCP_CMA_SIZE
   .config:1112:warning: symbol value 'n' invalid for AIC79XX_CMDS_PER_DEVICE
   .config:1181:warning: symbol value 'n' invalid for PANEL_LCD_PIN_SDA
   .config:1208:warning: symbol value 'n' invalid for MTDRAM_ERASE_SIZE
   .config:1238:warning: symbol value 'n' invalid for 
MTD_REDBOOT_DIRECTORY_BLOCK
   .config:1330:warning: symbol value 'n' invalid for SERIAL_UARTLITE_NR_UARTS
   .config:1516:warning: symbol value 'n' invalid for LEGACY_PTY_COUNT
   .config:1666:warning: symbol value 'n' invalid for AIC7XXX_RESET_DELAY_MS
   .config:1808:warning: symbol value 'n' invalid for IBM_EMAC_POLL_WEIGHT
   .config:1972:warning: symbol value 'n' invalid for DRM_I915_STOP_TIMEOUT
   .config:2387:warning: symbol value 'n' invalid for PANEL_LCD_BWIDTH
   .config:2412:warning: symbol value 'n' invalid for DRM_XE_TIMESLICE_MAX
   .config:2427:warning: symbol value 'n' invalid for 
FTRACE_RECORD_RECURSION_SIZE
   .config:2607:warning: symbol value 'n' invalid for KCOV_IRQ_AREA_SIZE
   .config:2633:warning: symbol value 'n' invalid for PANEL_PARPORT
   .config:2722:warning: symbol value 'n' invalid for NOUVEAU_DEBUG_DEFAULT
   .config:2919:warning: symbol value 'n' invalid for KCSAN_REPORT_ONCE_IN_MS
   .config:3017:warning: symbol value 'n' invalid for KCSAN_UDELAY_INTERRUPT
   .config:3041:warning: symbol value 'n' invalid for PANEL_LCD_PIN_BL
   .config:3066:warning: symbol value 'n' invalid for INITRAMFS_ROOT_GID
   .config:3113:warning: symbol value 'n' invalid for 
SND_SOC_SOF_DEBUG_IPC_FLOOD_TEST_NUM
   .config:3132:warning: symbol value 'n' invalid for SCSI_MESH_RESET_DELAY_MS
   .config:3173:warning: symbol value 'n' invalid for ATM_FORE200E_TX_RETRY
   .config:3216:warning: symbol value 'n' invalid for 
FB_OMAP2_DSS_MIN_FCK_PER_PCK
   .config:3306:warning: symbol value 'n' invalid for IP_VS_MH_TAB_INDEX
   .config:3454:warning: symbol value 'n' invalid for PSTORE_BLK_CONSOLE_SIZE
   .config:3554:warning: symbol value 'n' invalid for KCSAN_UDELAY_TASK
   .config:3564:warning: symbol value 'n' invalid for MMC_BLOCK_MINORS
   .config:3567:warning: symbol value 'n' invalid for INET_TABLE_PERTURB_ORDER
   .config:3612:warning: symbol value 'n' invalid for SCSI_NCR53C8XX_SYNC
   .config:3638:warning: symbol value 'n' invalid for BOOKE_WDT_DEFAULT_TIMEOUT
   .config:3730:warning: symbol value 'n' invalid for UCLAMP_BUCKETS_COU

Re: [PATCH 2/4] drm/ttm: Use LRU hitches

2024-02-16 Thread kernel test robot
Hi Thomas,

kernel test robot noticed the following build warnings:

[auto build test WARNING on drm-misc/drm-misc-next]
[also build test WARNING on drm-intel/for-linux-next 
drm-intel/for-linux-next-fixes drm-tip/drm-tip linus/master v6.8-rc4 
next-20240216]
[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/Thomas-Hellstr-m/drm-ttm-Allow-TTM-LRU-list-nodes-of-different-types/20240216-211801
base:   git://anongit.freedesktop.org/drm/drm-misc drm-misc-next
patch link:
https://lore.kernel.org/r/20240216131446.101961-3-thomas.hellstrom%40linux.intel.com
patch subject: [PATCH 2/4] drm/ttm: Use LRU hitches
config: m68k-allmodconfig 
(https://download.01.org/0day-ci/archive/20240217/202402171115.elbabdca-...@intel.com/config)
compiler: m68k-linux-gcc (GCC) 13.2.0
reproduce (this is a W=1 build): 
(https://download.01.org/0day-ci/archive/20240217/202402171115.elbabdca-...@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 
| Closes: 
https://lore.kernel.org/oe-kbuild-all/202402171115.elbabdca-...@intel.com/

All warnings (new ones prefixed by >>):

>> drivers/gpu/drm/ttm/ttm_resource.c:58: warning: expecting prototype for 
>> ttm_resource_cursor_fini_locked(). Prototype was for 
>> ttm_resource_cursor_fini() instead


vim +58 drivers/gpu/drm/ttm/ttm_resource.c

48  
49  /**
50   * ttm_resource_cursor_fini_locked() - Finalize the LRU list cursor 
usage
51   * @cursor: The struct ttm_resource_cursor to finalize.
52   *
53   * The function pulls the LRU list cursor off any lists it was previusly
54   * attached to. Needs to be called without the LRU list lock held. The
55   * function can be called multiple times after eachother.
56   */
57  void ttm_resource_cursor_fini(struct ttm_resource_cursor *cursor)
  > 58  {
59  spinlock_t *lru_lock = >man->bdev->lru_lock;
60  
61  spin_lock(lru_lock);
62  ttm_resource_cursor_fini_locked(cursor);
63  spin_unlock(lru_lock);
64  }
65  

-- 
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki


Re: [PATCH v6 1/5] drm: Stop using `select ACPI_VIDEO` in all drivers

2024-02-16 Thread kernel test robot
Hi Mario,

kernel test robot noticed the following build warnings:

[auto build test WARNING on drm-misc/drm-misc-next]
[also build test WARNING on drm-intel/for-linux-next-fixes drm-tip/drm-tip 
linus/master v6.8-rc4 next-20240216]
[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/Mario-Limonciello/drm-Stop-using-select-ACPI_VIDEO-in-all-drivers/20240215-055936
base:   git://anongit.freedesktop.org/drm/drm-misc drm-misc-next
patch link:
https://lore.kernel.org/r/20240214215756.6530-2-mario.limonciello%40amd.com
patch subject: [PATCH v6 1/5] drm: Stop using `select ACPI_VIDEO` in all drivers
config: alpha-kismet-CONFIG_FB_BACKLIGHT-CONFIG_FB_SSD1307-0-0 
(https://download.01.org/0day-ci/archive/20240217/202402170903.pslaho5f-...@intel.com/config)
reproduce: 
(https://download.01.org/0day-ci/archive/20240217/202402170903.pslaho5f-...@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 
| Closes: 
https://lore.kernel.org/oe-kbuild-all/202402170903.pslaho5f-...@intel.com/

kismet warnings: (new ones prefixed by >>)
>> kismet: WARNING: unmet direct dependencies detected for FB_BACKLIGHT when 
>> selected by FB_SSD1307
   .config:254:warning: symbol value 'n' invalid for SATA_MOBILE_LPM_POLICY
   .config:268:warning: symbol value 'n' invalid for INPUT_MOUSEDEV_SCREEN_Y
   .config:441:warning: symbol value 'n' invalid for KFENCE_SAMPLE_INTERVAL
   .config:460:warning: symbol value 'n' invalid for AIC79XX_DEBUG_MASK
   .config:610:warning: symbol value 'n' invalid for 
USB_GADGET_STORAGE_NUM_BUFFERS
   .config:619:warning: symbol value 'n' invalid for DRM_XE_JOB_TIMEOUT_MIN
   .config:645:warning: symbol value 'n' invalid for CRYPTO_DEV_QCE_SW_MAX_LEN
   .config:757:warning: symbol value 'n' invalid for PANEL_LCD_CHARSET
   .config:758:warning: symbol value 'n' invalid for SERIAL_ALTERA_UART_BAUDRATE
   .config:800:warning: symbol value 'n' invalid for SND_AC97_POWER_SAVE_DEFAULT
   .config:834:warning: symbol value 'n' invalid for DUMMY_CONSOLE_ROWS
   .config:844:warning: symbol value 'n' invalid for MAGIC_SYSRQ_DEFAULT_ENABLE
   .config:858:warning: symbol value 'n' invalid for 
DRM_I915_MAX_REQUEST_BUSYWAIT
   .config:882:warning: symbol value 'n' invalid for AIC79XX_CMDS_PER_DEVICE
   .config:894:warning: symbol value 'n' invalid for SND_AT73C213_TARGET_BITRATE
   .config:903:warning: symbol value 'n' invalid for DRM_XE_PREEMPT_TIMEOUT_MIN
   .config:915:warning: symbol value 'n' invalid for NET_EMATCH_STACK
   .config:917:warning: symbol value 'n' invalid for VMCP_CMA_SIZE
   .config:942:warning: symbol value 'n' invalid for PANEL_LCD_PIN_SDA
   .config:1062:warning: symbol value 'n' invalid for PANEL_LCD_PIN_E
   .config:1143:warning: symbol value 'n' invalid for RCU_CPU_STALL_TIMEOUT
   .config:1173:warning: symbol value 'n' invalid for MTDRAM_ERASE_SIZE
   .config:1281:warning: symbol value 'n' invalid for SERIAL_UARTLITE_NR_UARTS
   .config:1324:warning: symbol value 'n' invalid for VERBOSE_MCHECK_ON
   .config:1453:warning: symbol value 'n' invalid for LEGACY_PTY_COUNT
   .config:1605:warning: symbol value 'n' invalid for AIC7XXX_RESET_DELAY_MS
   .config:1659:warning: symbol value 'n' invalid for XEN_MEMORY_HOTPLUG_LIMIT
   .config:1755:warning: symbol value 'n' invalid for IBM_EMAC_POLL_WEIGHT
   .config:1881:warning: symbol value 'n' invalid for DRM_I915_STOP_TIMEOUT
   .config:2135:warning: symbol value 'n' invalid for AIC79XX_RESET_DELAY_MS
   .config:2155:warning: symbol value 'n' invalid for KCOV_IRQ_AREA_SIZE
   .config:2172:warning: symbol value 'n' invalid for RCU_FANOUT_LEAF
   .config:2315:warning: symbol value 'n' invalid for DRM_XE_TIMESLICE_MAX
   .config:2317:warning: symbol value 'n' invalid for PANEL_LCD_BWIDTH
   .config:2557:warning: symbol value 'n' invalid for PANEL_PARPORT
   .config:2643:warning: symbol value 'n' invalid for NOUVEAU_DEBUG_DEFAULT
   .config:2791:warning: symbol value 'n' invalid for 
SND_SOC_SOF_DEBUG_IPC_FLOOD_TEST_NUM
   .config:2831:warning: symbol value 'n' invalid for KCSAN_REPORT_ONCE_IN_MS
   .config:2932:warning: symbol value 'n' invalid for KCSAN_UDELAY_INTERRUPT
   .config:2954:warning: symbol value 'n' invalid for PANEL_LCD_PIN_BL
   .config:2972:warning: symbol value 'n' invalid for 
DEBUG_OBJECTS_ENABLE_DEFAULT
   .config:2978:warning: symbol value 'n' invalid for INITRAMFS_ROOT_GID
   .config:3082:warning: symbol value 'n' invalid for ATM_FORE200E_TX_RETRY
   .config:3119:warning: symbol value 'n' invalid for 
FB_OMAP2_DSS_MIN_FCK_PER_PCK
   .config:3212:warning: symbol value 'n' invalid for PSTORE_BLK_CONSOLE_SIZE
   .config:3341:warning: symbol value 'n' invalid for BOOKE_W

Re: [PATCH 3/4] drm/ttm: Consider hitch moves within bulk sublist moves

2024-02-16 Thread kernel test robot
Hi Thomas,

kernel test robot noticed the following build warnings:

[auto build test WARNING on drm-misc/drm-misc-next]
[also build test WARNING on drm-tip/drm-tip next-20240216]
[cannot apply to drm-intel/for-linux-next drm-intel/for-linux-next-fixes 
linus/master v6.8-rc4]
[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/Thomas-Hellstr-m/drm-ttm-Allow-TTM-LRU-list-nodes-of-different-types/20240216-211801
base:   git://anongit.freedesktop.org/drm/drm-misc drm-misc-next
patch link:
https://lore.kernel.org/r/20240216131446.101961-4-thomas.hellstrom%40linux.intel.com
patch subject: [PATCH 3/4] drm/ttm: Consider hitch moves within bulk sublist 
moves
config: arm-defconfig 
(https://download.01.org/0day-ci/archive/20240217/202402170714.cfloudkj-...@intel.com/config)
compiler: clang version 14.0.6 (https://github.com/llvm/llvm-project.git 
f28c006a5895fc0e329fe15fead81e37457cb1d1)
reproduce (this is a W=1 build): 
(https://download.01.org/0day-ci/archive/20240217/202402170714.cfloudkj-...@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 
| Closes: 
https://lore.kernel.org/oe-kbuild-all/202402170714.cfloudkj-...@intel.com/

All warnings (new ones prefixed by >>):

>> drivers/gpu/drm/ttm/ttm_resource.c:545:20: warning: incompatible pointer to 
>> integer conversion assigning to 'u64' (aka 'unsigned long long') from 'u64 
>> *' (aka 'unsigned long long *'); remove & [-Wint-conversion]
   cursor->bulk_age = >age;
^ ~~
>> drivers/gpu/drm/ttm/ttm_resource.c:551:23: warning: comparison between 
>> pointer and integer ('u64' (aka 'unsigned long long') and 'u64 *' (aka 
>> 'unsigned long long *')) [-Wpointer-integer-compare]
   if (cursor->bulk_age == >age)
    ^  ~~
   2 warnings generated.


vim +545 drivers/gpu/drm/ttm/ttm_resource.c

   517  
   518  /* Adjust to a bulk sublist being bumped while traversing it.*/
   519  static bool
   520  ttm_resource_cursor_check_bulk(struct ttm_resource_cursor *cursor,
   521 struct ttm_lru_item *next_lru)
   522  {
   523  struct ttm_resource *next = ttm_lru_item_to_res(next_lru);
   524  struct ttm_lru_bulk_move *bulk = NULL;
   525  struct ttm_buffer_object *bo = next->bo;
   526  
   527  lockdep_assert_held(>man->bdev->lru_lock);
   528  if (bo && bo->resource == next)
   529  bulk = bo->bulk_move;
   530  
   531  if (!bulk) {
   532  ttm_resource_cursor_clear_bulk(cursor);
   533  return false;
   534  }
   535  
   536  /*
   537   * We encountered a bulk sublist. Record its age and
   538   * set a hitch after the sublist.
   539   */
   540  if (cursor->bulk != bulk) {
   541  struct ttm_lru_bulk_move_pos *pos =
   542  ttm_lru_bulk_move_pos(bulk, next);
   543  
   544  cursor->bulk = bulk;
 > 545  cursor->bulk_age = >age;
   546  list_move(>bulk_hitch.link, 
>last->lru.link);
   547  return false;
   548  }
   549  
   550  /* Continue iterating down the bulk sublist */
 > 551  if (cursor->bulk_age == >age)
   552  return false;
   553  
   554  /*
   555   * The bulk sublist in which we had a hitch has moved and the
   556   * hitch moved with it. Restart iteration from a previously
   557   * set hitch after the bulk_move, and remove that backup
   558   * hitch.
   559   */
   560  list_move(>hitch.link, >bulk_hitch.link);
   561  ttm_resource_cursor_clear_bulk(cursor);
   562  
   563  return true;
   564  }
   565  

-- 
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki


Re: [PATCH v6 1/5] drm: Stop using `select ACPI_VIDEO` in all drivers

2024-02-16 Thread kernel test robot
Hi Mario,

kernel test robot noticed the following build warnings:

[auto build test WARNING on drm-misc/drm-misc-next]
[also build test WARNING on drm-intel/for-linux-next-fixes drm-tip/drm-tip 
linus/master v6.8-rc4 next-20240216]
[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/Mario-Limonciello/drm-Stop-using-select-ACPI_VIDEO-in-all-drivers/20240215-055936
base:   git://anongit.freedesktop.org/drm/drm-misc drm-misc-next
patch link:
https://lore.kernel.org/r/20240214215756.6530-2-mario.limonciello%40amd.com
patch subject: [PATCH v6 1/5] drm: Stop using `select ACPI_VIDEO` in all drivers
config: alpha-kismet-CONFIG_FB_BACKLIGHT-CONFIG_FB_SH_MOBILE_LCDC-0-0 
(https://download.01.org/0day-ci/archive/20240217/202402170543.qd0jrj6h-...@intel.com/config)
reproduce: 
(https://download.01.org/0day-ci/archive/20240217/202402170543.qd0jrj6h-...@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 
| Closes: 
https://lore.kernel.org/oe-kbuild-all/202402170543.qd0jrj6h-...@intel.com/

kismet warnings: (new ones prefixed by >>)
>> kismet: WARNING: unmet direct dependencies detected for FB_BACKLIGHT when 
>> selected by FB_SH_MOBILE_LCDC
   .config:92:warning: symbol value 'n' invalid for AIC7XXX_DEBUG_MASK
   .config:218:warning: symbol value 'n' invalid for RAPIDIO_DISC_TIMEOUT
   .config:242:warning: symbol value 'n' invalid for SATA_MOBILE_LPM_POLICY
   .config:259:warning: symbol value 'n' invalid for FAT_DEFAULT_CODEPAGE
   .config:339:warning: symbol value 'n' invalid for PSTORE_BLK_MAX_REASON
   .config:341:warning: symbol value 'n' invalid for PANEL_PROFILE
   .config:352:warning: symbol value 'n' invalid for AIC79XX_DEBUG_MASK
   .config:432:warning: symbol value 'n' invalid for KFENCE_SAMPLE_INTERVAL
   .config:610:warning: symbol value 'n' invalid for DRM_XE_JOB_TIMEOUT_MIN
   .config:616:warning: symbol value 'n' invalid for CRYPTO_DEV_QCE_SW_MAX_LEN
   .config:717:warning: symbol value 'n' invalid for PANEL_LCD_CHARSET
   .config:755:warning: symbol value 'n' invalid for AIC79XX_CMDS_PER_DEVICE
   .config:784:warning: symbol value 'n' invalid for SND_AC97_POWER_SAVE_DEFAULT
   .config:805:warning: symbol value 'n' invalid for PANEL_LCD_PIN_SDA
   .config:807:warning: symbol value 'n' invalid for MAGIC_SYSRQ_DEFAULT_ENABLE
   .config:825:warning: symbol value 'n' invalid for 
DRM_I915_MAX_REQUEST_BUSYWAIT
   .config:864:warning: symbol value 'n' invalid for SND_AT73C213_TARGET_BITRATE
   .config:886:warning: symbol value 'n' invalid for DRM_XE_PREEMPT_TIMEOUT_MIN
   .config:894:warning: symbol value 'n' invalid for NET_EMATCH_STACK
   .config:896:warning: symbol value 'n' invalid for VMCP_CMA_SIZE
   .config:988:warning: symbol value 'n' invalid for INPUT_MOUSEDEV_SCREEN_Y
   .config:1124:warning: symbol value 'n' invalid for RCU_CPU_STALL_TIMEOUT
   .config:1150:warning: symbol value 'n' invalid for MTDRAM_ERASE_SIZE
   .config:1237:warning: symbol value 'n' invalid for SERIAL_UARTLITE_NR_UARTS
   .config:1303:warning: symbol value 'n' invalid for 
USB_GADGET_STORAGE_NUM_BUFFERS
   .config:1396:warning: symbol value 'n' invalid for LEGACY_PTY_COUNT
   .config:1533:warning: symbol value 'n' invalid for AIC7XXX_RESET_DELAY_MS
   .config:1723:warning: symbol value 'n' invalid for IBM_EMAC_POLL_WEIGHT
   .config:1759:warning: symbol value 'n' invalid for PANEL_LCD_PIN_E
   .config:1805:warning: symbol value 'n' invalid for DRM_I915_STOP_TIMEOUT
   .config:1981:warning: symbol value 'n' invalid for KCOV_IRQ_AREA_SIZE
   .config:2132:warning: symbol value 'n' invalid for RCU_FANOUT_LEAF
   .config:2232:warning: symbol value 'n' invalid for DRM_XE_TIMESLICE_MAX
   .config:2278:warning: symbol value 'n' invalid for PANEL_LCD_BWIDTH
   .config:2512:warning: symbol value 'n' invalid for PANEL_PARPORT
   .config:2520:warning: symbol value 'n' invalid for 
SND_SOC_SOF_DEBUG_IPC_FLOOD_TEST_NUM
   .config:2599:warning: symbol value 'n' invalid for NOUVEAU_DEBUG_DEFAULT
   .config:2785:warning: symbol value 'n' invalid for KCSAN_REPORT_ONCE_IN_MS
   .config:2883:warning: symbol value 'n' invalid for PSTORE_BLK_CONSOLE_SIZE
   .config:2884:warning: symbol value 'n' invalid for KCSAN_UDELAY_INTERRUPT
   .config:2894:warning: symbol value 'n' invalid for AIC79XX_RESET_DELAY_MS
   .config:2908:warning: symbol value 'n' invalid for PANEL_LCD_PIN_BL
   .config:2924:warning: symbol value 'n' invalid for 
DEBUG_OBJECTS_ENABLE_DEFAULT
   .config:2931:warning: symbol value 'n' invalid for INITRAMFS_ROOT_GID
   .config:3032:warning: symbol value 'n' invalid for ATM_FORE200E_TX_RETRY
   .config:3059:warning: symbol value 'n' invalid for BOOKE_WDT_DEFAULT_TIMEO

Re: [PATCH v6 1/5] drm: Stop using `select ACPI_VIDEO` in all drivers

2024-02-16 Thread kernel test robot
Hi Mario,

kernel test robot noticed the following build warnings:

[auto build test WARNING on drm-misc/drm-misc-next]
[also build test WARNING on drm-intel/for-linux-next-fixes drm-tip/drm-tip 
linus/master v6.8-rc4 next-20240216]
[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/Mario-Limonciello/drm-Stop-using-select-ACPI_VIDEO-in-all-drivers/20240215-055936
base:   git://anongit.freedesktop.org/drm/drm-misc drm-misc-next
patch link:
https://lore.kernel.org/r/20240214215756.6530-2-mario.limonciello%40amd.com
patch subject: [PATCH v6 1/5] drm: Stop using `select ACPI_VIDEO` in all drivers
config: alpha-kismet-CONFIG_FB_BACKLIGHT-CONFIG_FB_RIVA-0-0 
(https://download.01.org/0day-ci/archive/20240217/202402170047.mijmtqic-...@intel.com/config)
reproduce: 
(https://download.01.org/0day-ci/archive/20240217/202402170047.mijmtqic-...@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 
| Closes: 
https://lore.kernel.org/oe-kbuild-all/202402170047.mijmtqic-...@intel.com/

kismet warnings: (new ones prefixed by >>)
>> kismet: WARNING: unmet direct dependencies detected for FB_BACKLIGHT when 
>> selected by FB_RIVA
   .config:69:warning: symbol value 'n' invalid for FAT_DEFAULT_CODEPAGE
   .config:240:warning: symbol value 'n' invalid for SATA_MOBILE_LPM_POLICY
   .config:307:warning: symbol value 'n' invalid for XEN_MEMORY_HOTPLUG_LIMIT
   .config:328:warning: symbol value 'n' invalid for PSTORE_BLK_MAX_REASON
   .config:359:warning: symbol value 'n' invalid for AIC79XX_DEBUG_MASK
   .config:429:warning: symbol value 'n' invalid for KFENCE_SAMPLE_INTERVAL
   .config:612:warning: symbol value 'n' invalid for CRYPTO_DEV_QCE_SW_MAX_LEN
   .config:613:warning: symbol value 'n' invalid for DRM_XE_JOB_TIMEOUT_MIN
   .config:702:warning: symbol value 'n' invalid for VGA_ARB_MAX_GPUS
   .config:715:warning: symbol value 'n' invalid for PANEL_LCD_CHARSET
   .config:789:warning: symbol value 'n' invalid for SND_AC97_POWER_SAVE_DEFAULT
   .config:793:warning: symbol value 'n' invalid for INPUT_MOUSEDEV_SCREEN_Y
   .config:811:warning: symbol value 'n' invalid for AIC79XX_CMDS_PER_DEVICE
   .config:830:warning: symbol value 'n' invalid for 
DRM_I915_MAX_REQUEST_BUSYWAIT
   .config:855:warning: symbol value 'n' invalid for SND_AT73C213_TARGET_BITRATE
   .config:877:warning: symbol value 'n' invalid for PANEL_LCD_PIN_SDA
   .config:893:warning: symbol value 'n' invalid for DRM_XE_PREEMPT_TIMEOUT_MIN
   .config:901:warning: symbol value 'n' invalid for NET_EMATCH_STACK
   .config:903:warning: symbol value 'n' invalid for VMCP_CMA_SIZE
   .config:1095:warning: symbol value 'n' invalid for 
USB_GADGET_STORAGE_NUM_BUFFERS
   .config:1130:warning: symbol value 'n' invalid for RCU_CPU_STALL_TIMEOUT
   .config:1159:warning: symbol value 'n' invalid for MTDRAM_ERASE_SIZE
   .config:1238:warning: symbol value 'n' invalid for SERIAL_UARTLITE_NR_UARTS
   .config:1397:warning: symbol value 'n' invalid for LEGACY_PTY_COUNT
   .config:1524:warning: symbol value 'n' invalid for PANEL_LCD_PIN_E
   .config:1528:warning: symbol value 'n' invalid for AIC7XXX_RESET_DELAY_MS
   .config:1726:warning: symbol value 'n' invalid for IBM_EMAC_POLL_WEIGHT
   .config:1763:warning: symbol value 'n' invalid for SCSI_MESH_RESET_DELAY_MS
   .config:1817:warning: symbol value 'n' invalid for DRM_I915_STOP_TIMEOUT
   .config:2048:warning: symbol value 'n' invalid for KCOV_IRQ_AREA_SIZE
   .config:2143:warning: symbol value 'n' invalid for RCU_FANOUT_LEAF
   .config:2237:warning: symbol value 'n' invalid for DRM_XE_TIMESLICE_MAX
   .config:2290:warning: symbol value 'n' invalid for PANEL_LCD_BWIDTH
   .config:2523:warning: symbol value 'n' invalid for PANEL_PARPORT
   .config:2568:warning: symbol value 'n' invalid for 
SND_SOC_SOF_DEBUG_IPC_FLOOD_TEST_NUM
   .config:2606:warning: symbol value 'n' invalid for NOUVEAU_DEBUG_DEFAULT
   .config:2707:warning: symbol value 'n' invalid for AIC79XX_RESET_DELAY_MS
   .config:2779:warning: symbol value 'n' invalid for 
SERIAL_ALTERA_UART_BAUDRATE
   .config:2791:warning: symbol value 'n' invalid for KCSAN_REPORT_ONCE_IN_MS
   .config:2888:warning: symbol value 'n' invalid for KCSAN_UDELAY_INTERRUPT
   .config:2910:warning: symbol value 'n' invalid for PANEL_LCD_PIN_BL
   .config:2934:warning: symbol value 'n' invalid for INITRAMFS_ROOT_GID
   .config:2968:warning: symbol value 'n' invalid for DUMMY_CONSOLE_ROWS
   .config:3008:warning: symbol value 'n' invalid for PSTORE_BLK_CONSOLE_SIZE
   .config:3038:warning: symbol value 'n' invalid for ATM_FORE200E_TX_RETRY
   .config:3078:warning: symbol value 'n' invalid for 
FB_OMAP2_DSS_MIN_FCK_PER_PCK
   .c

Re: [PATCH v6 1/5] drm: Stop using `select ACPI_VIDEO` in all drivers

2024-02-16 Thread kernel test robot
Hi Mario,

kernel test robot noticed the following build warnings:

[auto build test WARNING on drm-misc/drm-misc-next]
[also build test WARNING on drm-intel/for-linux-next-fixes drm-tip/drm-tip 
linus/master v6.8-rc4 next-20240216]
[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/Mario-Limonciello/drm-Stop-using-select-ACPI_VIDEO-in-all-drivers/20240215-055936
base:   git://anongit.freedesktop.org/drm/drm-misc drm-misc-next
patch link:
https://lore.kernel.org/r/20240214215756.6530-2-mario.limonciello%40amd.com
patch subject: [PATCH v6 1/5] drm: Stop using `select ACPI_VIDEO` in all drivers
config: alpha-kismet-CONFIG_FB_BACKLIGHT-CONFIG_FB_RADEON-0-0 
(https://download.01.org/0day-ci/archive/20240216/202402162046.jr7hgb8p-...@intel.com/config)
reproduce: 
(https://download.01.org/0day-ci/archive/20240216/202402162046.jr7hgb8p-...@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 
| Closes: 
https://lore.kernel.org/oe-kbuild-all/202402162046.jr7hgb8p-...@intel.com/

kismet warnings: (new ones prefixed by >>)
>> kismet: WARNING: unmet direct dependencies detected for FB_BACKLIGHT when 
>> selected by FB_RADEON
   .config:171:warning: symbol value 'n' invalid for PANEL_LCD_PIN_E
   .config:253:warning: symbol value 'n' invalid for SATA_MOBILE_LPM_POLICY
   .config:358:warning: symbol value 'n' invalid for PSTORE_BLK_MAX_REASON
   .config:438:warning: symbol value 'n' invalid for KFENCE_SAMPLE_INTERVAL
   .config:623:warning: symbol value 'n' invalid for DRM_XE_JOB_TIMEOUT_MIN
   .config:662:warning: symbol value 'n' invalid for CRYPTO_DEV_QCE_SW_MAX_LEN
   .config:677:warning: symbol value 'n' invalid for AIC79XX_DEBUG_MASK
   .config:773:warning: symbol value 'n' invalid for PANEL_LCD_CHARSET
   .config:804:warning: symbol value 'n' invalid for SND_AC97_POWER_SAVE_DEFAULT
   .config:870:warning: symbol value 'n' invalid for MAGIC_SYSRQ_DEFAULT_ENABLE
   .config:891:warning: symbol value 'n' invalid for 
DRM_I915_MAX_REQUEST_BUSYWAIT
   .config:918:warning: symbol value 'n' invalid for DRM_XE_PREEMPT_TIMEOUT_MIN
   .config:928:warning: symbol value 'n' invalid for NET_EMATCH_STACK
   .config:930:warning: symbol value 'n' invalid for VMCP_CMA_SIZE
   .config:935:warning: symbol value 'n' invalid for SND_AT73C213_TARGET_BITRATE
   .config:1064:warning: symbol value 'n' invalid for AIC79XX_CMDS_PER_DEVICE
   .config:1162:warning: symbol value 'n' invalid for RCU_CPU_STALL_TIMEOUT
   .config:1182:warning: symbol value 'n' invalid for PANEL_LCD_PIN_SDA
   .config:1190:warning: symbol value 'n' invalid for MTDRAM_ERASE_SIZE
   .config:1220:warning: symbol value 'n' invalid for AIC79XX_RESET_DELAY_MS
   .config:1312:warning: symbol value 'n' invalid for SERIAL_UARTLITE_NR_UARTS
   .config:1493:warning: symbol value 'n' invalid for LEGACY_PTY_COUNT
   .config:1636:warning: symbol value 'n' invalid for AIC7XXX_RESET_DELAY_MS
   .config:1637:warning: symbol value 'n' invalid for WATCHDOG_OPEN_TIMEOUT
   .config:1782:warning: symbol value 'n' invalid for IBM_EMAC_POLL_WEIGHT
   .config:1788:warning: symbol value 'n' invalid for 
MTD_REDBOOT_DIRECTORY_BLOCK
   .config:1939:warning: symbol value 'n' invalid for DRM_I915_STOP_TIMEOUT
   .config:2157:warning: symbol value 'n' invalid for SND_HDA_PREALLOC_SIZE
   .config:2205:warning: symbol value 'n' invalid for RCU_FANOUT_LEAF
   .config:2353:warning: symbol value 'n' invalid for PANEL_LCD_BWIDTH
   .config:2384:warning: symbol value 'n' invalid for DRM_XE_TIMESLICE_MAX
   .config:2400:warning: symbol value 'n' invalid for SERIAL_AR933X_NR_UARTS
   .config:2594:warning: symbol value 'n' invalid for PANEL_PARPORT
   .config:2634:warning: symbol value 'n' invalid for KCOV_IRQ_AREA_SIZE
   .config:2681:warning: symbol value 'n' invalid for NOUVEAU_DEBUG_DEFAULT
   .config:2872:warning: symbol value 'n' invalid for KCSAN_REPORT_ONCE_IN_MS
   .config:2971:warning: symbol value 'n' invalid for KCSAN_UDELAY_INTERRUPT
   .config:2994:warning: symbol value 'n' invalid for PANEL_LCD_PIN_BL
   .config:3020:warning: symbol value 'n' invalid for INITRAMFS_ROOT_GID
   .config:3048:warning: symbol value 'n' invalid for 
FTRACE_RECORD_RECURSION_SIZE
   .config:3128:warning: symbol value 'n' invalid for ATM_FORE200E_TX_RETRY
   .config:3165:warning: symbol value 'n' invalid for 
FB_OMAP2_DSS_MIN_FCK_PER_PCK
   .config:3203:warning: symbol value 'n' invalid for 
SND_SOC_SOF_DEBUG_IPC_FLOOD_TEST_NUM
   .config:3465:warning: symbol value 'n' invalid for PSTORE_BLK_CONSOLE_SIZE
   .config:3493:warning: symbol value 'n' invalid for KCSAN_UDELAY_TASK
   .config:3514:warning: symbol value 'n' invalid for MMC_BLOCK_MINORS
   .c

Re: [PATCH 01/28] [NOT FOR REVIEW] drm: color pipeline base work

2024-02-16 Thread kernel test robot
Hi Uma,

kernel test robot noticed the following build warnings:

[auto build test WARNING on drm-misc/drm-misc-next]
[also build test WARNING on drm/drm-next next-20240216]
[cannot apply to drm-intel/for-linux-next drm-intel/for-linux-next-fixes 
linus/master v6.8-rc4]
[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/Uma-Shankar/drm-color-pipeline-base-work/20240213-144544
base:   git://anongit.freedesktop.org/drm/drm-misc drm-misc-next
patch link:
https://lore.kernel.org/r/20240213064835.139464-2-uma.shankar%40intel.com
patch subject: [PATCH 01/28] [NOT FOR REVIEW] drm: color pipeline base work
config: x86_64-randconfig-121-20240214 
(https://download.01.org/0day-ci/archive/20240216/202402161931.6z8xdviq-...@intel.com/config)
compiler: gcc-12 (Debian 12.2.0-14) 12.2.0
reproduce (this is a W=1 build): 
(https://download.01.org/0day-ci/archive/20240216/202402161931.6z8xdviq-...@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 
| Closes: 
https://lore.kernel.org/oe-kbuild-all/202402161931.6z8xdviq-...@intel.com/

sparse warnings: (new ones prefixed by >>)
>> drivers/gpu/drm/vkms/vkms_colorop.c:11:11: sparse: sparse: symbol 
>> 'vkms_initialize_tf_pipeline' was not declared. Should it be static?
--
   drivers/gpu/drm/vkms/vkms_composer.c: note: in included file:
>> drivers/gpu/drm/vkms/tests/vkms_color_tests.c:29:29: sparse: sparse: symbol 
>> 'test_linear_lut' was not declared. Should it be static?
>> drivers/gpu/drm/vkms/tests/vkms_color_tests.c:87:32: sparse: sparse: symbol 
>> 'test_matrix_3x4_50_desat' was not declared. Should it be static?
>> drivers/gpu/drm/vkms/tests/vkms_color_tests.c:146:32: sparse: sparse: symbol 
>> 'test_matrix_3x4_bt709_enc' was not declared. Should it be static?

vim +/vkms_initialize_tf_pipeline +11 drivers/gpu/drm/vkms/vkms_colorop.c

10  
  > 11  const int vkms_initialize_tf_pipeline(struct drm_plane *plane, struct 
drm_prop_enum_list *list)
12  {
13  
14  struct drm_colorop *op, *prev_op;
15  struct drm_device *dev = plane->dev;
16  int ret;
17  
18  /* 1st op: 1d curve */
19  op = kzalloc(sizeof(struct drm_colorop), GFP_KERNEL);
20  if (!op) {
21  DRM_ERROR("KMS: Failed to allocate colorop\n");
22  return -ENOMEM;
23  }
24  
25  ret = drm_colorop_init(dev, op, plane, DRM_COLOROP_1D_CURVE);
26  if (ret)
27  return ret;
28  
29  list->type = op->base.id;
30  list->name = kasprintf(GFP_KERNEL, "Color Pipeline %d", 
op->base.id);
31  
32  prev_op = op;
33  
34  /* 2nd op: 3x4 matrix */
35  op = kzalloc(sizeof(struct drm_colorop), GFP_KERNEL);
36  if (!op) {
37  DRM_ERROR("KMS: Failed to allocate colorop\n");
38  return -ENOMEM;
39  }
40  
41  ret = drm_colorop_init(dev, op, plane, DRM_COLOROP_CTM_3X4);
42  if (ret)
43  return ret;
44  
45  drm_colorop_set_next_property(prev_op, op);
46  
47  prev_op = op;
48  
49  /* 3rd op: 3x4 matrix */
50  op = kzalloc(sizeof(struct drm_colorop), GFP_KERNEL);
51  if (!op) {
52  DRM_ERROR("KMS: Failed to allocate colorop\n");
53  return -ENOMEM;
54  }
55  
56  ret = drm_colorop_init(dev, op, plane, DRM_COLOROP_CTM_3X4);
57  if (ret)
58  return ret;
59  
60  drm_colorop_set_next_property(prev_op, op);
61  
62  prev_op = op;
63  
64  /* 4th op: 1d curve */
65  op = kzalloc(sizeof(struct drm_colorop), GFP_KERNEL);
66  if (!op) {
67  DRM_ERROR("KMS: Failed to allocate colorop\n");
68  return -ENOMEM;
69  }
70  
71  ret = drm_colorop_init(dev, op, plane, DRM_COLOROP_1D_CURVE);
72  if (ret)
73  return ret;
74  
75  drm_colorop_set_next_property(prev_op, op);
76  
77  return 0;
78  }
79  

-- 
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki


Re: [PATCH v6 1/5] drm: Stop using `select ACPI_VIDEO` in all drivers

2024-02-16 Thread kernel test robot
Hi Mario,

kernel test robot noticed the following build warnings:

[auto build test WARNING on drm-misc/drm-misc-next]
[also build test WARNING on drm-intel/for-linux-next-fixes drm-tip/drm-tip 
linus/master v6.8-rc4 next-20240216]
[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/Mario-Limonciello/drm-Stop-using-select-ACPI_VIDEO-in-all-drivers/20240215-055936
base:   git://anongit.freedesktop.org/drm/drm-misc drm-misc-next
patch link:
https://lore.kernel.org/r/20240214215756.6530-2-mario.limonciello%40amd.com
patch subject: [PATCH v6 1/5] drm: Stop using `select ACPI_VIDEO` in all drivers
config: powerpc-kismet-CONFIG_FB_BACKLIGHT-CONFIG_PMAC_BACKLIGHT-0-0 
(https://download.01.org/0day-ci/archive/20240216/202402161747.txwr5bw4-...@intel.com/config)
reproduce: 
(https://download.01.org/0day-ci/archive/20240216/202402161747.txwr5bw4-...@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 
| Closes: 
https://lore.kernel.org/oe-kbuild-all/202402161747.txwr5bw4-...@intel.com/

kismet warnings: (new ones prefixed by >>)
>> kismet: WARNING: unmet direct dependencies detected for FB_BACKLIGHT when 
>> selected by PMAC_BACKLIGHT
   .config:247:warning: symbol value 'n' invalid for AIC79XX_DEBUG_MASK
   .config:251:warning: symbol value 'n' invalid for PANEL_LCD_PIN_E
   .config:262:warning: symbol value 'n' invalid for SATA_MOBILE_LPM_POLICY
   .config:356:warning: symbol value 'n' invalid for PSTORE_BLK_MAX_REASON
   .config:407:warning: symbol value 'n' invalid for 
PPC_EARLY_DEBUG_16550_PHYSADDR
   .config:462:warning: symbol value 'n' invalid for KFENCE_SAMPLE_INTERVAL
   .config:563:warning: symbol value 'n' invalid for 
PPC_EARLY_DEBUG_HVSI_VTERMNO
   .config:663:warning: symbol value 'n' invalid for DRM_XE_JOB_TIMEOUT_MIN
   .config:677:warning: symbol value 'n' invalid for CRYPTO_DEV_QCE_SW_MAX_LEN
   .config:710:warning: symbol value 'n' invalid for AIC79XX_CMDS_PER_DEVICE
   .config:725:warning: symbol value 'n' invalid for DATA_SHIFT
   .config:765:warning: symbol value 'n' invalid for PANEL_LCD_PIN_SDA
   .config:793:warning: symbol value 'n' invalid for PANEL_LCD_CHARSET
   .config:854:warning: symbol value 'n' invalid for SND_AC97_POWER_SAVE_DEFAULT
   .config:904:warning: symbol value 'n' invalid for MAGIC_SYSRQ_DEFAULT_ENABLE
   .config:922:warning: symbol value 'n' invalid for 
DRM_I915_MAX_REQUEST_BUSYWAIT
   .config:958:warning: symbol value 'n' invalid for SND_AT73C213_TARGET_BITRATE
   .config:974:warning: symbol value 'n' invalid for DRM_XE_PREEMPT_TIMEOUT_MIN
   .config:986:warning: symbol value 'n' invalid for VMCP_CMA_SIZE
   .config:1270:warning: symbol value 'n' invalid for MTDRAM_ERASE_SIZE
   .config:1365:warning: symbol value 'n' invalid for SERIAL_UARTLITE_NR_UARTS
   .config:1398:warning: symbol value 'n' invalid for AIC79XX_RESET_DELAY_MS
   .config:1548:warning: symbol value 'n' invalid for LEGACY_PTY_COUNT
   .config:1673:warning: symbol value 'n' invalid for LOWMEM_CAM_NUM
   .config:1723:warning: symbol value 'n' invalid for AIC7XXX_RESET_DELAY_MS
   .config:1805:warning: symbol value 'n' invalid for PPC_MEMCONS_OUTPUT_SIZE
   .config:1874:warning: symbol value 'n' invalid for LOWMEM_SIZE
   .config:1899:warning: symbol value 'n' invalid for IBM_EMAC_POLL_WEIGHT
   .config:2030:warning: symbol value 'n' invalid for PANEL_PROFILE
   .config:2042:warning: symbol value 'n' invalid for DRM_I915_STOP_TIMEOUT
   .config:2054:warning: symbol value 'n' invalid for 
MTD_REDBOOT_DIRECTORY_BLOCK
   .config:2180:warning: symbol value 'n' invalid for KCOV_IRQ_AREA_SIZE
   .config:2304:warning: symbol value 'n' invalid for SND_HDA_PREALLOC_SIZE
   .config:2510:warning: symbol value 'n' invalid for PANEL_LCD_BWIDTH
   .config:2523:warning: symbol value 'n' invalid for DRM_XE_TIMESLICE_MAX
   .config:2770:warning: symbol value 'n' invalid for PANEL_PARPORT
   .config:2864:warning: symbol value 'n' invalid for 
SND_SOC_SOF_DEBUG_IPC_FLOOD_TEST_NUM
   .config:2868:warning: symbol value 'n' invalid for NOUVEAU_DEBUG_DEFAULT
   .config:3081:warning: symbol value 'n' invalid for KCSAN_REPORT_ONCE_IN_MS
   .config:3189:warning: symbol value 'n' invalid for KCSAN_UDELAY_INTERRUPT
   .config:3214:warning: symbol value 'n' invalid for PANEL_LCD_PIN_BL
   .config:3227:warning: symbol value 'n' invalid for PSTORE_BLK_CONSOLE_SIZE
   .config:3237:warning: symbol value 'n' invalid for 
DEBUG_OBJECTS_ENABLE_DEFAULT
   .config:3244:warning: symbol value 'n' invalid for INITRAMFS_ROOT_GID
   .config:3335:warning: symbol value 'n' invalid for 
FTRACE_RECORD_RECURSION_SIZE
   .config:3362:warning: symbol value 'n' invalid for ATM_FORE200E_T

Re: [PATCH v6 1/5] drm: Stop using `select ACPI_VIDEO` in all drivers

2024-02-16 Thread kernel test robot
Hi Mario,

kernel test robot noticed the following build warnings:

[auto build test WARNING on drm-misc/drm-misc-next]
[also build test WARNING on drm-intel/for-linux-next-fixes drm-tip/drm-tip 
linus/master v6.8-rc4 next-20240216]
[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/Mario-Limonciello/drm-Stop-using-select-ACPI_VIDEO-in-all-drivers/20240215-055936
base:   git://anongit.freedesktop.org/drm/drm-misc drm-misc-next
patch link:
https://lore.kernel.org/r/20240214215756.6530-2-mario.limonciello%40amd.com
patch subject: [PATCH v6 1/5] drm: Stop using `select ACPI_VIDEO` in all drivers
config: alpha-kismet-CONFIG_FB_BACKLIGHT-CONFIG_FB_NVIDIA-0-0 
(https://download.01.org/0day-ci/archive/20240216/202402161633.zhmogq2g-...@intel.com/config)
reproduce: 
(https://download.01.org/0day-ci/archive/20240216/202402161633.zhmogq2g-...@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 
| Closes: 
https://lore.kernel.org/oe-kbuild-all/202402161633.zhmogq2g-...@intel.com/

kismet warnings: (new ones prefixed by >>)
>> kismet: WARNING: unmet direct dependencies detected for FB_BACKLIGHT when 
>> selected by FB_NVIDIA
   .config:98:warning: symbol value 'n' invalid for SERIAL_AR933X_NR_UARTS
   .config:208:warning: symbol value 'n' invalid for 
USB_GADGET_STORAGE_NUM_BUFFERS
   .config:244:warning: symbol value 'n' invalid for SATA_MOBILE_LPM_POLICY
   .config:345:warning: symbol value 'n' invalid for PSTORE_BLK_MAX_REASON
   .config:427:warning: symbol value 'n' invalid for AIC79XX_DEBUG_MASK
   .config:432:warning: symbol value 'n' invalid for KFENCE_SAMPLE_INTERVAL
   .config:620:warning: symbol value 'n' invalid for DRM_XE_JOB_TIMEOUT_MIN
   .config:652:warning: symbol value 'n' invalid for CRYPTO_DEV_QCE_SW_MAX_LEN
   .config:687:warning: symbol value 'n' invalid for PANEL_LCD_PIN_E
   .config:757:warning: symbol value 'n' invalid for PANEL_LCD_CHARSET
   .config:800:warning: symbol value 'n' invalid for SND_AC97_POWER_SAVE_DEFAULT
   .config:848:warning: symbol value 'n' invalid for MAGIC_SYSRQ_DEFAULT_ENABLE
   .config:853:warning: symbol value 'n' invalid for AIC79XX_CMDS_PER_DEVICE
   .config:865:warning: symbol value 'n' invalid for 
DRM_I915_MAX_REQUEST_BUSYWAIT
   .config:896:warning: symbol value 'n' invalid for SND_AT73C213_TARGET_BITRATE
   .config:907:warning: symbol value 'n' invalid for DRM_XE_PREEMPT_TIMEOUT_MIN
   .config:913:warning: symbol value 'n' invalid for PANEL_LCD_PIN_SDA
   .config:915:warning: symbol value 'n' invalid for NET_EMATCH_STACK
   .config:917:warning: symbol value 'n' invalid for VMCP_CMA_SIZE
   .config:1149:warning: symbol value 'n' invalid for RCU_CPU_STALL_TIMEOUT
   .config:1176:warning: symbol value 'n' invalid for MTDRAM_ERASE_SIZE
   .config:1282:warning: symbol value 'n' invalid for SERIAL_UARTLITE_NR_UARTS
   .config:1453:warning: symbol value 'n' invalid for LEGACY_PTY_COUNT
   .config:1591:warning: symbol value 'n' invalid for AIC7XXX_RESET_DELAY_MS
   .config:1592:warning: symbol value 'n' invalid for WATCHDOG_OPEN_TIMEOUT
   .config:1710:warning: symbol value 'n' invalid for AIC79XX_RESET_DELAY_MS
   .config:1757:warning: symbol value 'n' invalid for IBM_EMAC_POLL_WEIGHT
   .config:1891:warning: symbol value 'n' invalid for DRM_I915_STOP_TIMEOUT
   .config:2178:warning: symbol value 'n' invalid for RCU_FANOUT_LEAF
   .config:2192:warning: symbol value 'n' invalid for KCOV_IRQ_AREA_SIZE
   .config:2327:warning: symbol value 'n' invalid for DRM_XE_TIMESLICE_MAX
   .config:2328:warning: symbol value 'n' invalid for PANEL_LCD_BWIDTH
   .config:2378:warning: symbol value 'n' invalid for 
MTD_REDBOOT_DIRECTORY_BLOCK
   .config:2570:warning: symbol value 'n' invalid for PANEL_PARPORT
   .config:2655:warning: symbol value 'n' invalid for NOUVEAU_DEBUG_DEFAULT
   .config:2846:warning: symbol value 'n' invalid for KCSAN_REPORT_ONCE_IN_MS
   .config:2860:warning: symbol value 'n' invalid for 
SND_SOC_SOF_DEBUG_IPC_FLOOD_TEST_NUM
   .config:2934:warning: symbol value 'n' invalid for XEN_MEMORY_HOTPLUG_LIMIT
   .config:2944:warning: symbol value 'n' invalid for KCSAN_UDELAY_INTERRUPT
   .config:2969:warning: symbol value 'n' invalid for PANEL_LCD_PIN_BL
   .config:2995:warning: symbol value 'n' invalid for INITRAMFS_ROOT_GID
   .config:3101:warning: symbol value 'n' invalid for ATM_FORE200E_TX_RETRY
   .config:3142:warning: symbol value 'n' invalid for 
FB_OMAP2_DSS_MIN_FCK_PER_PCK
   .config:3223:warning: symbol value 'n' invalid for PSTORE_BLK_CONSOLE_SIZE
   .config:3344:warning: symbol value 'n' invalid for BOOKE_WDT_DEFAULT_TIMEOUT
   .config:3426:warning: symbol value 'n' invalid for KCSAN_UDELAY_TA

Re: [PATCH v6 1/5] drm: Stop using `select ACPI_VIDEO` in all drivers

2024-02-15 Thread kernel test robot
Hi Mario,

kernel test robot noticed the following build warnings:

[auto build test WARNING on drm-misc/drm-misc-next]
[also build test WARNING on drm-intel/for-linux-next-fixes drm-tip/drm-tip 
linus/master v6.8-rc4 next-20240215]
[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/Mario-Limonciello/drm-Stop-using-select-ACPI_VIDEO-in-all-drivers/20240215-055936
base:   git://anongit.freedesktop.org/drm/drm-misc drm-misc-next
patch link:
https://lore.kernel.org/r/20240214215756.6530-2-mario.limonciello%40amd.com
patch subject: [PATCH v6 1/5] drm: Stop using `select ACPI_VIDEO` in all drivers
config: alpha-kismet-CONFIG_FB_BACKLIGHT-CONFIG_FB_ATY128-0-0 
(https://download.01.org/0day-ci/archive/20240216/202402161205.v9d7iypg-...@intel.com/config)
reproduce: 
(https://download.01.org/0day-ci/archive/20240216/202402161205.v9d7iypg-...@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 
| Closes: 
https://lore.kernel.org/oe-kbuild-all/202402161205.v9d7iypg-...@intel.com/

kismet warnings: (new ones prefixed by >>)
>> kismet: WARNING: unmet direct dependencies detected for FB_BACKLIGHT when 
>> selected by FB_ATY128
   .config:233:warning: symbol value 'n' invalid for SATA_MOBILE_LPM_POLICY
   .config:335:warning: symbol value 'n' invalid for AIC79XX_DEBUG_MASK
   .config:336:warning: symbol value 'n' invalid for PSTORE_BLK_MAX_REASON
   .config:437:warning: symbol value 'n' invalid for KFENCE_SAMPLE_INTERVAL
   .config:511:warning: symbol value 'n' invalid for INPUT_MOUSEDEV_SCREEN_Y
   .config:613:warning: symbol value 'n' invalid for DRM_XE_JOB_TIMEOUT_MIN
   .config:620:warning: symbol value 'n' invalid for CRYPTO_DEV_QCE_SW_MAX_LEN
   .config:705:warning: symbol value 'n' invalid for AIC79XX_CMDS_PER_DEVICE
   .config:719:warning: symbol value 'n' invalid for PANEL_LCD_CHARSET
   .config:766:warning: symbol value 'n' invalid for XEN_MEMORY_HOTPLUG_LIMIT
   .config:774:warning: symbol value 'n' invalid for PANEL_LCD_PIN_SDA
   .config:791:warning: symbol value 'n' invalid for SND_AC97_POWER_SAVE_DEFAULT
   .config:825:warning: symbol value 'n' invalid for MAGIC_SYSRQ_DEFAULT_ENABLE
   .config:840:warning: symbol value 'n' invalid for 
DRM_I915_MAX_REQUEST_BUSYWAIT
   .config:871:warning: symbol value 'n' invalid for 
USB_GADGET_STORAGE_NUM_BUFFERS
   .config:875:warning: symbol value 'n' invalid for SND_AT73C213_TARGET_BITRATE
   .config:894:warning: symbol value 'n' invalid for DRM_XE_PREEMPT_TIMEOUT_MIN
   .config:903:warning: symbol value 'n' invalid for NET_EMATCH_STACK
   .config:905:warning: symbol value 'n' invalid for VMCP_CMA_SIZE
   .config:1160:warning: symbol value 'n' invalid for MTDRAM_ERASE_SIZE
   .config:1246:warning: symbol value 'n' invalid for SERIAL_UARTLITE_NR_UARTS
   .config:1287:warning: symbol value 'n' invalid for PANEL_LCD_PIN_E
   .config:1411:warning: symbol value 'n' invalid for LEGACY_PTY_COUNT
   .config:1517:warning: symbol value 'n' invalid for 
SERIAL_ALTERA_UART_BAUDRATE
   .config:1543:warning: symbol value 'n' invalid for WATCHDOG_OPEN_TIMEOUT
   .config:1547:warning: symbol value 'n' invalid for AIC7XXX_RESET_DELAY_MS
   .config:1739:warning: symbol value 'n' invalid for IBM_EMAC_POLL_WEIGHT
   .config:1833:warning: symbol value 'n' invalid for DRM_I915_STOP_TIMEOUT
   .config:1972:warning: symbol value 'n' invalid for KCOV_IRQ_AREA_SIZE
   .config:2263:warning: symbol value 'n' invalid for DRM_XE_TIMESLICE_MAX
   .config:2304:warning: symbol value 'n' invalid for PANEL_LCD_BWIDTH
   .config:2383:warning: symbol value 'n' invalid for AIC79XX_RESET_DELAY_MS
   .config:2500:warning: symbol value 'n' invalid for 
SND_SOC_SOF_DEBUG_IPC_FLOOD_TEST_NUM
   .config:2535:warning: symbol value 'n' invalid for PANEL_PARPORT
   .config:2622:warning: symbol value 'n' invalid for NOUVEAU_DEBUG_DEFAULT
   .config:2808:warning: symbol value 'n' invalid for KCSAN_REPORT_ONCE_IN_MS
   .config:2904:warning: symbol value 'n' invalid for PSTORE_BLK_CONSOLE_SIZE
   .config:2906:warning: symbol value 'n' invalid for KCSAN_UDELAY_INTERRUPT
   .config:2928:warning: symbol value 'n' invalid for PANEL_LCD_PIN_BL
   .config:2945:warning: symbol value 'n' invalid for 
DEBUG_OBJECTS_ENABLE_DEFAULT
   .config:2952:warning: symbol value 'n' invalid for INITRAMFS_ROOT_GID
   .config:3033:warning: symbol value 'n' invalid for 
MTD_REDBOOT_DIRECTORY_BLOCK
   .config:3058:warning: symbol value 'n' invalid for ATM_FORE200E_TX_RETRY
   .config:3075:warning: symbol value 'n' invalid for BOOKE_WDT_DEFAULT_TIMEOUT
   .config:3098:warning: symbol value 'n' invalid for 
FB_OMAP2_DSS_MIN_FCK_PER_PCK
   .config:3339:warning: symbol

Re: [PATCH 4/6] drm/i915/psr: Silence period and lfps half cycle

2024-02-15 Thread kernel test robot
Hi Jouni,

kernel test robot noticed the following build warnings:

[auto build test WARNING on drm-intel/for-linux-next]
[also build test WARNING on drm-tip/drm-tip next-20240215]
[cannot apply to drm-intel/for-linux-next-fixes drm/drm-next linus/master 
v6.8-rc4]
[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/Jouni-H-gander/drm-display-Add-missing-aux-less-alpm-wake-related-bits/20240215-185209
base:   git://anongit.freedesktop.org/drm-intel for-linux-next
patch link:
https://lore.kernel.org/r/20240215104934.2395239-5-jouni.hogander%40intel.com
patch subject: [PATCH 4/6] drm/i915/psr: Silence period and lfps half cycle
config: i386-buildonly-randconfig-004-20240215 
(https://download.01.org/0day-ci/archive/20240216/202402161056.o7ey8uvv-...@intel.com/config)
compiler: clang version 17.0.6 (https://github.com/llvm/llvm-project 
6009708b4367171ccdbf4b5905cb6a803753fe18)
reproduce (this is a W=1 build): 
(https://download.01.org/0day-ci/archive/20240216/202402161056.o7ey8uvv-...@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 
| Closes: 
https://lore.kernel.org/oe-kbuild-all/202402161056.o7ey8uvv-...@intel.com/

All warnings (new ones prefixed by >>):

>> drivers/gpu/drm/i915/display/intel_psr.c:1253:6: warning: variable 
>> 'silence_period' is uninitialized when used here [-Wuninitialized]
1253 | silence_period > 256 || silence_period < 0 ||
 | ^~
   drivers/gpu/drm/i915/display/intel_psr.c:1240:17: note: initialize the 
variable 'silence_period' to silence this warning
1240 | silence_period, lfps_half_cycle;
 |   ^
 |= 0
   1 warning generated.


vim +/silence_period +1253 drivers/gpu/drm/i915/display/intel_psr.c

  1234  
  1235  static int _lnl_compute_aux_less_alpm_params(struct intel_dp *intel_dp,
  1236   struct intel_crtc_state 
*crtc_state)
  1237  {
  1238  struct drm_i915_private *i915 = dp_to_i915(intel_dp);
  1239  int aux_less_wake_time, aux_less_wake_lines, 
switch_to_active_lines,
  1240  silence_period, lfps_half_cycle;
  1241  
  1242  aux_less_wake_time =
  1243  _lnl_compute_aux_less_wake_time(crtc_state->port_clock 
/ 1000);
  1244  aux_less_wake_lines = 
intel_usecs_to_scanlines(_state->hw.adjusted_mode,
  1245 
aux_less_wake_time);
  1246  
  1247  switch_to_active_lines =
  1248  intel_usecs_to_scanlines(
  1249  _state->hw.adjusted_mode,
  1250  
_lnl_compute_switch_to_active_time(crtc_state->port_clock / 1000));
  1251  
  1252  if (aux_less_wake_lines > 32 || switch_to_active_lines > 32 ||
> 1253  silence_period > 256 || silence_period < 0 ||
  1254  
!_lnl_get_silence_period_and_lfps_half_cycle(intel_dp->link_rate,
  1255   
_period,
  1256   
_half_cycle))
  1257  return false;
  1258  
  1259  if (i915->display.params.psr_safest_params) {
  1260  aux_less_wake_lines = 32;
  1261  switch_to_active_lines = 32;
  1262  }
  1263  
  1264  intel_dp->psr.alpm_parameters.aux_less_wake_lines = 
aux_less_wake_lines;
  1265  intel_dp->psr.alpm_parameters.switch_to_active_lines = 
switch_to_active_lines;
  1266  intel_dp->psr.alpm_parameters.silence_period_sym_clocks = 
silence_period;
  1267  intel_dp->psr.alpm_parameters.lfps_half_cycle_num_of_syms = 
lfps_half_cycle;
  1268  
  1269  return true;
  1270  }
  1271  

-- 
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki


Re: [PATCH v6 1/5] drm: Stop using `select ACPI_VIDEO` in all drivers

2024-02-15 Thread kernel test robot
Hi Mario,

kernel test robot noticed the following build errors:

[auto build test ERROR on drm-misc/drm-misc-next]
[also build test ERROR on drm-intel/for-linux-next-fixes drm-tip/drm-tip 
linus/master v6.8-rc4 next-20240215]
[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/Mario-Limonciello/drm-Stop-using-select-ACPI_VIDEO-in-all-drivers/20240215-055936
base:   git://anongit.freedesktop.org/drm/drm-misc drm-misc-next
patch link:
https://lore.kernel.org/r/20240214215756.6530-2-mario.limonciello%40amd.com
patch subject: [PATCH v6 1/5] drm: Stop using `select ACPI_VIDEO` in all drivers
config: nios2-randconfig-r061-20240215 
(https://download.01.org/0day-ci/archive/20240216/202402160847.fdgskgjp-...@intel.com/config)
compiler: nios2-linux-gcc (GCC) 13.2.0
reproduce (this is a W=1 build): 
(https://download.01.org/0day-ci/archive/20240216/202402160847.fdgskgjp-...@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 
| Closes: 
https://lore.kernel.org/oe-kbuild-all/202402160847.fdgskgjp-...@intel.com/

All errors (new ones prefixed by >>):

   nios2-linux-ld: drivers/video/fbdev/ssd1307fb.o: in function 
`ssd1307fb_remove':
   ssd1307fb.c:(.text+0x40c): undefined reference to 
`backlight_device_unregister'
>> ssd1307fb.c:(.text+0x40c): relocation truncated to fit: R_NIOS2_CALL26 
>> against `backlight_device_unregister'
   nios2-linux-ld: drivers/video/fbdev/ssd1307fb.o: in function 
`ssd1307fb_probe':
   ssd1307fb.c:(.text+0x1d98): undefined reference to 
`backlight_device_register'
>> ssd1307fb.c:(.text+0x1d98): relocation truncated to fit: R_NIOS2_CALL26 
>> against `backlight_device_register'

Kconfig warnings: (for reference only)
   WARNING: unmet direct dependencies detected for FB_BACKLIGHT
   Depends on [n]: HAS_IOMEM [=y] && FB [=y] && BACKLIGHT_CLASS_DEVICE [=n]
   Selected by [y]:
   - FB_SSD1307 [=y] && HAS_IOMEM [=y] && FB [=y] && I2C [=y] && (GPIOLIB [=y] 
|| COMPILE_TEST [=y])

-- 
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki


Re: [PATCH v6 1/5] drm: Stop using `select ACPI_VIDEO` in all drivers

2024-02-15 Thread kernel test robot
Hi Mario,

kernel test robot noticed the following build warnings:

[auto build test WARNING on drm-misc/drm-misc-next]
[also build test WARNING on drm-intel/for-linux-next-fixes drm-tip/drm-tip 
linus/master v6.8-rc4 next-20240215]
[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/Mario-Limonciello/drm-Stop-using-select-ACPI_VIDEO-in-all-drivers/20240215-055936
base:   git://anongit.freedesktop.org/drm/drm-misc drm-misc-next
patch link:
https://lore.kernel.org/r/20240214215756.6530-2-mario.limonciello%40amd.com
patch subject: [PATCH v6 1/5] drm: Stop using `select ACPI_VIDEO` in all drivers
config: alpha-kismet-CONFIG_FB_BACKLIGHT-CONFIG_FB_ATY-0-0 
(https://download.01.org/0day-ci/archive/20240216/202402160822.2b7vxnn3-...@intel.com/config)
reproduce: 
(https://download.01.org/0day-ci/archive/20240216/202402160822.2b7vxnn3-...@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 
| Closes: 
https://lore.kernel.org/oe-kbuild-all/202402160822.2b7vxnn3-...@intel.com/

kismet warnings: (new ones prefixed by >>)
>> kismet: WARNING: unmet direct dependencies detected for FB_BACKLIGHT when 
>> selected by FB_ATY
   .config:163:warning: symbol value 'n' invalid for 
USB_GADGET_STORAGE_NUM_BUFFERS
   .config:241:warning: symbol value 'n' invalid for SATA_MOBILE_LPM_POLICY
   .config:343:warning: symbol value 'n' invalid for PSTORE_BLK_MAX_REASON
   .config:432:warning: symbol value 'n' invalid for KFENCE_SAMPLE_INTERVAL
   .config:572:warning: symbol value 'n' invalid for PANEL_LCD_PIN_E
   .config:596:warning: symbol value 'n' invalid for AIC79XX_DEBUG_MASK
   .config:616:warning: symbol value 'n' invalid for DRM_XE_JOB_TIMEOUT_MIN
   .config:629:warning: symbol value 'n' invalid for CRYPTO_DEV_QCE_SW_MAX_LEN
   .config:738:warning: symbol value 'n' invalid for PANEL_LCD_CHARSET
   .config:794:warning: symbol value 'n' invalid for SND_AC97_POWER_SAVE_DEFAULT
   .config:852:warning: symbol value 'n' invalid for 
DRM_I915_MAX_REQUEST_BUSYWAIT
   .config:887:warning: symbol value 'n' invalid for SND_AT73C213_TARGET_BITRATE
   .config:902:warning: symbol value 'n' invalid for SERIAL_AR933X_NR_UARTS
   .config:903:warning: symbol value 'n' invalid for DRM_XE_PREEMPT_TIMEOUT_MIN
   .config:911:warning: symbol value 'n' invalid for NET_EMATCH_STACK
   .config:913:warning: symbol value 'n' invalid for VMCP_CMA_SIZE
   .config:986:warning: symbol value 'n' invalid for AIC79XX_CMDS_PER_DEVICE
   .config:1048:warning: symbol value 'n' invalid for PANEL_LCD_PIN_SDA
   .config:1170:warning: symbol value 'n' invalid for MTDRAM_ERASE_SIZE
   .config:1270:warning: symbol value 'n' invalid for SERIAL_UARTLITE_NR_UARTS
   .config:1434:warning: symbol value 'n' invalid for LEGACY_PTY_COUNT
   .config:1578:warning: symbol value 'n' invalid for AIC7XXX_RESET_DELAY_MS
   .config:1614:warning: symbol value 'n' invalid for AIC79XX_RESET_DELAY_MS
   .config:1753:warning: symbol value 'n' invalid for IBM_EMAC_POLL_WEIGHT
   .config:1867:warning: symbol value 'n' invalid for DRM_I915_STOP_TIMEOUT
   .config:2174:warning: symbol value 'n' invalid for RCU_FANOUT_LEAF
   .config:2220:warning: symbol value 'n' invalid for 
MTD_REDBOOT_DIRECTORY_BLOCK
   .config:2308:warning: symbol value 'n' invalid for DRM_XE_TIMESLICE_MAX
   .config:2320:warning: symbol value 'n' invalid for PANEL_LCD_BWIDTH
   .config:2339:warning: symbol value 'n' invalid for KCOV_IRQ_AREA_SIZE
   .config:2559:warning: symbol value 'n' invalid for PANEL_PARPORT
   .config:2646:warning: symbol value 'n' invalid for NOUVEAU_DEBUG_DEFAULT
   .config:2838:warning: symbol value 'n' invalid for KCSAN_REPORT_ONCE_IN_MS
   .config:2936:warning: symbol value 'n' invalid for KCSAN_UDELAY_INTERRUPT
   .config:2958:warning: symbol value 'n' invalid for PANEL_LCD_PIN_BL
   .config:2971:warning: symbol value 'n' invalid for 
SND_SOC_SOF_DEBUG_IPC_FLOOD_TEST_NUM
   .config:2976:warning: symbol value 'n' invalid for 
DEBUG_OBJECTS_ENABLE_DEFAULT
   .config:2984:warning: symbol value 'n' invalid for INITRAMFS_ROOT_GID
   .config:3090:warning: symbol value 'n' invalid for ATM_FORE200E_TX_RETRY
   .config:3124:warning: symbol value 'n' invalid for 
FB_OMAP2_DSS_MIN_FCK_PER_PCK
   .config:3301:warning: symbol value 'n' invalid for PSTORE_BLK_CONSOLE_SIZE
   .config:3393:warning: symbol value 'n' invalid for 
FTRACE_RECORD_RECURSION_SIZE
   .config:3415:warning: symbol value 'n' invalid for KCSAN_UDELAY_TASK
   .config:3448:warning: symbol value 'n' invalid for BOOKE_WDT_DEFAULT_TIMEOUT
   .config:3468:warning: symbol value 'n' invalid for MMC_BLOCK_MINORS
   .config:3472:warning: symbol value 'n' invalid for INET_TABLE_PERTUR

Re: [PATCH 2/2] i915/pmu: Cleanup pending events on unbind

2024-02-15 Thread kernel test robot
Hi Umesh,

kernel test robot noticed the following build warnings:

[auto build test WARNING on drm-intel/for-linux-next]
[also build test WARNING on drm-intel/for-linux-next-fixes drm-tip/drm-tip 
linus/master v6.8-rc4 next-20240215]
[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/Umesh-Nerlige-Ramappa/i915-pmu-Add-pmu_teardown-helper/20240214-020605
base:   git://anongit.freedesktop.org/drm-intel for-linux-next
patch link:
https://lore.kernel.org/r/20240213180302.47266-3-umesh.nerlige.ramappa%40intel.com
patch subject: [PATCH 2/2] i915/pmu: Cleanup pending events on unbind
config: x86_64-randconfig-121-20240214 
(https://download.01.org/0day-ci/archive/20240216/202402160519.aioeunoj-...@intel.com/config)
compiler: gcc-12 (Debian 12.2.0-14) 12.2.0
reproduce (this is a W=1 build): 
(https://download.01.org/0day-ci/archive/20240216/202402160519.aioeunoj-...@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 
| Closes: 
https://lore.kernel.org/oe-kbuild-all/202402160519.aioeunoj-...@intel.com/

sparse warnings: (new ones prefixed by >>)
>> drivers/gpu/drm/i915/i915_pmu.c:1405:44: sparse: sparse: incorrect type in 
>> initializer (different address spaces) @@ expected struct file *file @@  
>>got struct file [noderef] __rcu * @@
   drivers/gpu/drm/i915/i915_pmu.c:1405:44: sparse: expected struct file 
*file
   drivers/gpu/drm/i915/i915_pmu.c:1405:44: sparse: got struct file 
[noderef] __rcu *
   drivers/gpu/drm/i915/i915_pmu.c: note: in included file (through 
include/linux/preempt.h, include/linux/spinlock.h, include/linux/fdtable.h):
   include/linux/list.h:83:21: sparse: sparse: self-comparison always evaluates 
to true

vim +1405 drivers/gpu/drm/i915/i915_pmu.c

  1385  
  1386  static void close_event_file(struct perf_event *event)
  1387  {
  1388  unsigned int max_open_fds, fd;
  1389  struct files_struct *files;
  1390  struct task_struct *task;
  1391  struct fdtable *fdt;
  1392  
  1393  task = event->owner;
  1394  if (!task)
  1395  return;
  1396  
  1397  files = task->files;
  1398  if (!files)
  1399  return;
  1400  
  1401  spin_lock(>file_lock);
  1402  fdt = files_fdtable(files);
  1403  max_open_fds = __open_files(fdt);
  1404  for (fd = 0; fd < max_open_fds; fd++) {
> 1405  struct file *file = fdt->fd[fd];
  1406  
  1407  if (!file || file->private_data != event)
  1408  continue;
  1409  
  1410  rcu_assign_pointer(fdt->fd[fd], NULL);
  1411  __clear_bit(fd, fdt->open_fds);
  1412  __clear_bit(fd / BITS_PER_LONG, fdt->full_fds_bits);
  1413  if (fd < files->next_fd)
  1414  files->next_fd = fd;
  1415  filp_close(file, files);
  1416  break;
  1417  }
  1418  spin_unlock(>file_lock);
  1419  }
  1420  

-- 
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki


Re: [PATCH v6 1/5] drm: Stop using `select ACPI_VIDEO` in all drivers

2024-02-15 Thread kernel test robot
Hi Mario,

kernel test robot noticed the following build warnings:

[auto build test WARNING on drm-misc/drm-misc-next]
[also build test WARNING on drm-intel/for-linux-next-fixes drm-tip/drm-tip 
linus/master v6.8-rc4 next-20240215]
[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/Mario-Limonciello/drm-Stop-using-select-ACPI_VIDEO-in-all-drivers/20240215-055936
base:   git://anongit.freedesktop.org/drm/drm-misc drm-misc-next
patch link:
https://lore.kernel.org/r/20240214215756.6530-2-mario.limonciello%40amd.com
patch subject: [PATCH v6 1/5] drm: Stop using `select ACPI_VIDEO` in all drivers
config: alpha-kismet-CONFIG_FB_BACKLIGHT-CONFIG_FB_ATMEL-0-0 
(https://download.01.org/0day-ci/archive/20240216/202402160459.dyhkpajy-...@intel.com/config)
reproduce: 
(https://download.01.org/0day-ci/archive/20240216/202402160459.dyhkpajy-...@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 
| Closes: 
https://lore.kernel.org/oe-kbuild-all/202402160459.dyhkpajy-...@intel.com/

kismet warnings: (new ones prefixed by >>)
>> kismet: WARNING: unmet direct dependencies detected for FB_BACKLIGHT when 
>> selected by FB_ATMEL
   .config:166:warning: symbol value 'n' invalid for RAPIDIO_DISC_TIMEOUT
   .config:190:warning: symbol value 'n' invalid for FAT_DEFAULT_CODEPAGE
   .config:241:warning: symbol value 'n' invalid for SATA_MOBILE_LPM_POLICY
   .config:335:warning: symbol value 'n' invalid for AIC79XX_DEBUG_MASK
   .config:344:warning: symbol value 'n' invalid for PSTORE_BLK_MAX_REASON
   .config:426:warning: symbol value 'n' invalid for KFENCE_SAMPLE_INTERVAL
   .config:596:warning: symbol value 'n' invalid for DRM_XE_JOB_TIMEOUT_MIN
   .config:618:warning: symbol value 'n' invalid for CRYPTO_DEV_QCE_SW_MAX_LEN
   .config:712:warning: symbol value 'n' invalid for PANEL_LCD_CHARSET
   .config:752:warning: symbol value 'n' invalid for AIC79XX_CMDS_PER_DEVICE
   .config:770:warning: symbol value 'n' invalid for SND_AC97_POWER_SAVE_DEFAULT
   .config:790:warning: symbol value 'n' invalid for PANEL_LCD_PIN_SDA
   .config:810:warning: symbol value 'n' invalid for MAGIC_SYSRQ_DEFAULT_ENABLE
   .config:823:warning: symbol value 'n' invalid for 
DRM_I915_MAX_REQUEST_BUSYWAIT
   .config:860:warning: symbol value 'n' invalid for SND_AT73C213_TARGET_BITRATE
   .config:875:warning: symbol value 'n' invalid for DRM_XE_PREEMPT_TIMEOUT_MIN
   .config:884:warning: symbol value 'n' invalid for NET_EMATCH_STACK
   .config:886:warning: symbol value 'n' invalid for VMCP_CMA_SIZE
   .config:917:warning: symbol value 'n' invalid for INPUT_MOUSEDEV_SCREEN_Y
   .config:1139:warning: symbol value 'n' invalid for MTDRAM_ERASE_SIZE
   .config:1233:warning: symbol value 'n' invalid for SERIAL_UARTLITE_NR_UARTS
   .config:1245:warning: symbol value 'n' invalid for 
USB_GADGET_STORAGE_NUM_BUFFERS
   .config:1403:warning: symbol value 'n' invalid for LEGACY_PTY_COUNT
   .config:1541:warning: symbol value 'n' invalid for WATCHDOG_OPEN_TIMEOUT
   .config:1550:warning: symbol value 'n' invalid for AIC7XXX_RESET_DELAY_MS
   .config:1686:warning: symbol value 'n' invalid for PANEL_LCD_PIN_E
   .config:1717:warning: symbol value 'n' invalid for IBM_EMAC_POLL_WEIGHT
   .config:1805:warning: symbol value 'n' invalid for DRM_I915_STOP_TIMEOUT
   .config:1972:warning: symbol value 'n' invalid for KCOV_IRQ_AREA_SIZE
   .config:2126:warning: symbol value 'n' invalid for RCU_FANOUT_LEAF
   .config:2231:warning: symbol value 'n' invalid for DRM_XE_TIMESLICE_MAX
   .config:2274:warning: symbol value 'n' invalid for PANEL_LCD_BWIDTH
   .config:2465:warning: symbol value 'n' invalid for 
SND_SOC_SOF_DEBUG_IPC_FLOOD_TEST_NUM
   .config:2585:warning: symbol value 'n' invalid for NOUVEAU_DEBUG_DEFAULT
   .config:2775:warning: symbol value 'n' invalid for KCSAN_REPORT_ONCE_IN_MS
   .config:2836:warning: symbol value 'n' invalid for AIC79XX_RESET_DELAY_MS
   .config:2873:warning: symbol value 'n' invalid for KCSAN_UDELAY_INTERRUPT
   .config:2887:warning: symbol value 'n' invalid for PSTORE_BLK_CONSOLE_SIZE
   .config:2896:warning: symbol value 'n' invalid for PANEL_LCD_PIN_BL
   .config:2920:warning: symbol value 'n' invalid for INITRAMFS_ROOT_GID
   .config:3025:warning: symbol value 'n' invalid for ATM_FORE200E_TX_RETRY
   .config:3062:warning: symbol value 'n' invalid for 
FB_OMAP2_DSS_MIN_FCK_PER_PCK
   .config:3074:warning: symbol value 'n' invalid for BOOKE_WDT_DEFAULT_TIMEOUT
   .config:3302:warning: symbol value 'n' invalid for KCSAN_UDELAY_TASK
   .config:3394:warning: symbol value 'n' invalid for 
MTD_REDBOOT_DIRECTORY_BLOCK
   .config:3401:warning: symbol value 'n' invalid for MMC_BLOCK_MINO

Re: [PATCH v6 1/5] drm: Stop using `select ACPI_VIDEO` in all drivers

2024-02-15 Thread kernel test robot
Hi Mario,

kernel test robot noticed the following build errors:

[auto build test ERROR on drm-misc/drm-misc-next]
[also build test ERROR on drm-intel/for-linux-next-fixes drm-tip/drm-tip 
linus/master v6.8-rc4 next-20240215]
[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/Mario-Limonciello/drm-Stop-using-select-ACPI_VIDEO-in-all-drivers/20240215-055936
base:   git://anongit.freedesktop.org/drm/drm-misc drm-misc-next
patch link:
https://lore.kernel.org/r/20240214215756.6530-2-mario.limonciello%40amd.com
patch subject: [PATCH v6 1/5] drm: Stop using `select ACPI_VIDEO` in all drivers
config: openrisc-randconfig-r064-20240215 
(https://download.01.org/0day-ci/archive/20240216/202402160446.yalmybpi-...@intel.com/config)
compiler: or1k-linux-gcc (GCC) 13.2.0
reproduce (this is a W=1 build): 
(https://download.01.org/0day-ci/archive/20240216/202402160446.yalmybpi-...@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 
| Closes: 
https://lore.kernel.org/oe-kbuild-all/202402160446.yalmybpi-...@intel.com/

All errors (new ones prefixed by >>):

   or1k-linux-ld: drivers/video/fbdev/nvidia/nv_backlight.o: in function 
`nvidia_bl_init':
>> nv_backlight.c:(.text+0x26c): undefined reference to 
>> `backlight_device_register'
>> nv_backlight.c:(.text+0x26c): relocation truncated to fit: 
>> R_OR1K_INSN_REL_26 against undefined symbol `backlight_device_register'
   or1k-linux-ld: drivers/video/fbdev/nvidia/nv_backlight.o: in function 
`nvidia_bl_exit':
>> nv_backlight.c:(.text+0x32c): undefined reference to 
>> `backlight_device_unregister'
>> nv_backlight.c:(.text+0x32c): relocation truncated to fit: 
>> R_OR1K_INSN_REL_26 against undefined symbol `backlight_device_unregister'
   or1k-linux-ld: drivers/video/fbdev/aty/aty128fb.o: in function 
`aty128_remove':
>> aty128fb.c:(.text+0x14c): undefined reference to 
>> `backlight_device_unregister'
>> aty128fb.c:(.text+0x14c): relocation truncated to fit: R_OR1K_INSN_REL_26 
>> against undefined symbol `backlight_device_unregister'
   or1k-linux-ld: drivers/video/fbdev/aty/aty128fb.o: in function `aty128_init':
>> aty128fb.c:(.text.unlikely+0x5bc): undefined reference to 
>> `backlight_device_register'
>> aty128fb.c:(.text.unlikely+0x5bc): relocation truncated to fit: 
>> R_OR1K_INSN_REL_26 against undefined symbol `backlight_device_register'
   or1k-linux-ld: drivers/auxdisplay/ht16k33.o: in function 
`ht16k33_fbdev_probe':
>> ht16k33.c:(.text+0x17f4): undefined reference to 
>> `devm_backlight_device_register'
>> ht16k33.c:(.text+0x17f4): relocation truncated to fit: R_OR1K_INSN_REL_26 
>> against undefined symbol `devm_backlight_device_register'

Kconfig warnings: (for reference only)
   WARNING: unmet direct dependencies detected for FB_BACKLIGHT
   Depends on [n]: HAS_IOMEM [=y] && FB [=y] && BACKLIGHT_CLASS_DEVICE [=n]
   Selected by [y]:
   - HT16K33 [=y] && AUXDISPLAY [=y] && FB [=y] && I2C [=y] && INPUT [=y]
   - FB_ATMEL [=y] && FB [=y] && OF [=y] && HAVE_CLK [=y] && HAS_IOMEM [=y] && 
(HAVE_FB_ATMEL [=n] || COMPILE_TEST [=y])
   - FB_NVIDIA [=y] && HAS_IOMEM [=y] && FB [=y] && PCI [=y] && 
FB_NVIDIA_BACKLIGHT [=y]
   - FB_ATY128 [=y] && HAS_IOMEM [=y] && FB [=y] && PCI [=y] && 
FB_ATY128_BACKLIGHT [=y]

-- 
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki


Re: [PATCH 2/2] i915/pmu: Cleanup pending events on unbind

2024-02-14 Thread kernel test robot
Hi Umesh,

kernel test robot noticed the following build warnings:

[auto build test WARNING on drm-intel/for-linux-next]
[also build test WARNING on drm-intel/for-linux-next-fixes drm-tip/drm-tip 
linus/master v6.8-rc4 next-20240214]
[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/Umesh-Nerlige-Ramappa/i915-pmu-Add-pmu_teardown-helper/20240214-020605
base:   git://anongit.freedesktop.org/drm-intel for-linux-next
patch link:
https://lore.kernel.org/r/20240213180302.47266-3-umesh.nerlige.ramappa%40intel.com
patch subject: [PATCH 2/2] i915/pmu: Cleanup pending events on unbind
config: x86_64-randconfig-121-20240214 
(https://download.01.org/0day-ci/archive/20240215/202402151001.pziuj91o-...@intel.com/config)
compiler: gcc-12 (Debian 12.2.0-14) 12.2.0
reproduce (this is a W=1 build): 
(https://download.01.org/0day-ci/archive/20240215/202402151001.pziuj91o-...@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 
| Closes: 
https://lore.kernel.org/oe-kbuild-all/202402151001.pziuj91o-...@intel.com/

sparse warnings: (new ones prefixed by >>)
>> drivers/gpu/drm/i915/i915_pmu.c:1405:44: sparse: sparse: incorrect type in 
>> initializer (different address spaces) @@ expected struct file *file @@  
>>got struct file [noderef] __rcu * @@
   drivers/gpu/drm/i915/i915_pmu.c:1405:44: sparse: expected struct file 
*file
   drivers/gpu/drm/i915/i915_pmu.c:1405:44: sparse: got struct file 
[noderef] __rcu *
   drivers/gpu/drm/i915/i915_pmu.c: note: in included file (through 
include/linux/preempt.h, include/linux/spinlock.h, include/linux/fdtable.h):
   include/linux/list.h:83:21: sparse: sparse: self-comparison always evaluates 
to true

vim +1405 drivers/gpu/drm/i915/i915_pmu.c

  1385  
  1386  static void close_event_file(struct perf_event *event)
  1387  {
  1388  unsigned int max_open_fds, fd;
  1389  struct files_struct *files;
  1390  struct task_struct *task;
  1391  struct fdtable *fdt;
  1392  
  1393  task = event->owner;
  1394  if (!task)
  1395  return;
  1396  
  1397  files = task->files;
  1398  if (!files)
  1399  return;
  1400  
  1401  spin_lock(>file_lock);
  1402  fdt = files_fdtable(files);
  1403  max_open_fds = __open_files(fdt);
  1404  for (fd = 0; fd < max_open_fds; fd++) {
> 1405  struct file *file = fdt->fd[fd];
  1406  
  1407  if (!file || file->private_data != event)
  1408  continue;
  1409  
  1410  rcu_assign_pointer(fdt->fd[fd], NULL);
  1411  __clear_bit(fd, fdt->open_fds);
  1412  __clear_bit(fd / BITS_PER_LONG, fdt->full_fds_bits);
  1413  if (fd < files->next_fd)
  1414  files->next_fd = fd;
  1415  filp_close(file, files);
  1416  break;
  1417  }
  1418  spin_unlock(>file_lock);
  1419  }
  1420  

-- 
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki


Re: [PATCH 01/28] [NOT FOR REVIEW] drm: color pipeline base work

2024-02-13 Thread kernel test robot
Hi Uma,

kernel test robot noticed the following build warnings:

[auto build test WARNING on drm-misc/drm-misc-next]
[also build test WARNING on drm/drm-next next-20240213]
[cannot apply to drm-intel/for-linux-next drm-intel/for-linux-next-fixes 
linus/master v6.8-rc4]
[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/Uma-Shankar/drm-color-pipeline-base-work/20240213-144544
base:   git://anongit.freedesktop.org/drm/drm-misc drm-misc-next
patch link:
https://lore.kernel.org/r/20240213064835.139464-2-uma.shankar%40intel.com
patch subject: [PATCH 01/28] [NOT FOR REVIEW] drm: color pipeline base work
config: x86_64-allyesconfig 
(https://download.01.org/0day-ci/archive/20240214/202402141056.lzcslaot-...@intel.com/config)
compiler: clang version 17.0.6 (https://github.com/llvm/llvm-project 
6009708b4367171ccdbf4b5905cb6a803753fe18)
reproduce (this is a W=1 build): 
(https://download.01.org/0day-ci/archive/20240214/202402141056.lzcslaot-...@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 
| Closes: 
https://lore.kernel.org/oe-kbuild-all/202402141056.lzcslaot-...@intel.com/

All warnings (new ones prefixed by >>):

>> drivers/gpu/drm/tests/drm_fixp_test.c:11:59: warning: overflow in 
>> expression; result is 9223372036854775807 with type 'long long' 
>> [-Winteger-overflow]
  11 | KUNIT_EXPECT_EQ(test, 0x7fffll, ((1LL << 63) - 
1));
 |  ^
   1 warning generated.
--
>> drivers/gpu/drm/vkms/vkms_composer.c:95:5: warning: no previous prototype 
>> for function 'lerp_u16' [-Wmissing-prototypes]
  95 | u16 lerp_u16(u16 a, u16 b, s64 t)
 | ^
   drivers/gpu/drm/vkms/vkms_composer.c:95:1: note: declare 'static' if the 
function is not intended to be used outside of this translation unit
  95 | u16 lerp_u16(u16 a, u16 b, s64 t)
 | ^
 | static 
>> drivers/gpu/drm/vkms/vkms_composer.c:105:5: warning: no previous prototype 
>> for function 'get_lut_index' [-Wmissing-prototypes]
 105 | s64 get_lut_index(const struct vkms_color_lut *lut, u16 
channel_value)
 | ^
   drivers/gpu/drm/vkms/vkms_composer.c:105:1: note: declare 'static' if the 
function is not intended to be used outside of this translation unit
 105 | s64 get_lut_index(const struct vkms_color_lut *lut, u16 
channel_value)
 | ^
 | static 
>> drivers/gpu/drm/vkms/vkms_composer.c:167:6: warning: no previous prototype 
>> for function 'apply_3x4_matrix' [-Wmissing-prototypes]
 167 | void apply_3x4_matrix(struct pixel_argb_s32 *pixel, const struct 
drm_color_ctm_3x4 *matrix)
 |  ^
   drivers/gpu/drm/vkms/vkms_composer.c:167:1: note: declare 'static' if the 
function is not intended to be used outside of this translation unit
 167 | void apply_3x4_matrix(struct pixel_argb_s32 *pixel, const struct 
drm_color_ctm_3x4 *matrix)
 | ^
 | static 
   3 warnings generated.
--
>> drivers/gpu/drm/vkms/vkms_colorop.c:11:1: warning: 'const' type qualifier on 
>> return type has no effect [-Wignored-qualifiers]
  11 | const int vkms_initialize_tf_pipeline(struct drm_plane *plane, 
struct drm_prop_enum_list *list)
 | ^
>> drivers/gpu/drm/vkms/vkms_colorop.c:11:11: warning: no previous prototype 
>> for function 'vkms_initialize_tf_pipeline' [-Wmissing-prototypes]
  11 | const int vkms_initialize_tf_pipeline(struct drm_plane *plane, 
struct drm_prop_enum_list *list)
 |   ^
   drivers/gpu/drm/vkms/vkms_colorop.c:11:7: note: declare 'static' if the 
function is not intended to be used outside of this translation unit
  11 | const int vkms_initialize_tf_pipeline(struct drm_plane *plane, 
struct drm_prop_enum_list *list)
 |   ^
 | static 
>> drivers/gpu/drm/vkms/vkms_colorop.c:80:5: warning: no previous prototype for 
>> function 'vkms_initialize_colorops' [-Wmissing-prototypes]
  80 | int vkms_initialize_colorops(struct drm_plane *plane)
 | ^
   drivers/gpu/drm/vkms/vkms_colorop.c:80:1: note: declare 'static' if the 
function is not intended to be used outside of this translation unit
  80 | int vkms_initialize_colorops(struct drm_plane *plane)
 | ^
 | static 
   3 warnings generated.


vim +11 drivers/gpu/drm/tests/drm_fixp_test.c

 8  
 9  static void drm_test_sm2fixp(struct kunit *test)
10  {
  > 11  KUNIT_EXPECT_EQ(test, 0x7fffll, ((1LL << 63) - 1));
12  
13  /* 1 */
14

Re: [PATCH 01/28] [NOT FOR REVIEW] drm: color pipeline base work

2024-02-13 Thread kernel test robot
Hi Uma,

kernel test robot noticed the following build warnings:

[auto build test WARNING on drm-misc/drm-misc-next]
[also build test WARNING on drm/drm-next next-20240213]
[cannot apply to drm-intel/for-linux-next drm-intel/for-linux-next-fixes 
linus/master v6.8-rc4]
[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/Uma-Shankar/drm-color-pipeline-base-work/20240213-144544
base:   git://anongit.freedesktop.org/drm/drm-misc drm-misc-next
patch link:
https://lore.kernel.org/r/20240213064835.139464-2-uma.shankar%40intel.com
patch subject: [PATCH 01/28] [NOT FOR REVIEW] drm: color pipeline base work
config: x86_64-defconfig 
(https://download.01.org/0day-ci/archive/20240214/202402140432.nufiowye-...@intel.com/config)
compiler: gcc-11 (Debian 11.3.0-12) 11.3.0
reproduce (this is a W=1 build): 
(https://download.01.org/0day-ci/archive/20240214/202402140432.nufiowye-...@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 
| Closes: 
https://lore.kernel.org/oe-kbuild-all/202402140432.nufiowye-...@intel.com/

All warnings (new ones prefixed by >>):

>> drivers/gpu/drm/drm_colorop.c:268: warning: Function parameter or struct 
>> member 'type' not described in 'drm_get_colorop_curve_1d_type_name'
   drivers/gpu/drm/drm_colorop.c:268: warning: Excess function parameter 
'range' description in 'drm_get_colorop_curve_1d_type_name'


vim +268 drivers/gpu/drm/drm_colorop.c

   259  
   260  /**
   261   * drm_get_colorop_curve_1d_type_name - return a string for 1D curve 
type
   262   * @range: 1d curve type to compute name of
   263   *
   264   * In contrast to the other drm_get_*_name functions this one here 
returns a
   265   * const pointer and hence is threadsafe.
   266   */
   267  const char *drm_get_colorop_curve_1d_type_name(enum 
drm_colorop_curve_1d_type type)
 > 268  {
   269  if (WARN_ON(type >= ARRAY_SIZE(colorop_curve_1d_type_name)))
   270  return "unknown";
   271  
   272  return colorop_curve_1d_type_name[type];
   273  }
   274  

-- 
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki


Re: [PATCH 4/5] drm/xe/hdcp: Enable HDCP for XE

2024-02-09 Thread kernel test robot
Hi Suraj,

kernel test robot noticed the following build warnings:

[auto build test WARNING on drm-xe/drm-xe-next]
[also build test WARNING on drm-tip/drm-tip]
[cannot apply to drm-intel/for-linux-next drm-intel/for-linux-next-fixes 
linus/master v6.8-rc3 next-20240209]
[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/Suraj-Kandpal/drm-i915-hdcp-Move-intel_hdcp_gsc_message-def-away-from-header-file/20240209-181915
base:   https://gitlab.freedesktop.org/drm/xe/kernel.git drm-xe-next
patch link:
https://lore.kernel.org/r/20240209101412.1326176-5-suraj.kandpal%40intel.com
patch subject: [PATCH 4/5] drm/xe/hdcp: Enable HDCP for XE
config: loongarch-allmodconfig 
(https://download.01.org/0day-ci/archive/20240210/202402100132.xip3zz5i-...@intel.com/config)
compiler: loongarch64-linux-gcc (GCC) 13.2.0
reproduce (this is a W=1 build): 
(https://download.01.org/0day-ci/archive/20240210/202402100132.xip3zz5i-...@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 
| Closes: 
https://lore.kernel.org/oe-kbuild-all/202402100132.xip3zz5i-...@intel.com/

All warnings (new ones prefixed by >>):

>> drivers/gpu/drm/xe/xe_gsc_submit.c:50: warning: expecting prototype for 
>> xe_gsc_get_host_session_id(). Prototype was for 
>> xe_gsc_create_host_session_id() instead


vim +50 drivers/gpu/drm/xe/xe_gsc_submit.c

42  
43  /**
44   * xe_gsc_get_host_session_id - Creates a random 64 bit host_session id 
with
45   * bits 56-63 masked.
46   *
47   * Returns: random host_session_id which can be used to send messages 
to gsc cs
48   */
49  u64 xe_gsc_create_host_session_id(void)
  > 50  {
51  u64 host_session_id;
52  
53  get_random_bytes(_session_id, sizeof(u64));
54  host_session_id &= ~HOST_SESSION_CLIENT_MASK;
55  return host_session_id;
56  }
57  

-- 
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki


Re: [PATCH 2/3] drm/xe/hdcp: Enable HDCP for XE

2024-02-02 Thread kernel test robot
Hi Suraj,

kernel test robot noticed the following build warnings:

[auto build test WARNING on drm-intel/for-linux-next]
[also build test WARNING on drm-intel/for-linux-next-fixes drm-xe/drm-xe-next 
drm-tip/drm-tip linus/master v6.8-rc2 next-20240202]
[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/Suraj-Kandpal/drm-i915-hdcp-Move-intel_hdcp_gsc_message-def-away-from-header-file/20240202-164840
base:   git://anongit.freedesktop.org/drm-intel for-linux-next
patch link:
https://lore.kernel.org/r/20240202083737.1088306-3-suraj.kandpal%40intel.com
patch subject: [PATCH 2/3] drm/xe/hdcp: Enable HDCP for XE
config: s390-allmodconfig 
(https://download.01.org/0day-ci/archive/20240203/202402030852.ssijmp2s-...@intel.com/config)
compiler: clang version 19.0.0git (https://github.com/llvm/llvm-project 
7dd790db8b77c4a833c06632e903dc4f13877a64)
reproduce (this is a W=1 build): 
(https://download.01.org/0day-ci/archive/20240203/202402030852.ssijmp2s-...@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 
| Closes: 
https://lore.kernel.org/oe-kbuild-all/202402030852.ssijmp2s-...@intel.com/

All warnings (new ones prefixed by >>):

   In file included from drivers/gpu/drm/xe/display/xe_hdcp_gsc.c:7:
   In file included from drivers/gpu/drm/xe/compat-i915-headers/i915_drv.h:15:
   In file included from 
drivers/gpu/drm/xe/compat-i915-headers/gem/i915_gem_object.h:11:
   In file included from drivers/gpu/drm/xe/xe_bo.h:11:
   In file included from drivers/gpu/drm/xe/xe_bo_types.h:9:
   In file included from include/linux/iosys-map.h:10:
   In file included from include/linux/io.h:13:
   In file included from arch/s390/include/asm/io.h:78:
   include/asm-generic/io.h:547:31: warning: performing pointer arithmetic on a 
null pointer has undefined behavior [-Wnull-pointer-arithmetic]
 547 | val = __raw_readb(PCI_IOBASE + addr);
 |   ~~ ^
   include/asm-generic/io.h:560:61: warning: performing pointer arithmetic on a 
null pointer has undefined behavior [-Wnull-pointer-arithmetic]
 560 | val = __le16_to_cpu((__le16 __force)__raw_readw(PCI_IOBASE + 
addr));
 | ~~ ^
   include/uapi/linux/byteorder/big_endian.h:37:59: note: expanded from macro 
'__le16_to_cpu'
  37 | #define __le16_to_cpu(x) __swab16((__force __u16)(__le16)(x))
 |   ^
   include/uapi/linux/swab.h:102:54: note: expanded from macro '__swab16'
 102 | #define __swab16(x) (__u16)__builtin_bswap16((__u16)(x))
 |  ^
   In file included from drivers/gpu/drm/xe/display/xe_hdcp_gsc.c:7:
   In file included from drivers/gpu/drm/xe/compat-i915-headers/i915_drv.h:15:
   In file included from 
drivers/gpu/drm/xe/compat-i915-headers/gem/i915_gem_object.h:11:
   In file included from drivers/gpu/drm/xe/xe_bo.h:11:
   In file included from drivers/gpu/drm/xe/xe_bo_types.h:9:
   In file included from include/linux/iosys-map.h:10:
   In file included from include/linux/io.h:13:
   In file included from arch/s390/include/asm/io.h:78:
   include/asm-generic/io.h:573:61: warning: performing pointer arithmetic on a 
null pointer has undefined behavior [-Wnull-pointer-arithmetic]
 573 | val = __le32_to_cpu((__le32 __force)__raw_readl(PCI_IOBASE + 
addr));
 | ~~ ^
   include/uapi/linux/byteorder/big_endian.h:35:59: note: expanded from macro 
'__le32_to_cpu'
  35 | #define __le32_to_cpu(x) __swab32((__force __u32)(__le32)(x))
 |   ^
   include/uapi/linux/swab.h:115:54: note: expanded from macro '__swab32'
 115 | #define __swab32(x) (__u32)__builtin_bswap32((__u32)(x))
 |  ^
   In file included from drivers/gpu/drm/xe/display/xe_hdcp_gsc.c:7:
   In file included from drivers/gpu/drm/xe/compat-i915-headers/i915_drv.h:15:
   In file included from 
drivers/gpu/drm/xe/compat-i915-headers/gem/i915_gem_object.h:11:
   In file included from drivers/gpu/drm/xe/xe_bo.h:11:
   In file included from drivers/gpu/drm/xe/xe_bo_types.h:9:
   In file included from include/linux/iosys-map.h:10:
   In file included from include/linux/io.h:13:
   In file included from arch/s390/include/asm/io.h:78:
   include/asm-generic/io.h:584:33: warning: performing pointer arithmetic on a 
null pointer has undefined behavior [-Wnull-pointer-arithmetic]
 584 | __raw_writeb

Re: [PATCH v3 12/16] drm/i915: Simplify intel_initial_plane_config() calling convention

2024-02-02 Thread kernel test robot
Hi Ville,

kernel test robot noticed the following build errors:

[auto build test ERROR on drm-intel/for-linux-next]
[also build test ERROR on drm-intel/for-linux-next-fixes drm-tip/drm-tip 
linus/master v6.8-rc2 next-20240202]
[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/Ville-Syrjala/drm-i915-Use-struct-resource-for-memory-region-IO-as-well/20240125-222947
base:   git://anongit.freedesktop.org/drm-intel for-linux-next
patch link:
https://lore.kernel.org/r/20240116075636.6121-13-ville.syrjala%40linux.intel.com
patch subject: [PATCH v3 12/16] drm/i915: Simplify intel_initial_plane_config() 
calling convention
config: x86_64-randconfig-076-20240202 
(https://download.01.org/0day-ci/archive/20240203/202402030704.ngzofdct-...@intel.com/config)
compiler: clang version 17.0.6 (https://github.com/llvm/llvm-project 
6009708b4367171ccdbf4b5905cb6a803753fe18)
reproduce (this is a W=1 build): 
(https://download.01.org/0day-ci/archive/20240203/202402030704.ngzofdct-...@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 
| Closes: 
https://lore.kernel.org/oe-kbuild-all/202402030704.ngzofdct-...@intel.com/

All errors (new ones prefixed by >>):

>> drivers/gpu/drm/xe/display/xe_plane_initial.c:270:6: error: no previous 
>> prototype for function 'intel_crtc_initial_plane_config' 
>> [-Werror,-Wmissing-prototypes]
 270 | void intel_crtc_initial_plane_config(struct intel_crtc *crtc)
 |  ^
   drivers/gpu/drm/xe/display/xe_plane_initial.c:270:1: note: declare 'static' 
if the function is not intended to be used outside of this translation unit
 270 | void intel_crtc_initial_plane_config(struct intel_crtc *crtc)
 | ^
 | static 
   1 error generated.

Kconfig warnings: (for reference only)
   WARNING: unmet direct dependencies detected for DRM_I915_DEBUG_GEM
   Depends on [n]: HAS_IOMEM [=y] && DRM_I915 [=m] && EXPERT [=y] && 
DRM_I915_WERROR [=n]
   Selected by [m]:
   - DRM_I915_DEBUG [=y] && HAS_IOMEM [=y] && DRM_I915 [=m] && EXPERT [=y] && 
!COMPILE_TEST [=n]


vim +/intel_crtc_initial_plane_config +270 
drivers/gpu/drm/xe/display/xe_plane_initial.c

44e694958b9539 Maarten Lankhorst 2023-08-17  269  
44e694958b9539 Maarten Lankhorst 2023-08-17 @270  void 
intel_crtc_initial_plane_config(struct intel_crtc *crtc)

-- 
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki


[drm-tip:drm-tip 1/7] drivers/gpu/drm/bridge/samsung-dsim.c:1504:3: error: implicit declaration of function 'samsung_dsim_set_stop_state' is invalid in C99

2024-01-28 Thread kernel test robot
tree:   git://anongit.freedesktop.org/drm/drm-tip drm-tip
head:   0f1b42b9d395bd4097b2846230a13869dc638216
commit: cd3a0e22e5de2867cd98b5223094a467a5b0993d [1/7] Merge remote-tracking 
branch 'drm-misc/drm-misc-next' into drm-tip
config: arm-defconfig 
(https://download.01.org/0day-ci/archive/20240129/202401291018.wgyuxgmh-...@intel.com/config)
compiler: clang version 14.0.6 (https://github.com/llvm/llvm-project.git 
f28c006a5895fc0e329fe15fead81e37457cb1d1)
reproduce (this is a W=1 build): 
(https://download.01.org/0day-ci/archive/20240129/202401291018.wgyuxgmh-...@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 
| Closes: 
https://lore.kernel.org/oe-kbuild-all/202401291018.wgyuxgmh-...@intel.com/

All errors (new ones prefixed by >>):

>> drivers/gpu/drm/bridge/samsung-dsim.c:1504:3: error: implicit declaration of 
>> function 'samsung_dsim_set_stop_state' is invalid in C99 
>> [-Werror,-Wimplicit-function-declaration]
   samsung_dsim_set_stop_state(dsi, true);
   ^
   drivers/gpu/drm/bridge/samsung-dsim.c:1504:3: note: did you mean 
'samsung_dsim_set_phy_ctrl'?
   drivers/gpu/drm/bridge/samsung-dsim.c:749:13: note: 
'samsung_dsim_set_phy_ctrl' declared here
   static void samsung_dsim_set_phy_ctrl(struct samsung_dsim *dsi)
   ^
   drivers/gpu/drm/bridge/samsung-dsim.c:1629:22: error: use of undeclared 
identifier 'samsung_dsim_atomic_disable'; did you mean 
'samsung_dsim_atomic_enable'?
   .atomic_disable = samsung_dsim_atomic_disable,
 ^~~
 samsung_dsim_atomic_enable
   drivers/gpu/drm/bridge/samsung-dsim.c:1487:13: note: 
'samsung_dsim_atomic_enable' declared here
   static void samsung_dsim_atomic_enable(struct drm_bridge *bridge,
   ^
   2 errors generated.


vim +/samsung_dsim_set_stop_state +1504 drivers/gpu/drm/bridge/samsung-dsim.c

e7447128ca4a25 Jagan Teki 2023-03-08  1497  
e7447128ca4a25 Jagan Teki 2023-03-08  1498  static void 
samsung_dsim_atomic_post_disable(struct drm_bridge *bridge,
e7447128ca4a25 Jagan Teki 2023-03-08  1499  
 struct drm_bridge_state *old_bridge_state)
e7447128ca4a25 Jagan Teki 2023-03-08  1500  {
e7447128ca4a25 Jagan Teki 2023-03-08  1501  struct samsung_dsim 
*dsi = bridge_to_dsi(bridge);
e7447128ca4a25 Jagan Teki 2023-03-08  1502  
b2fe2292624ac4 Dario Binacchi 2023-12-18  1503  if 
(!samsung_dsim_hw_is_exynos(dsi->plat_data->hw_type))
b2fe2292624ac4 Dario Binacchi 2023-12-18 @1504  
samsung_dsim_set_stop_state(dsi, true);
e7447128ca4a25 Jagan Teki 2023-03-08  1505  
e7447128ca4a25 Jagan Teki 2023-03-08  1506  dsi->state &= 
~DSIM_STATE_ENABLED;
e7447128ca4a25 Jagan Teki 2023-03-08  1507  
pm_runtime_put_sync(dsi->dev);
e7447128ca4a25 Jagan Teki 2023-03-08  1508  }
e7447128ca4a25 Jagan Teki 2023-03-08  1509  

:: The code at line 1504 was first introduced by commit
:: b2fe2292624ac4fc98dcdaf76c983d3f6e8455e5 drm: bridge: samsung-dsim: 
enter display mode in the enable() callback

:: TO: Dario Binacchi 
:: CC: Robert Foss 

-- 
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki


Re: [PATCH v3 12/16] drm/i915: Simplify intel_initial_plane_config() calling convention

2024-01-27 Thread kernel test robot
Hi Ville,

kernel test robot noticed the following build warnings:

[auto build test WARNING on drm-intel/for-linux-next]
[also build test WARNING on drm-intel/for-linux-next-fixes drm-tip/drm-tip 
linus/master v6.8-rc1 next-20240125]
[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/Ville-Syrjala/drm-i915-Use-struct-resource-for-memory-region-IO-as-well/20240125-222947
base:   git://anongit.freedesktop.org/drm-intel for-linux-next
patch link:
https://lore.kernel.org/r/20240116075636.6121-13-ville.syrjala%40linux.intel.com
patch subject: [PATCH v3 12/16] drm/i915: Simplify intel_initial_plane_config() 
calling convention
config: alpha-randconfig-r121-20240127 
(https://download.01.org/0day-ci/archive/20240128/202401281233.cx62upwx-...@intel.com/config)
compiler: alpha-linux-gcc (GCC) 13.2.0
reproduce: 
(https://download.01.org/0day-ci/archive/20240128/202401281233.cx62upwx-...@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 
| Closes: 
https://lore.kernel.org/oe-kbuild-all/202401281233.cx62upwx-...@intel.com/

sparse warnings: (new ones prefixed by >>)
>> drivers/gpu/drm/xe/display/xe_plane_initial.c:270:6: sparse: sparse: symbol 
>> 'intel_crtc_initial_plane_config' was not declared. Should it be static?

vim +/intel_crtc_initial_plane_config +270 
drivers/gpu/drm/xe/display/xe_plane_initial.c

44e694958b9539 Maarten Lankhorst 2023-08-17  269  
44e694958b9539 Maarten Lankhorst 2023-08-17 @270  void 
intel_crtc_initial_plane_config(struct intel_crtc *crtc)

-- 
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki


Re: [PATCH] drm/i915: move interrupt save/restore into vblank section helpers

2024-01-17 Thread kernel test robot
Hi Luca,

kernel test robot noticed the following build errors:

[auto build test ERROR on drm-intel/for-linux-next]
[also build test ERROR on drm-tip/drm-tip linus/master next-20240117]
[cannot apply to drm-intel/for-linux-next-fixes v6.7]
[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/Luca-Coelho/drm-i915-move-interrupt-save-restore-into-vblank-section-helpers/20240117-174910
base:   git://anongit.freedesktop.org/drm-intel for-linux-next
patch link:
https://lore.kernel.org/r/20240117094613.1401573-1-luciano.coelho%40intel.com
patch subject: [PATCH] drm/i915: move interrupt save/restore into vblank 
section helpers
config: i386-randconfig-011-20240117 
(https://download.01.org/0day-ci/archive/20240118/202401180456.xkw1s0m1-...@intel.com/config)
compiler: ClangBuiltLinux clang version 17.0.6 
(https://github.com/llvm/llvm-project 6009708b4367171ccdbf4b5905cb6a803753fe18)
reproduce (this is a W=1 build): 
(https://download.01.org/0day-ci/archive/20240118/202401180456.xkw1s0m1-...@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 
| Closes: 
https://lore.kernel.org/oe-kbuild-all/202401180456.xkw1s0m1-...@intel.com/

All errors (new ones prefixed by >>):

>> drivers/gpu/drm/i915/display/intel_vblank.c:282:17: error: use of undeclared 
>> identifier 'irqflags'
 282 | local_irq_save(irqflags);
 |^
>> drivers/gpu/drm/i915/display/intel_vblank.c:282:17: error: use of undeclared 
>> identifier 'irqflags'
>> drivers/gpu/drm/i915/display/intel_vblank.c:282:17: error: use of undeclared 
>> identifier 'irqflags'
>> drivers/gpu/drm/i915/display/intel_vblank.c:282:17: error: use of undeclared 
>> identifier 'irqflags'
   drivers/gpu/drm/i915/display/intel_vblank.c:294:20: error: use of undeclared 
identifier 'irqflags'
 294 | local_irq_restore(irqflags);
 |   ^
   drivers/gpu/drm/i915/display/intel_vblank.c:294:20: error: use of undeclared 
identifier 'irqflags'
   drivers/gpu/drm/i915/display/intel_vblank.c:294:20: error: use of undeclared 
identifier 'irqflags'
   drivers/gpu/drm/i915/display/intel_vblank.c:294:20: error: use of undeclared 
identifier 'irqflags'
   drivers/gpu/drm/i915/display/intel_vblank.c:309:16: warning: unused variable 
'irqflags' [-Wunused-variable]
 309 | unsigned long irqflags;
 |   ^~~~
   drivers/gpu/drm/i915/display/intel_vblank.c:441:16: warning: unused variable 
'irqflags' [-Wunused-variable]
 441 | unsigned long irqflags;
 |   ^~~~
   2 warnings and 8 errors generated.


vim +/irqflags +282 drivers/gpu/drm/i915/display/intel_vblank.c

   267  
   268  /*
   269   * These functions help enter and exit vblank critical sections.  When
   270   * entering, they disable interrupts and, for i915, acquire the
   271   * uncore's spinlock.  Conversely, when exiting, they release the
   272   * spinlock and restore the interrupts state.
   273   *
   274   * This lock in i915 is needed because some old platforms (at least
   275   * IVB and possibly HSW as well), which are not supported in Xe, need
   276   * all register accesses to the same cacheline to be serialized,
   277   * otherwise they may hang.
   278   */
   279  static void intel_vblank_section_enter(struct drm_i915_private *i915)
   280  __acquires(i915->uncore.lock)
   281  {
 > 282  local_irq_save(irqflags);
   283  #ifdef I915
   284  spin_lock(>uncore.lock);
   285  #endif
   286  }
   287  

-- 
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki


Re: [PATCH] drm/i915: move interrupt save/restore into vblank section helpers

2024-01-17 Thread kernel test robot
Hi Luca,

kernel test robot noticed the following build errors:

[auto build test ERROR on drm-intel/for-linux-next]
[also build test ERROR on drm-tip/drm-tip linus/master next-20240117]
[cannot apply to drm-intel/for-linux-next-fixes v6.7]
[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/Luca-Coelho/drm-i915-move-interrupt-save-restore-into-vblank-section-helpers/20240117-174910
base:   git://anongit.freedesktop.org/drm-intel for-linux-next
patch link:
https://lore.kernel.org/r/20240117094613.1401573-1-luciano.coelho%40intel.com
patch subject: [PATCH] drm/i915: move interrupt save/restore into vblank 
section helpers
config: i386-buildonly-randconfig-004-20240117 
(https://download.01.org/0day-ci/archive/20240118/202401180149.bsppqd72-...@intel.com/config)
compiler: gcc-7 (Ubuntu 7.5.0-6ubuntu2) 7.5.0
reproduce (this is a W=1 build): 
(https://download.01.org/0day-ci/archive/20240118/202401180149.bsppqd72-...@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 
| Closes: 
https://lore.kernel.org/oe-kbuild-all/202401180149.bsppqd72-...@intel.com/

All error/warnings (new ones prefixed by >>):

   In file included from include/linux/bitops.h:7:0,
from include/linux/kernel.h:23,
from arch/x86/include/asm/percpu.h:27,
from arch/x86/include/asm/current.h:10,
from include/linux/mutex.h:14,
from include/linux/notifier.h:14,
from include/linux/pm_qos.h:16,
from drivers/gpu/drm/i915/i915_drv.h:35,
from drivers/gpu/drm/i915/display/intel_vblank.c:6:
   drivers/gpu/drm/i915/display/intel_vblank.c: In function 
'intel_vblank_section_enter':
>> drivers/gpu/drm/i915/display/intel_vblank.c:282:17: error: 'irqflags' 
>> undeclared (first use in this function); did you mean 'mf_flags'?
 local_irq_save(irqflags);
^
   include/linux/typecheck.h:11:9: note: in definition of macro 'typecheck'
 typeof(x) __dummy2; \
^
   include/linux/irqflags.h:245:36: note: in expansion of macro 
'raw_local_irq_save'
#define local_irq_save(flags) do { raw_local_irq_save(flags); } while (0)
   ^~
   drivers/gpu/drm/i915/display/intel_vblank.c:282:2: note: in expansion of 
macro 'local_irq_save'
 local_irq_save(irqflags);
 ^~
   drivers/gpu/drm/i915/display/intel_vblank.c:282:17: note: each undeclared 
identifier is reported only once for each function it appears in
 local_irq_save(irqflags);
^
   include/linux/typecheck.h:11:9: note: in definition of macro 'typecheck'
 typeof(x) __dummy2; \
^
   include/linux/irqflags.h:245:36: note: in expansion of macro 
'raw_local_irq_save'
#define local_irq_save(flags) do { raw_local_irq_save(flags); } while (0)
   ^~
   drivers/gpu/drm/i915/display/intel_vblank.c:282:2: note: in expansion of 
macro 'local_irq_save'
 local_irq_save(irqflags);
 ^~
   include/linux/typecheck.h:12:18: warning: comparison of distinct pointer 
types lacks a cast
 (void)(&__dummy == &__dummy2); \
 ^
   include/linux/irqflags.h:178:3: note: in expansion of macro 'typecheck'
  typecheck(unsigned long, flags); \
  ^
   include/linux/irqflags.h:245:36: note: in expansion of macro 
'raw_local_irq_save'
#define local_irq_save(flags) do { raw_local_irq_save(flags); } while (0)
   ^~
   drivers/gpu/drm/i915/display/intel_vblank.c:282:2: note: in expansion of 
macro 'local_irq_save'
 local_irq_save(irqflags);
 ^~
   drivers/gpu/drm/i915/display/intel_vblank.c: In function 
'intel_vblank_section_exit':
   drivers/gpu/drm/i915/display/intel_vblank.c:294:20: error: 'irqflags' 
undeclared (first use in this function); did you mean 'mf_flags'?
 local_irq_restore(irqflags);
   ^
   include/linux/typecheck.h:11:9: note: in definition of macro 'typecheck'
 typeof(x) __dummy2; \
^
   include/linux/irqflags.h:246:39: note: in expansion of macro 
'raw_local_irq_restore'
#define local_irq_restore(flags) do { raw_local_irq_restore(flags); } while 
(0)
  ^
   drivers/gpu/drm/i915/display/intel_vblank.c:294:2: note: in expansion of 
macro 'local_irq_restore'
 local_irq_restore(irqflags);
 ^
   include/linux/typecheck.h:12:18: warning: comparison of dis

Re: [PATCH v2 12/15] drm/i915: Simplify intel_initial_plane_config() calling convention

2024-01-12 Thread kernel test robot
Hi Ville,

kernel test robot noticed the following build warnings:

[auto build test WARNING on drm-intel/for-linux-next]
[also build test WARNING on drm-tip/drm-tip linus/master next-20240112]
[cannot apply to drm-intel/for-linux-next-fixes v6.7]
[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/Ville-Syrjala/drm-i915-Use-struct-resource-for-memory-region-IO-as-well/20240112-020958
base:   git://anongit.freedesktop.org/drm-intel for-linux-next
patch link:
https://lore.kernel.org/r/20231215105929.29568-13-ville.syrjala%40linux.intel.com
patch subject: [PATCH v2 12/15] drm/i915: Simplify intel_initial_plane_config() 
calling convention
config: arm64-allmodconfig 
(https://download.01.org/0day-ci/archive/20240113/202401131457.pbfnaudc-...@intel.com/config)
compiler: clang version 18.0.0git (https://github.com/llvm/llvm-project 
9bde5becb44ea071f5e1fa1f5d4071dc8788b18c)
reproduce (this is a W=1 build): 
(https://download.01.org/0day-ci/archive/20240113/202401131457.pbfnaudc-...@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 
| Closes: 
https://lore.kernel.org/oe-kbuild-all/202401131457.pbfnaudc-...@intel.com/

All warnings (new ones prefixed by >>):

>> drivers/gpu/drm/xe/display/xe_plane_initial.c:270:6: warning: no previous 
>> prototype for function 'intel_crtc_initial_plane_config' 
>> [-Wmissing-prototypes]
 270 | void intel_crtc_initial_plane_config(struct intel_crtc *crtc)
 |  ^
   drivers/gpu/drm/xe/display/xe_plane_initial.c:270:1: note: declare 'static' 
if the function is not intended to be used outside of this translation unit
 270 | void intel_crtc_initial_plane_config(struct intel_crtc *crtc)
 | ^
 | static 
   1 warning generated.


vim +/intel_crtc_initial_plane_config +270 
drivers/gpu/drm/xe/display/xe_plane_initial.c

44e694958b9539 Maarten Lankhorst 2023-08-17  269  
44e694958b9539 Maarten Lankhorst 2023-08-17 @270  void 
intel_crtc_initial_plane_config(struct intel_crtc *crtc)

-- 
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki


Re: [PATCH v2 12/15] drm/i915: Simplify intel_initial_plane_config() calling convention

2024-01-12 Thread kernel test robot
Hi Ville,

kernel test robot noticed the following build warnings:

[auto build test WARNING on drm-intel/for-linux-next]
[also build test WARNING on drm-tip/drm-tip linus/master next-20240112]
[cannot apply to drm-intel/for-linux-next-fixes v6.7]
[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/Ville-Syrjala/drm-i915-Use-struct-resource-for-memory-region-IO-as-well/20240112-020958
base:   git://anongit.freedesktop.org/drm-intel for-linux-next
patch link:
https://lore.kernel.org/r/20231215105929.29568-13-ville.syrjala%40linux.intel.com
patch subject: [PATCH v2 12/15] drm/i915: Simplify intel_initial_plane_config() 
calling convention
config: arm64-randconfig-004-20240113 
(https://download.01.org/0day-ci/archive/20240113/202401130812.fucmw99v-...@intel.com/config)
compiler: aarch64-linux-gcc (GCC) 13.2.0
reproduce (this is a W=1 build): 
(https://download.01.org/0day-ci/archive/20240113/202401130812.fucmw99v-...@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 
| Closes: 
https://lore.kernel.org/oe-kbuild-all/202401130812.fucmw99v-...@intel.com/

All warnings (new ones prefixed by >>):

>> drivers/gpu/drm/xe/display/xe_plane_initial.c:270:6: warning: no previous 
>> prototype for 'intel_crtc_initial_plane_config' [-Wmissing-prototypes]
 270 | void intel_crtc_initial_plane_config(struct intel_crtc *crtc)
 |  ^~~

Kconfig warnings: (for reference only)
   WARNING: unmet direct dependencies detected for FB_IOMEM_HELPERS
   Depends on [n]: HAS_IOMEM [=y] && FB_CORE [=n]
   Selected by [m]:
   - DRM_XE_DISPLAY [=y] && HAS_IOMEM [=y] && DRM_XE [=m] && EXPERT [=y] && 
DRM_XE [=m]=m


vim +/intel_crtc_initial_plane_config +270 
drivers/gpu/drm/xe/display/xe_plane_initial.c

44e694958b9539 Maarten Lankhorst 2023-08-17  269  
44e694958b9539 Maarten Lankhorst 2023-08-17 @270  void 
intel_crtc_initial_plane_config(struct intel_crtc *crtc)

-- 
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki


Re: [PATCH 4/6] drm/imx: prefer snprintf over sprintf

2024-01-12 Thread kernel test robot
Hi Jani,

kernel test robot noticed the following build warnings:

[auto build test WARNING on drm-misc/drm-misc-next]
[also build test WARNING on drm-intel/for-linux-next 
drm-intel/for-linux-next-fixes drm-tip/drm-tip linus/master v6.7 next-20240112]
[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/Jani-Nikula/drm-nouveau-acr-ga102-remove-unused-but-set-variable/20240111-014206
base:   git://anongit.freedesktop.org/drm/drm-misc drm-misc-next
patch link:
https://lore.kernel.org/r/14c0108a54007a8360d84162a1d63cba9613b945.1704908087.git.jani.nikula%40intel.com
patch subject: [PATCH 4/6] drm/imx: prefer snprintf over sprintf
config: sparc64-allmodconfig 
(https://download.01.org/0day-ci/archive/20240112/202401121801.3j6gnsgm-...@intel.com/config)
compiler: sparc64-linux-gcc (GCC) 13.2.0
reproduce (this is a W=1 build): 
(https://download.01.org/0day-ci/archive/20240112/202401121801.3j6gnsgm-...@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 
| Closes: 
https://lore.kernel.org/oe-kbuild-all/202401121801.3j6gnsgm-...@intel.com/

All warnings (new ones prefixed by >>):

   drivers/gpu/drm/imx/ipuv3/imx-ldb.c: In function 'imx_ldb_probe':
>> drivers/gpu/drm/imx/ipuv3/imx-ldb.c:658:57: warning: '_sel' directive output 
>> may be truncated writing 4 bytes into a region of size between 3 and 13 
>> [-Wformat-truncation=]
 658 | snprintf(clkname, sizeof(clkname), "di%d_sel", i);
 | ^~~~
   drivers/gpu/drm/imx/ipuv3/imx-ldb.c:658:17: note: 'snprintf' output between 
8 and 18 bytes into a destination of size 16
 658 | snprintf(clkname, sizeof(clkname), "di%d_sel", i);
 | ^


vim +/_sel +658 drivers/gpu/drm/imx/ipuv3/imx-ldb.c

   617  
   618  static int imx_ldb_probe(struct platform_device *pdev)
   619  {
   620  struct device *dev = >dev;
   621  struct device_node *np = dev->of_node;
   622  struct device_node *child;
   623  struct imx_ldb *imx_ldb;
   624  int dual;
   625  int ret;
   626  int i;
   627  
   628  imx_ldb = devm_kzalloc(dev, sizeof(*imx_ldb), GFP_KERNEL);
   629  if (!imx_ldb)
   630  return -ENOMEM;
   631  
   632  imx_ldb->regmap = syscon_regmap_lookup_by_phandle(np, "gpr");
   633  if (IS_ERR(imx_ldb->regmap)) {
   634  dev_err(dev, "failed to get parent regmap\n");
   635  return PTR_ERR(imx_ldb->regmap);
   636  }
   637  
   638  /* disable LDB by resetting the control register to POR default 
*/
   639  regmap_write(imx_ldb->regmap, IOMUXC_GPR2, 0);
   640  
   641  imx_ldb->dev = dev;
   642  imx_ldb->lvds_mux = device_get_match_data(dev);
   643  
   644  dual = of_property_read_bool(np, "fsl,dual-channel");
   645  if (dual)
   646  imx_ldb->ldb_ctrl |= LDB_SPLIT_MODE_EN;
   647  
   648  /*
   649   * There are three different possible clock mux configurations:
   650   * i.MX53:  ipu1_di0_sel, ipu1_di1_sel
   651   * i.MX6q:  ipu1_di0_sel, ipu1_di1_sel, ipu2_di0_sel, 
ipu2_di1_sel
   652   * i.MX6dl: ipu1_di0_sel, ipu1_di1_sel, lcdif_sel
   653   * Map them all to di0_sel...di3_sel.
   654   */
   655  for (i = 0; i < 4; i++) {
   656  char clkname[16];
   657  
 > 658  snprintf(clkname, sizeof(clkname), "di%d_sel", i);
   659  imx_ldb->clk_sel[i] = devm_clk_get(imx_ldb->dev, 
clkname);
   660  if (IS_ERR(imx_ldb->clk_sel[i])) {
   661  ret = PTR_ERR(imx_ldb->clk_sel[i]);
   662  imx_ldb->clk_sel[i] = NULL;
   663  break;
   664  }
   665  
   666  imx_ldb->clk_parent[i] = 
clk_get_parent(imx_ldb->clk_sel[i]);
   667  }
   668  if (i == 0)
   669  return ret;
   670  
   671  for_each_child_of_node(np, child) {
   672  struct imx_ldb_channel *channel;
   673  int bus_format;
   674  
   675  ret = of_property_read_u32(child, "reg", );
   676  if (ret || i < 0 || i > 1) {
   677  ret = -EINVAL;
   678  goto free_child

Re: [PATCH 3/6] drm/amdgpu: prefer snprintf over sprintf

2024-01-11 Thread kernel test robot
Hi Jani,

kernel test robot noticed the following build warnings:

[auto build test WARNING on drm-misc/drm-misc-next]
[also build test WARNING on drm-intel/for-linux-next 
drm-intel/for-linux-next-fixes drm-tip/drm-tip linus/master v6.7 next-20240111]
[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/Jani-Nikula/drm-nouveau-acr-ga102-remove-unused-but-set-variable/20240111-014206
base:   git://anongit.freedesktop.org/drm/drm-misc drm-misc-next
patch link:
https://lore.kernel.org/r/fea7a52924f98b1ac24f4a7e6ba21d7754422430.1704908087.git.jani.nikula%40intel.com
patch subject: [PATCH 3/6] drm/amdgpu: prefer snprintf over sprintf
config: sparc64-allmodconfig 
(https://download.01.org/0day-ci/archive/20240112/202401121126.i9vgrvmb-...@intel.com/config)
compiler: sparc64-linux-gcc (GCC) 13.2.0
reproduce (this is a W=1 build): 
(https://download.01.org/0day-ci/archive/20240112/202401121126.i9vgrvmb-...@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 
| Closes: 
https://lore.kernel.org/oe-kbuild-all/202401121126.i9vgrvmb-...@intel.com/

All warnings (new ones prefixed by >>):

   drivers/gpu/drm/amd/amdgpu/amdgpu_gfx.c: In function 
'amdgpu_gfx_kiq_init_ring':
>> drivers/gpu/drm/amd/amdgpu/amdgpu_gfx.c:332:61: warning: '%d' directive 
>> output may be truncated writing between 1 and 10 bytes into a region of size 
>> between 0 and 8 [-Wformat-truncation=]
 332 | snprintf(ring->name, sizeof(ring->name), "kiq_%d.%d.%d.%d",
 | ^~
   drivers/gpu/drm/amd/amdgpu/amdgpu_gfx.c:332:50: note: directive argument in 
the range [0, 2147483647]
 332 | snprintf(ring->name, sizeof(ring->name), "kiq_%d.%d.%d.%d",
 |  ^
   drivers/gpu/drm/amd/amdgpu/amdgpu_gfx.c:332:9: note: 'snprintf' output 
between 12 and 41 bytes into a destination of size 16
 332 | snprintf(ring->name, sizeof(ring->name), "kiq_%d.%d.%d.%d",
 | ^~~
 333 |  xcc_id, ring->me, ring->pipe, ring->queue);
 |  ~~


vim +332 drivers/gpu/drm/amd/amdgpu/amdgpu_gfx.c

   306  
   307  int amdgpu_gfx_kiq_init_ring(struct amdgpu_device *adev,
   308   struct amdgpu_ring *ring,
   309   struct amdgpu_irq_src *irq, int xcc_id)
   310  {
   311  struct amdgpu_kiq *kiq = >gfx.kiq[xcc_id];
   312  int r = 0;
   313  
   314  spin_lock_init(>ring_lock);
   315  
   316  ring->adev = NULL;
   317  ring->ring_obj = NULL;
   318  ring->use_doorbell = true;
   319  ring->xcc_id = xcc_id;
   320  ring->vm_hub = AMDGPU_GFXHUB(xcc_id);
   321  ring->doorbell_index =
   322  (adev->doorbell_index.kiq +
   323   xcc_id * adev->doorbell_index.xcc_doorbell_range)
   324  << 1;
   325  
   326  r = amdgpu_gfx_kiq_acquire(adev, ring, xcc_id);
   327  if (r)
   328  return r;
   329  
   330  ring->eop_gpu_addr = kiq->eop_gpu_addr;
   331  ring->no_scheduler = true;
 > 332  snprintf(ring->name, sizeof(ring->name), "kiq_%d.%d.%d.%d",
   333   xcc_id, ring->me, ring->pipe, ring->queue);
   334  r = amdgpu_ring_init(adev, ring, 1024, irq, 
AMDGPU_CP_KIQ_IRQ_DRIVER0,
   335   AMDGPU_RING_PRIO_DEFAULT, NULL);
   336  if (r)
   337  dev_warn(adev->dev, "(%d) failed to init kiq ring\n", 
r);
   338  
   339  return r;
   340  }
   341  

-- 
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki


Re: [PATCH 3/4] drm/ttm: improve idle/busy handling

2023-12-15 Thread kernel test robot
Hi Christian,

kernel test robot noticed the following build warnings:

[auto build test WARNING on drm-misc/drm-misc-next]
[also build test WARNING on drm-intel/for-linux-next 
drm-intel/for-linux-next-fixes drm-tip/drm-tip linus/master v6.7-rc5 
next-20231215]
[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/Christian-K-nig/drm-ttm-replace-busy-placement-with-flags-v3/20231213-224456
base:   git://anongit.freedesktop.org/drm/drm-misc drm-misc-next
patch link:
https://lore.kernel.org/r/20231213144222.1871-3-christian.koenig%40amd.com
patch subject: [PATCH 3/4] drm/ttm: improve idle/busy handling
config: x86_64-defconfig 
(https://download.01.org/0day-ci/archive/20231216/202312160809.nvmibwrj-...@intel.com/config)
compiler: gcc-11 (Debian 11.3.0-12) 11.3.0
reproduce (this is a W=1 build): 
(https://download.01.org/0day-ci/archive/20231216/202312160809.nvmibwrj-...@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 
| Closes: 
https://lore.kernel.org/oe-kbuild-all/202312160809.nvmibwrj-...@intel.com/

All warnings (new ones prefixed by >>):

>> scripts/kernel-doc: drivers/gpu/drm/ttm/ttm_resource.c:301: warning: 
>> Function parameter or struct member 'busy' not described in 
>> 'ttm_resource_compatible'

-- 
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki


Re: [PATCH 3/4] drm/ttm: improve idle/busy handling

2023-12-14 Thread kernel test robot
Hi Christian,

kernel test robot noticed the following build warnings:

[auto build test WARNING on drm-misc/drm-misc-next]
[also build test WARNING on drm-intel/for-linux-next 
drm-intel/for-linux-next-fixes drm-tip/drm-tip linus/master v6.7-rc5 
next-20231214]
[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/Christian-K-nig/drm-ttm-replace-busy-placement-with-flags-v3/20231213-224456
base:   git://anongit.freedesktop.org/drm/drm-misc drm-misc-next
patch link:
https://lore.kernel.org/r/20231213144222.1871-3-christian.koenig%40amd.com
patch subject: [PATCH 3/4] drm/ttm: improve idle/busy handling
config: arm-defconfig 
(https://download.01.org/0day-ci/archive/20231214/202312141637.ciyxvfvl-...@intel.com/config)
compiler: clang version 14.0.6 (https://github.com/llvm/llvm-project.git 
f28c006a5895fc0e329fe15fead81e37457cb1d1)
reproduce (this is a W=1 build): 
(https://download.01.org/0day-ci/archive/20231214/202312141637.ciyxvfvl-...@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 
| Closes: 
https://lore.kernel.org/oe-kbuild-all/202312141637.ciyxvfvl-...@intel.com/

All warnings (new ones prefixed by >>):

>> drivers/gpu/drm/ttm/ttm_resource.c:301: warning: Function parameter or 
>> member 'busy' not described in 'ttm_resource_compatible'


vim +301 drivers/gpu/drm/ttm/ttm_resource.c

544432703b2fe7 Arunpravin Paneer Selvam 2022-08-20  289  
544432703b2fe7 Arunpravin Paneer Selvam 2022-08-20  290  /**
9909b7ee1d1561 Somalapuram Amaranath2023-12-13  291   * 
ttm_resource_compatible - check if resource is compatible with placement
544432703b2fe7 Arunpravin Paneer Selvam 2022-08-20  292   *
9909b7ee1d1561 Somalapuram Amaranath2023-12-13  293   * @res: the resource 
to check
9909b7ee1d1561 Somalapuram Amaranath2023-12-13  294   * @placement: the 
placement to check against
544432703b2fe7 Arunpravin Paneer Selvam 2022-08-20  295   *
9909b7ee1d1561 Somalapuram Amaranath2023-12-13  296   * Returns true if the 
placement is compatible.
544432703b2fe7 Arunpravin Paneer Selvam 2022-08-20  297   */
9909b7ee1d1561 Somalapuram Amaranath2023-12-13  298  bool 
ttm_resource_compatible(struct ttm_resource *res,
1e59504faf5d28 Christian König  2023-12-13  299 
 struct ttm_placement *placement,
1e59504faf5d28 Christian König  2023-12-13  300 
 bool busy)
98cca519df6da6 Christian König  2021-08-30 @301  {
544432703b2fe7 Arunpravin Paneer Selvam 2022-08-20  302 struct 
ttm_buffer_object *bo = res->bo;
544432703b2fe7 Arunpravin Paneer Selvam 2022-08-20  303 struct 
ttm_device *bdev = bo->bdev;
98cca519df6da6 Christian König  2021-08-30  304 unsigned i;
98cca519df6da6 Christian König  2021-08-30  305  
98cca519df6da6 Christian König  2021-08-30  306 if 
(res->placement & TTM_PL_FLAG_TEMPORARY)
98cca519df6da6 Christian König  2021-08-30  307 return 
false;
98cca519df6da6 Christian König  2021-08-30  308  
9909b7ee1d1561 Somalapuram Amaranath2023-12-13  309 for (i = 0; i < 
placement->num_placement; i++) {
9909b7ee1d1561 Somalapuram Amaranath2023-12-13  310 const 
struct ttm_place *place = >placement[i];
9909b7ee1d1561 Somalapuram Amaranath2023-12-13  311 struct 
ttm_resource_manager *man;
9909b7ee1d1561 Somalapuram Amaranath2023-12-13  312  
9909b7ee1d1561 Somalapuram Amaranath2023-12-13  313 if 
(res->mem_type != place->mem_type)
9909b7ee1d1561 Somalapuram Amaranath2023-12-13  314 
continue;
98cca519df6da6 Christian König  2021-08-30  315  
1e59504faf5d28 Christian König  2023-12-13  316 if 
(place->flags & (busy ? TTM_PL_FLAG_IDLE : TTM_PL_FLAG_BUSY))
1e59504faf5d28 Christian König  2023-12-13  317 
continue;
1e59504faf5d28 Christian König  2023-12-13  318  
1e59504faf5d28 Christian König  2023-12-13  319 if 
(place->flags & TTM_PL_FLAG_CONTIGUOUS &&
1e59504faf5d28 Christian König  2023-12-13  320  
!(res->placement & TTM_PL_FLAG_CONTIGUOUS))
1e59504faf5d28 Christian König  2023-12-13  321 
continue;
1e59504faf5d28 Christian König  2023-12-13  322  
9909b7ee1d1561 Somalapuram Amaranath2023-12-13  323 man = 
ttm_manager_type(bdev, res->mem_type);
9909b7ee1d1561 Somalapuram Amaranath2023-12-13  324 if 
(ma

Re: [PATCH 1/3] drm: Add Adaptive Sync SDP logging

2023-12-08 Thread kernel test robot
Hi Mitul,

kernel test robot noticed the following build warnings:

[auto build test WARNING on drm-intel/for-linux-next]
[also build test WARNING on drm-intel/for-linux-next-fixes drm/drm-next 
drm-tip/drm-tip linus/master v6.7-rc4 next-20231208]
[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/Mitul-Golani/drm-Add-Adaptive-Sync-SDP-logging/20231208-142503
base:   git://anongit.freedesktop.org/drm-intel for-linux-next
patch link:
https://lore.kernel.org/r/20231208061933.964588-2-mitulkumar.ajitkumar.golani%40intel.com
patch subject: [PATCH 1/3] drm: Add Adaptive Sync SDP logging
reproduce: 
(https://download.01.org/0day-ci/archive/20231209/202312090656.uvvxevqz-...@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 
| Closes: 
https://lore.kernel.org/oe-kbuild-all/202312090656.uvvxevqz-...@intel.com/

All warnings (new ones prefixed by >>):

>> ./include/drm/display/drm_dp_helper.h:126: warning: Function parameter or 
>> member 'revision' not described in 'drm_dp_as_sdp'
>> ./include/drm/display/drm_dp_helper.h:126: warning: Function parameter or 
>> member 'vtotal' not described in 'drm_dp_as_sdp'
>> ./include/drm/display/drm_dp_helper.h:126: warning: Function parameter or 
>> member 'target_rr' not described in 'drm_dp_as_sdp'

vim +126 ./include/drm/display/drm_dp_helper.h

   100  
   101  /**
   102   * struct drm_dp_as_sdp - drm DP Adaptive Sync SDP
   103   *
   104   * This structure represents a DP AS SDP of drm
   105   * It is based on DP 2.1 spec [Table 2-126:  Adaptive-Sync SDP Header 
Bytes] and
   106   * [Table 2-127: Adaptive-Sync SDP Payload for DB0 through DB8]
   107   *
   108   * @sdp_type: secondary-data packet type
   109   * @length: number of valid data bytes
   110   * @vmin: minimum vtotal
   111   * @vmax: maximum vtotal
   112   * @duration_incr_ms: Successive frame duration increase
   113   * @duration_decr_ms: Successive frame duration decrease
   114   * @operation_mode: Adaptive Sync Operation Mode
   115   */
   116  
   117  struct drm_dp_as_sdp {
   118  unsigned char sdp_type;
   119  unsigned char revision;
   120  unsigned char length;
   121  int vtotal;
   122  int target_rr;
   123  int duration_incr_ms;
   124  int duration_decr_ms;
   125  int operation_mode;
 > 126  };
   127  

-- 
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki


[Intel-gfx] [drm-intel:drm-intel-gt-next] [drm/i915] [confidence: ] 9bb66c179f: assertion_failure

2023-12-07 Thread kernel test robot



Hello,

kernel test robot noticed "assertion_failure" on:

commit: 9bb66c179f50e61df20ba13c9b34ca17d00b05fb ("drm/i915: Reserve some 
kernel space per vm")
git://anongit.freedesktop.org/drm-intel drm-intel-gt-next

in testcase: igt
version: igt-x86_64-0f075441-1_20230520
with following parameters:

group: group-04



compiler: gcc-12
test machine: 20 threads 1 sockets (Commet Lake) with 16G memory

(please refer to attached dmesg/kmsg for entire log/backtrace)


we also observed below tests failed upon this commit while pass on parent.

8aa519f17512da50 9bb66c179f50e61df20ba13c9b3
 ---
   fail:runs  %reproductionfail:runs
   | | |
   :6  100%   6:6 
igt.api_intel_bb.bb-with-allocator.fail
   :6  100%   6:6 
igt.api_intel_bb.blit-noreloc-keep-cache.fail
   :6  100%   6:6 
igt.api_intel_bb.blit-noreloc-purge-cache.fail
   :6  100%   6:6 
igt.api_intel_bb.blit-reloc-purge-cache.fail
   :6  100%   6:6 igt.api_intel_bb.delta-check.fail
   :6  100%   6:6 
igt.api_intel_bb.object-noreloc-keep-cache-simple.fail
   :6  100%   6:6 
igt.api_intel_bb.object-noreloc-purge-cache-simple.fail
   :6   83%   5:6 
igt.api_intel_bb.object-reloc-purge-cache.fail
   :6  100%   6:6 
igt.api_intel_bb.simple-bb-ctx.fail
   :6  100%   6:6 igt.api_intel_bb.simple-bb.fail



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 
| Closes: 
https://lore.kernel.org/oe-lkp/202312071643.321205c6-oliver.s...@intel.com


[   43.922756][  T447]
[   43.935008][  T447] IGT-Version: 1.27.1-g0f075441 (x86_64) (Linux: 
6.6.0-rc7-01579-g9bb66c179f50 x86_64)
[   43.935018][  T447]
[   43.947248][  T447] Starting subtest: bb-with-allocator
[   43.947258][  T447]
[   43.956752][  T447] (api_intel_bb:857) intel_batchbuffer-CRITICAL: Test 
assertion failure function __intel_bb_add_object, file 
../lib/intel_batchbuffer.c:1673:
[   43.956762][  T447]
[   43.974467][  T447] (api_intel_bb:857) intel_batchbuffer-CRITICAL: Failed 
assertion: allocated || reserved
[   43.974477][  T447]
[   43.987691][  T447] (api_intel_bb:857) intel_batchbuffer-CRITICAL: Can't get 
offset, allocated: 0, reserved: 0
[   43.987706][  T447]


The kernel config and materials to reproduce are available at:
https://download.01.org/0day-ci/archive/20231207/202312071643.321205c6-oliver.s...@intel.com



-- 
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki



Re: [Intel-gfx] [PATCH] drm/i915/hdcp: Fail Repeater authentication if Type1 device not present

2023-12-06 Thread kernel test robot
Hi Suraj,

kernel test robot noticed the following build errors:

[auto build test ERROR on drm-tip/drm-tip]

url:
https://github.com/intel-lab-lkp/linux/commits/Suraj-Kandpal/drm-i915-hdcp-Fail-Repeater-authentication-if-Type1-device-not-present/20231206-174124
base:   git://anongit.freedesktop.org/drm/drm-tip drm-tip
patch link:
https://lore.kernel.org/r/20231206093916.1733863-1-suraj.kandpal%40intel.com
patch subject: [Intel-gfx] [PATCH] drm/i915/hdcp: Fail Repeater authentication 
if Type1 device not present
config: x86_64-defconfig 
(https://download.01.org/0day-ci/archive/20231206/202312062206.3ktqfac1-...@intel.com/config)
compiler: gcc-11 (Debian 11.3.0-12) 11.3.0
reproduce (this is a W=1 build): 
(https://download.01.org/0day-ci/archive/20231206/202312062206.3ktqfac1-...@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 
| Closes: 
https://lore.kernel.org/oe-kbuild-all/202312062206.3ktqfac1-...@intel.com/

All errors (new ones prefixed by >>):

   In file included from include/drm/ttm/ttm_resource.h:34,
from include/drm/ttm/ttm_device.h:30,
from drivers/gpu/drm/i915/i915_drv.h:37,
from drivers/gpu/drm/i915/display/intel_hdcp.c:18:
   drivers/gpu/drm/i915/display/intel_hdcp.c: In function 
'hdcp2_authenticate_repeater_topology':
>> drivers/gpu/drm/i915/display/intel_hdcp.c:1638:30: error: 'dev_priv' 
>> undeclared (first use in this function); did you mean 'dev_crit'?
1638 | drm_dbg_kms(_priv->drm,
 |  ^~~~
   include/drm/drm_print.h:410:29: note: in definition of macro 'drm_dev_dbg'
 410 | __drm_dev_dbg(NULL, dev, cat, fmt, ##__VA_ARGS__)
 | ^~~
   drivers/gpu/drm/i915/display/intel_hdcp.c:1638:17: note: in expansion of 
macro 'drm_dbg_kms'
1638 | drm_dbg_kms(_priv->drm,
 | ^~~
   drivers/gpu/drm/i915/display/intel_hdcp.c:1638:30: note: each undeclared 
identifier is reported only once for each function it appears in
1638 | drm_dbg_kms(_priv->drm,
 |  ^~~~
   include/drm/drm_print.h:410:29: note: in definition of macro 'drm_dev_dbg'
 410 | __drm_dev_dbg(NULL, dev, cat, fmt, ##__VA_ARGS__)
 | ^~~
   drivers/gpu/drm/i915/display/intel_hdcp.c:1638:17: note: in expansion of 
macro 'drm_dbg_kms'
1638 | drm_dbg_kms(_priv->drm,
 | ^~~


vim +1638 drivers/gpu/drm/i915/display/intel_hdcp.c

  1599  
  1600  static
  1601  int hdcp2_authenticate_repeater_topology(struct intel_connector 
*connector)
  1602  {
  1603  struct intel_digital_port *dig_port = 
intel_attached_dig_port(connector);
  1604  struct drm_i915_private *i915 = to_i915(connector->base.dev);
  1605  struct intel_hdcp *hdcp = >hdcp;
  1606  union {
  1607  struct hdcp2_rep_send_receiverid_list recvid_list;
  1608  struct hdcp2_rep_send_ack rep_ack;
  1609  } msgs;
  1610  const struct intel_hdcp_shim *shim = hdcp->shim;
  1611  u32 seq_num_v, device_cnt;
  1612  u8 *rx_info;
  1613  int ret;
  1614  
  1615  ret = shim->read_2_2_msg(connector, 
HDCP_2_2_REP_SEND_RECVID_LIST,
  1616   _list, 
sizeof(msgs.recvid_list));
  1617  if (ret < 0)
  1618  return ret;
  1619  
  1620  rx_info = msgs.recvid_list.rx_info;
  1621  
  1622  if (HDCP_2_2_MAX_CASCADE_EXCEEDED(rx_info[1]) ||
  1623  HDCP_2_2_MAX_DEVS_EXCEEDED(rx_info[1])) {
  1624  drm_dbg_kms(>drm, "Topology Max Size Exceeded\n");
  1625  return -EINVAL;
  1626  }
  1627  
  1628  /*
  1629   * MST topology is not Type 1 capable if it contains a 
downstream
  1630   * device that is only HDCP 1.x or Legacy HDCP 2.0/2.1 
compliant.
  1631   */
  1632  dig_port->hdcp_mst_type1_capable =
  1633  !HDCP_2_2_HDCP1_DEVICE_CONNECTED(rx_info[1]) &&
  1634  !HDCP_2_2_HDCP_2_0_REP_CONNECTED(rx_info[1]);
  1635  
  1636  if (!dig_port->hdcp_mst_type1_capable && hdcp->content_type &&
  1637  !intel_encoder_is_mst(connector->encoder)) {
> 1638  drm_dbg_kms(_priv->drm,
  1639  "HDCP1.x or 2.0 Legacy Device 
Downstream\n");
  1640  return -EINVAL;
  1641  }
  1642  
  1643  /* Converting and Storing the seq_num_v to local variable as 
DWORD */
  1644  seq_num_v =
  1645 

Re: [Intel-gfx] [PATCH] drm/i915/hdcp: Fail Repeater authentication if Type1 device not present

2023-12-06 Thread kernel test robot
Hi Suraj,

kernel test robot noticed the following build errors:

[auto build test ERROR on drm-tip/drm-tip]

url:
https://github.com/intel-lab-lkp/linux/commits/Suraj-Kandpal/drm-i915-hdcp-Fail-Repeater-authentication-if-Type1-device-not-present/20231206-174124
base:   git://anongit.freedesktop.org/drm/drm-tip drm-tip
patch link:
https://lore.kernel.org/r/20231206093916.1733863-1-suraj.kandpal%40intel.com
patch subject: [Intel-gfx] [PATCH] drm/i915/hdcp: Fail Repeater authentication 
if Type1 device not present
config: x86_64-allyesconfig 
(https://download.01.org/0day-ci/archive/20231206/202312062210.sq5uhqkd-...@intel.com/config)
compiler: clang version 16.0.4 (https://github.com/llvm/llvm-project.git 
ae42196bc493ffe877a7e3dff8be32035dea4d07)
reproduce (this is a W=1 build): 
(https://download.01.org/0day-ci/archive/20231206/202312062210.sq5uhqkd-...@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 
| Closes: 
https://lore.kernel.org/oe-kbuild-all/202312062210.sq5uhqkd-...@intel.com/

All errors (new ones prefixed by >>):

   warning: unknown warning option '-Wrestrict' [-Wunknown-warning-option]
   warning: unknown warning option '-Wpacked-not-aligned'; did you mean 
'-Wpacked-non-pod'? [-Wunknown-warning-option]
   warning: unknown warning option '-Wformat-overflow'; did you mean 
'-Wshift-overflow'? [-Wunknown-warning-option]
   warning: unknown warning option '-Wformat-truncation' 
[-Wunknown-warning-option]
   warning: unknown warning option '-Wstringop-overflow'; did you mean 
'-Wshift-overflow'? [-Wunknown-warning-option]
   warning: unknown warning option '-Wstringop-truncation'; did you mean 
'-Wstring-concatenation'? [-Wunknown-warning-option]
>> drivers/gpu/drm/i915/display/intel_hdcp.c:1638:16: error: use of undeclared 
>> identifier 'dev_priv'
   drm_dbg_kms(_priv->drm,
^
>> drivers/gpu/drm/i915/display/intel_hdcp.c:1638:16: error: use of undeclared 
>> identifier 'dev_priv'
   6 warnings and 2 errors generated.


vim +/dev_priv +1638 drivers/gpu/drm/i915/display/intel_hdcp.c

  1599  
  1600  static
  1601  int hdcp2_authenticate_repeater_topology(struct intel_connector 
*connector)
  1602  {
  1603  struct intel_digital_port *dig_port = 
intel_attached_dig_port(connector);
  1604  struct drm_i915_private *i915 = to_i915(connector->base.dev);
  1605  struct intel_hdcp *hdcp = >hdcp;
  1606  union {
  1607  struct hdcp2_rep_send_receiverid_list recvid_list;
  1608  struct hdcp2_rep_send_ack rep_ack;
  1609  } msgs;
  1610  const struct intel_hdcp_shim *shim = hdcp->shim;
  1611  u32 seq_num_v, device_cnt;
  1612  u8 *rx_info;
  1613  int ret;
  1614  
  1615  ret = shim->read_2_2_msg(connector, 
HDCP_2_2_REP_SEND_RECVID_LIST,
  1616   _list, 
sizeof(msgs.recvid_list));
  1617  if (ret < 0)
  1618  return ret;
  1619  
  1620  rx_info = msgs.recvid_list.rx_info;
  1621  
  1622  if (HDCP_2_2_MAX_CASCADE_EXCEEDED(rx_info[1]) ||
  1623  HDCP_2_2_MAX_DEVS_EXCEEDED(rx_info[1])) {
  1624  drm_dbg_kms(>drm, "Topology Max Size Exceeded\n");
  1625  return -EINVAL;
  1626  }
  1627  
  1628  /*
  1629   * MST topology is not Type 1 capable if it contains a 
downstream
  1630   * device that is only HDCP 1.x or Legacy HDCP 2.0/2.1 
compliant.
  1631   */
  1632  dig_port->hdcp_mst_type1_capable =
  1633  !HDCP_2_2_HDCP1_DEVICE_CONNECTED(rx_info[1]) &&
  1634  !HDCP_2_2_HDCP_2_0_REP_CONNECTED(rx_info[1]);
  1635  
  1636  if (!dig_port->hdcp_mst_type1_capable && hdcp->content_type &&
  1637  !intel_encoder_is_mst(connector->encoder)) {
> 1638  drm_dbg_kms(_priv->drm,
  1639  "HDCP1.x or 2.0 Legacy Device 
Downstream\n");
  1640  return -EINVAL;
  1641  }
  1642  
  1643  /* Converting and Storing the seq_num_v to local variable as 
DWORD */
  1644  seq_num_v =
  1645  drm_hdcp_be24_to_cpu((const u8 
*)msgs.recvid_list.seq_num_v);
  1646  
  1647  if (!hdcp->hdcp2_encrypted && seq_num_v) {
  1648  drm_dbg_kms(>drm,
  1649  "Non zero Seq_num_v at first RecvId_List 
msg\n");
  1650  return -EINVAL;
  1651  }
  1652  
  1653  if (seq_num_v < hdcp->seq_num_v) {
  1654  /* Roll over of the seq_num_v from repeater. 
Reauthenticate. */
  1655 

[Intel-gfx] [linux-next:master] BUILD REGRESSION 0f5f12ac05f36f117e793656c3f560625e927f1b

2023-12-05 Thread kernel test robot
tree/branch: 
https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
branch HEAD: 0f5f12ac05f36f117e793656c3f560625e927f1b  Add linux-next specific 
files for 20231205

Error/Warning reports:

https://lore.kernel.org/oe-kbuild-all/202312051416.yirwcymp-...@intel.com
https://lore.kernel.org/oe-kbuild-all/202312051418.jkbrbdyp-...@intel.com
https://lore.kernel.org/oe-kbuild-all/202312051419.dsbnpgym-...@intel.com
https://lore.kernel.org/oe-kbuild-all/202312051913.e5iif8qz-...@intel.com
https://lore.kernel.org/oe-kbuild-all/202312051935.ixiyu8kn-...@intel.com
https://lore.kernel.org/oe-kbuild-all/202312052245.yfpbsgnh-...@intel.com
https://lore.kernel.org/oe-kbuild-all/202312060025.bdeqzrwx-...@intel.com
https://lore.kernel.org/oe-kbuild-all/202312060311.tnsv2fl2-...@intel.com
https://lore.kernel.org/oe-kbuild-all/202312060355.m0ejtq4x-...@intel.com
https://lore.kernel.org/oe-kbuild-all/202312061137.qgjj4ntc-...@intel.com

Error/Warning: (recently discovered and may have been fixed)

aarch64-linux-ld: qcom_stats.c:(.text+0x470): undefined reference to `qmp_send'
arch/mips/kernel/crash.c:96:6: warning: no previous prototype for 
'default_machine_crash_shutdown' [-Wmissing-prototypes]
arch/mips/kernel/machine_kexec.c:161:6: warning: no previous prototype for 
'kexec_nonboot_cpu_jump' [-Wmissing-prototypes]
arch/mips/kernel/machine_kexec.c:170:6: warning: conflicting types for 
'kexec_reboot'; have 'void(void)'
arch/mips/kernel/machine_kexec.c:170:6: warning: no previous prototype for 
'kexec_reboot' [-Wmissing-prototypes]
arch/mips/kernel/machine_kexec.c:77:17: error: 'kexec_args' undeclared (first 
use in this function)
drivers/gpu/drm/amd/amdgpu/../amdkfd/kfd_process.c:1671:9: sparse:struct 
dma_fence *
drivers/gpu/drm/amd/amdgpu/../amdkfd/kfd_process.c:1671:9: sparse:struct 
dma_fence [noderef] __rcu *
drivers/gpu/drm/amd/amdgpu/amdgpu_amdkfd_gpuvm.c:2765:36: sparse:struct 
dma_fence *
drivers/gpu/drm/amd/amdgpu/amdgpu_amdkfd_gpuvm.c:2765:36: sparse:struct 
dma_fence [noderef] __rcu *
drivers/leds/leds-sun50i-a100.c:309:12: error: call to __compiletime_assert_280 
declared with 'error' attribute: FIELD_PREP: value too large for the field
drivers/media/i2c/saa6752hs.c:598:18: error: implicit declaration of function 
'v4l2_subdev_state_get_format' [-Werror=implicit-function-declaration]
qcom_stats.c:(.text+0x33c): undefined reference to `qmp_send'
qcom_stats.c:(.text+0x398): undefined reference to `__aeabi_uldivmod'
qcom_stats.c:(.text+0x6c4): undefined reference to `__udivdi3'
qcom_stats.c:(.text+0x8a0): undefined reference to `qmp_get'
qcom_stats.c:(.text.qcom_ddr_stats_show+0x14c): undefined reference to 
`__udivdi3'

Unverified Error/Warning (likely false positive, please contact us if 
interested):

drivers/gpu/drm/i915/display/intel_fbdev_fb.c:111 intel_fbdev_fb_fill_info() 
error: uninitialized symbol 'vaddr'.

Error/Warning ids grouped by kconfigs:

gcc_recent_errors
|-- alpha-randconfig-r013-20211213
|   |-- (.init.text):undefined-reference-to-__auxiliary_driver_register
|   |-- (.text):undefined-reference-to-auxiliary_device_init
|   |-- 
alpha-linux-ld:(.init.text):undefined-reference-to-__auxiliary_driver_register
|   |-- alpha-linux-ld:(.text):undefined-reference-to-__auxiliary_device_add
|   `-- alpha-linux-ld:(.text):undefined-reference-to-auxiliary_device_init
|-- arc-randconfig-c031-20221114
|   `-- 
drivers-media-i2c-saa6752hs.c:error:implicit-declaration-of-function-v4l2_subdev_state_get_format
|-- arm-allyesconfig
|   `-- qcom_stats.c:(.text):undefined-reference-to-__aeabi_uldivmod
|-- arm64-randconfig-r034-20230701
|   |-- aarch64-linux-ld:qcom_stats.c:(.text):undefined-reference-to-qmp_send
|   |-- qcom_stats.c:(.text):undefined-reference-to-qmp_get
|   `-- qcom_stats.c:(.text):undefined-reference-to-qmp_send
|-- i386-randconfig-061-20231205
|   `-- 
lib-zstd-compress-zstd_fast.c:sparse:sparse:Using-plain-integer-as-NULL-pointer
|-- i386-randconfig-063-20231205
|   `-- 
lib-zstd-compress-zstd_fast.c:sparse:sparse:Using-plain-integer-as-NULL-pointer
|-- i386-randconfig-141-20231205
|   |-- block-bdev.c-bdev_open_by_dev()-warn:possible-memory-leak-of-handle
|   |-- 
drivers-gpu-drm-amd-amdgpu-amdgpu_connectors.c-amdgpu_connector_dvi_detect()-warn:inconsistent-indenting
|   |-- 
drivers-gpu-drm-amd-amdgpu-amdgpu_ras.c-amdgpu_ras_query_error_status_helper()-error:we-previously-assumed-info-could-be-null-(see-line-)
|   |-- 
drivers-gpu-drm-drm_gpuvm.c-drm_gpuvm_exec_lock_range()-error:uninitialized-symbol-ret-.
|   |-- 
drivers-hwtracing-stm-core.c-stm_register_device()-error:double-free-of-stm
|   |-- 
fs-bcachefs-btree_update_interior.c-bch2_btree_update_start()-warn:inconsistent-returns-c-gc_lock-.
|   |-- 
fs-bcachefs-btree_write_buffer.c-bch2_btree_write_buffer_flush_locked()-error:we-previously-assumed-iter.path-could-be-null-(see-line-)
|   |-- 
fs-bcachefs-recovery.c-bch2_journal_replay()-error:uninitialized-symbol-ret-.
|   |-- 

Re: [Intel-gfx] [PATCH 1/3] drm: Add Adaptive Sync SDP logging

2023-11-23 Thread kernel test robot
Hi Mitul,

kernel test robot noticed the following build warnings:

[auto build test WARNING on drm-tip/drm-tip]

url:
https://github.com/intel-lab-lkp/linux/commits/Mitul-Golani/drm-Add-Adaptive-Sync-SDP-logging/20231123-220931
base:   git://anongit.freedesktop.org/drm/drm-tip drm-tip
patch link:
https://lore.kernel.org/r/20231123140244.4183869-2-mitulkumar.ajitkumar.golani%40intel.com
patch subject: [Intel-gfx] [PATCH 1/3] drm: Add Adaptive Sync SDP logging
config: x86_64-allyesconfig 
(https://download.01.org/0day-ci/archive/20231124/202311241251.zxizrjrp-...@intel.com/config)
compiler: clang version 16.0.4 (https://github.com/llvm/llvm-project.git 
ae42196bc493ffe877a7e3dff8be32035dea4d07)
reproduce (this is a W=1 build): 
(https://download.01.org/0day-ci/archive/20231124/202311241251.zxizrjrp-...@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 
| Closes: 
https://lore.kernel.org/oe-kbuild-all/202311241251.zxizrjrp-...@intel.com/

All warnings (new ones prefixed by >>):

>> drivers/gpu/drm/display/drm_dp_helper.c:2927:36: warning: format specifies 
>> type 'char *' but the argument has type 'u16' (aka 'unsigned short') 
>> [-Wformat]
   DP_SDP_LOG("target_rr: %s\n", async->target_rr);
  ~~ ^~~~
  %hu
   drivers/gpu/drm/display/drm_dp_helper.c:2923:60: note: expanded from macro 
'DP_SDP_LOG'
   #define DP_SDP_LOG(fmt, ...) dev_printk(level, dev, fmt, ##__VA_ARGS__)
   ~~~^~~
   include/linux/dev_printk.h:129:34: note: expanded from macro 'dev_printk'
   _dev_printk(level, dev, fmt, ##__VA_ARGS__);\
   ~~~^~~
   1 warning generated.


vim +2927 drivers/gpu/drm/display/drm_dp_helper.c

  2919  
  2920  void drm_dp_as_sdp_log(const char *level, struct device *dev,
  2921 const struct drm_dp_as_sdp *async)
  2922  {
  2923  #define DP_SDP_LOG(fmt, ...) dev_printk(level, dev, fmt, ##__VA_ARGS__)
  2924  DP_SDP_LOG("DP SDP: %s, revision %u, length %u\n", "VSC",
  2925 async->revision, async->length);
  2926  DP_SDP_LOG("vmin: %d vmax: %d\n", async->vmin, async->vmax);
> 2927  DP_SDP_LOG("target_rr: %s\n", async->target_rr);
  2928  DP_SDP_LOG("duration_incr_ms: %u\n", 
async->duration_incr_ms);
  2929  DP_SDP_LOG("duration_decr_ms: %u\n", 
async->duration_decr_ms);
  2930  DP_SDP_LOG("operation_mode: %u\n", async->operation_mode);
  2931  #undef DP_SDP_LOG
  2932  }
  2933  EXPORT_SYMBOL(drm_dp_as_sdp_log);
  2934  

-- 
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki


Re: [Intel-gfx] [PATCH 1/3] drm: Add Adaptive Sync SDP logging

2023-11-23 Thread kernel test robot
Hi Mitul,

kernel test robot noticed the following build warnings:

[auto build test WARNING on drm-tip/drm-tip]

url:
https://github.com/intel-lab-lkp/linux/commits/Mitul-Golani/drm-Add-Adaptive-Sync-SDP-logging/20231123-220931
base:   git://anongit.freedesktop.org/drm/drm-tip drm-tip
patch link:
https://lore.kernel.org/r/20231123140244.4183869-2-mitulkumar.ajitkumar.golani%40intel.com
patch subject: [Intel-gfx] [PATCH 1/3] drm: Add Adaptive Sync SDP logging
config: x86_64-defconfig 
(https://download.01.org/0day-ci/archive/20231124/202311241136.tl5styqx-...@intel.com/config)
compiler: gcc-11 (Debian 11.3.0-12) 11.3.0
reproduce (this is a W=1 build): 
(https://download.01.org/0day-ci/archive/20231124/202311241136.tl5styqx-...@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 
| Closes: 
https://lore.kernel.org/oe-kbuild-all/202311241136.tl5styqx-...@intel.com/

All warnings (new ones prefixed by >>):

   In file included from include/linux/device.h:15,
from include/linux/backlight.h:12,
from drivers/gpu/drm/display/drm_dp_helper.c:23:
   drivers/gpu/drm/display/drm_dp_helper.c: In function 'drm_dp_as_sdp_log':
>> drivers/gpu/drm/display/drm_dp_helper.c:2927:20: warning: format '%s' 
>> expects argument of type 'char *', but argument 4 has type 'int' [-Wformat=]
2927 | DP_SDP_LOG("target_rr: %s\n", async->target_rr);
 |^  
 ||
 |int
   include/linux/dev_printk.h:129:41: note: in definition of macro 'dev_printk'
 129 | _dev_printk(level, dev, fmt, ##__VA_ARGS__); 
   \
 | ^~~
   drivers/gpu/drm/display/drm_dp_helper.c:2927:9: note: in expansion of macro 
'DP_SDP_LOG'
2927 | DP_SDP_LOG("target_rr: %s\n", async->target_rr);
 | ^~
   drivers/gpu/drm/display/drm_dp_helper.c:2927:37: note: format string is 
defined here
2927 | DP_SDP_LOG("target_rr: %s\n", async->target_rr);
 |~^
 | |
 | char *
 |%d


vim +2927 drivers/gpu/drm/display/drm_dp_helper.c

  2919  
  2920  void drm_dp_as_sdp_log(const char *level, struct device *dev,
  2921 const struct drm_dp_as_sdp *async)
  2922  {
  2923  #define DP_SDP_LOG(fmt, ...) dev_printk(level, dev, fmt, ##__VA_ARGS__)
  2924  DP_SDP_LOG("DP SDP: %s, revision %u, length %u\n", "VSC",
  2925 async->revision, async->length);
  2926  DP_SDP_LOG("vmin: %d vmax: %d\n", async->vmin, async->vmax);
> 2927  DP_SDP_LOG("target_rr: %s\n", async->target_rr);
  2928  DP_SDP_LOG("duration_incr_ms: %u\n", 
async->duration_incr_ms);
  2929  DP_SDP_LOG("duration_decr_ms: %u\n", 
async->duration_decr_ms);
  2930  DP_SDP_LOG("operation_mode: %u\n", async->operation_mode);
  2931  #undef DP_SDP_LOG
  2932  }
  2933  EXPORT_SYMBOL(drm_dp_as_sdp_log);
  2934  

-- 
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki


Re: [Intel-gfx] [PATCH] drm/ttm: replace busy placement with flags v3

2023-11-22 Thread kernel test robot
Hi Somalapuram,

kernel test robot noticed the following build warnings:

[auto build test WARNING on drm-tip/drm-tip]

url:
https://github.com/intel-lab-lkp/linux/commits/Somalapuram-Amaranath/drm-ttm-replace-busy-placement-with-flags-v3/20231113-190252
base:   git://anongit.freedesktop.org/drm/drm-tip drm-tip
patch link:
https://lore.kernel.org/r/20231113110016.462621-1-Amaranath.Somalapuram%40amd.com
patch subject: [Intel-gfx] [PATCH] drm/ttm: replace busy placement with flags v3
config: i386-randconfig-061-20231123 
(https://download.01.org/0day-ci/archive/20231123/202311231106.fulszizp-...@intel.com/config)
compiler: gcc-12 (Debian 12.2.0-14) 12.2.0
reproduce (this is a W=1 build): 
(https://download.01.org/0day-ci/archive/20231123/202311231106.fulszizp-...@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 
| Closes: 
https://lore.kernel.org/oe-kbuild-all/202311231106.fulszizp-...@intel.com/

sparse warnings: (new ones prefixed by >>)
>> drivers/gpu/drm/vmwgfx/vmwgfx_ttm_buffer.c:77:22: sparse: sparse: symbol 
>> 'vmw_vram_sys_placement' was not declared. Should it be static?
   drivers/gpu/drm/vmwgfx/vmwgfx_ttm_buffer.c:101:22: sparse: sparse: symbol 
'vmw_pt_sys_placement' was not declared. Should it be static?
>> drivers/gpu/drm/vmwgfx/vmwgfx_ttm_buffer.c:120:22: sparse: sparse: symbol 
>> 'vmw_srf_placement' was not declared. Should it be static?
>> drivers/gpu/drm/vmwgfx/vmwgfx_ttm_buffer.c:144:22: sparse: sparse: symbol 
>> 'vmw_nonfixed_placement' was not declared. Should it be static?

vim +/vmw_vram_sys_placement +77 drivers/gpu/drm/vmwgfx/vmwgfx_ttm_buffer.c

76  
  > 77  struct ttm_placement vmw_vram_sys_placement = {
78  .num_placement = 2,
79  .placement = vram_sys_placement_flags,
80  };
81  
82  static const struct ttm_place sys_placement_flags = {
83  .fpfn = 0,
84  .lpfn = 0,
85  .mem_type = TTM_PL_SYSTEM,
86  .flags = 0
87  };
88  
89  struct ttm_placement vmw_sys_placement = {
90  .num_placement = 1,
91  .placement = _placement_flags,
92  };
93  
94  static const struct ttm_place vmw_sys_placement_flags = {
95  .fpfn = 0,
96  .lpfn = 0,
97  .mem_type = VMW_PL_SYSTEM,
98  .flags = 0
99  };
   100  
   101  struct ttm_placement vmw_pt_sys_placement = {
   102  .num_placement = 1,
   103  .placement = _sys_placement_flags,
   104  };
   105  
   106  static const struct ttm_place gmr_vram_placement_flags[] = {
   107  {
   108  .fpfn = 0,
   109  .lpfn = 0,
   110  .mem_type = VMW_PL_GMR,
   111  .flags = 0
   112  }, {
   113  .fpfn = 0,
   114  .lpfn = 0,
   115  .mem_type = TTM_PL_VRAM,
   116  .flags = TTM_PL_FLAG_BUSY
   117  }
   118  };
   119  
 > 120  struct ttm_placement vmw_srf_placement = {
   121  .num_placement = 2,
   122  .placement = gmr_vram_placement_flags
   123  };
   124  
   125  static const struct ttm_place nonfixed_placement_flags[] = {
   126  {
   127  .fpfn = 0,
   128  .lpfn = 0,
   129  .mem_type = TTM_PL_SYSTEM,
   130  .flags = 0
   131  }, {
   132  .fpfn = 0,
   133  .lpfn = 0,
   134  .mem_type = VMW_PL_GMR,
   135  .flags = TTM_PL_FLAG_IDLE
   136  }, {
   137  .fpfn = 0,
   138  .lpfn = 0,
   139  .mem_type = VMW_PL_MOB,
   140  .flags = TTM_PL_FLAG_IDLE
   141  }
   142  };
   143  
 > 144  struct ttm_placement vmw_nonfixed_placement = {
   145  .num_placement = 3,
   146  .placement = nonfixed_placement_flags,
   147  };
   148  

-- 
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki


[Intel-gfx] [drm-intel:for-linux-next-gt 1/6] drivers/gpu/drm/i915/i915_drm_client.h:81:1: error: non-void function does not return a value

2023-11-22 Thread kernel test robot
tree:   git://anongit.freedesktop.org/drm-intel for-linux-next-gt
head:   5032c607e886e0c40749a05d37b835c1757d38ff
commit: e4ae85e364fc652ea15d85b0f3a6da304c9b5ce7 [1/6] drm/i915: Add ability 
for tracking buffer objects per client
config: x86_64-buildonly-randconfig-006-20231122 
(https://download.01.org/0day-ci/archive/20231122/202311222102.lhbe6kcx-...@intel.com/config)
compiler: clang version 16.0.4 (https://github.com/llvm/llvm-project.git 
ae42196bc493ffe877a7e3dff8be32035dea4d07)
reproduce (this is a W=1 build): 
(https://download.01.org/0day-ci/archive/20231122/202311222102.lhbe6kcx-...@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 
| Closes: 
https://lore.kernel.org/oe-kbuild-all/202311222102.lhbe6kcx-...@intel.com/

Note: the drm-intel/for-linux-next-gt HEAD 
5032c607e886e0c40749a05d37b835c1757d38ff builds fine.
  It only hurts bisectability.

All errors (new ones prefixed by >>):

   In file included from drivers/gpu/drm/i915/selftests/igt_spinner.c:12:
   In file included from drivers/gpu/drm/i915/selftests/igt_spinner.h:10:
   In file included from drivers/gpu/drm/i915/gem/i915_gem_context.h:12:
   In file included from drivers/gpu/drm/i915/gt/intel_context.h:14:
   In file included from drivers/gpu/drm/i915/i915_drv.h:54:
>> drivers/gpu/drm/i915/i915_drm_client.h:81:1: error: non-void function does 
>> not return a value [-Werror,-Wreturn-type]
   }
   ^
   1 error generated.


vim +81 drivers/gpu/drm/i915/i915_drm_client.h

78  
79  static inline bool i915_drm_client_remove_object(struct 
drm_i915_gem_object *obj)
80  {
  > 81  }
82  #endif
83  

-- 
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki


Re: [Intel-gfx] [PATCH v5 4/4] drm/i915/display: Split i915 specific code away from intel_fb.c

2023-11-21 Thread kernel test robot
Hi Jouni,

kernel test robot noticed the following build errors:

[auto build test ERROR on drm-tip/drm-tip]

url:
https://github.com/intel-lab-lkp/linux/commits/Jouni-H-gander/drm-i915-display-use-intel_bo_to_drm_bo-in-intel_fb-c/20231121-193155
base:   git://anongit.freedesktop.org/drm/drm-tip drm-tip
patch link:
https://lore.kernel.org/r/20231121112729.4191245-5-jouni.hogander%40intel.com
patch subject: [Intel-gfx] [PATCH v5 4/4] drm/i915/display: Split i915 specific 
code away from intel_fb.c
config: i386-allmodconfig 
(https://download.01.org/0day-ci/archive/20231122/202311220447.1vw2sgej-...@intel.com/config)
compiler: clang version 16.0.4 (https://github.com/llvm/llvm-project.git 
ae42196bc493ffe877a7e3dff8be32035dea4d07)
reproduce (this is a W=1 build): 
(https://download.01.org/0day-ci/archive/20231122/202311220447.1vw2sgej-...@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 
| Closes: 
https://lore.kernel.org/oe-kbuild-all/202311220447.1vw2sgej-...@intel.com/

All errors (new ones prefixed by >>):

>> make[7]: *** No rule to make target 
>> 'drivers/gpu/drm/i915/display/intel_fb_bo.o', needed by 
>> 'drivers/gpu/drm/i915/i915.o'.
   make[7]: *** [scripts/Makefile.build:243: 
drivers/gpu/drm/i915/display/intel_fb.o] Error 1
   make[7]: Target 'drivers/gpu/drm/i915/' not remade because of errors.

-- 
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki


Re: [Intel-gfx] [PATCH v5 4/4] drm/i915/display: Split i915 specific code away from intel_fb.c

2023-11-21 Thread kernel test robot
Hi Jouni,

kernel test robot noticed the following build errors:

[auto build test ERROR on drm-tip/drm-tip]

url:
https://github.com/intel-lab-lkp/linux/commits/Jouni-H-gander/drm-i915-display-use-intel_bo_to_drm_bo-in-intel_fb-c/20231121-193155
base:   git://anongit.freedesktop.org/drm/drm-tip drm-tip
patch link:
https://lore.kernel.org/r/20231121112729.4191245-5-jouni.hogander%40intel.com
patch subject: [Intel-gfx] [PATCH v5 4/4] drm/i915/display: Split i915 specific 
code away from intel_fb.c
config: x86_64-allyesconfig 
(https://download.01.org/0day-ci/archive/20231122/202311220315.yzadz5tr-...@intel.com/config)
compiler: clang version 16.0.4 (https://github.com/llvm/llvm-project.git 
ae42196bc493ffe877a7e3dff8be32035dea4d07)
reproduce (this is a W=1 build): 
(https://download.01.org/0day-ci/archive/20231122/202311220315.yzadz5tr-...@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 
| Closes: 
https://lore.kernel.org/oe-kbuild-all/202311220315.yzadz5tr-...@intel.com/

All errors (new ones prefixed by >>):

>> make[7]: *** No rule to make target 
>> 'drivers/gpu/drm/i915/display/intel_fb_bo.o', needed by 
>> 'drivers/gpu/drm/i915/built-in.a'.
   make[7]: *** [scripts/Makefile.build:243: 
drivers/gpu/drm/i915/display/intel_fb.o] Error 1
   make[7]: Target 'drivers/gpu/drm/i915/' not remade because of errors.
--
>> drivers/gpu/drm/i915/display/intel_fb.c:17:10: fatal error: 'intel_fb_bo.h' 
>> file not found
   #include "intel_fb_bo.h"
^~~
   1 error generated.


vim +17 drivers/gpu/drm/i915/display/intel_fb.c

11  
12  #include "i915_drv.h"
13  #include "intel_display.h"
14  #include "intel_display_types.h"
15  #include "intel_dpt.h"
16  #include "intel_fb.h"
  > 17  #include "intel_fb_bo.h"
18  #include "intel_frontbuffer.h"
19  

-- 
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki


[Intel-gfx] [linus:master] [file] 0ede61d858: will-it-scale.per_thread_ops -2.9% regression

2023-11-19 Thread kernel test robot



Hello,

kernel test robot noticed a -2.9% regression of will-it-scale.per_thread_ops on:


commit: 0ede61d8589cc2d93aa78230d74ac58b5b8d0244 ("file: convert to 
SLAB_TYPESAFE_BY_RCU")
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git master

testcase: will-it-scale
test machine: 224 threads 4 sockets Intel(R) Xeon(R) Platinum 8380H CPU @ 
2.90GHz (Cooper Lake) with 192G memory
parameters:

nr_task: 16
mode: thread
test: poll2
cpufreq_governor: performance




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 
| Closes: 
https://lore.kernel.org/oe-lkp/202311201406.2022ca3f-oliver.s...@intel.com


Details are as below:
-->


The kernel config and materials to reproduce are available at:
https://download.01.org/0day-ci/archive/20231120/202311201406.2022ca3f-oliver.s...@intel.com

=
compiler/cpufreq_governor/kconfig/mode/nr_task/rootfs/tbox_group/test/testcase:
  
gcc-12/performance/x86_64-rhel-8.3/thread/16/debian-11.1-x86_64-20220510.cgz/lkp-cpl-4sp2/poll2/will-it-scale

commit: 
  93faf426e3 ("vfs: shave work on failed file open")
  0ede61d858 ("file: convert to SLAB_TYPESAFE_BY_RCU")

93faf426e3cc000c 0ede61d8589cc2d93aa78230d74 
 --- 
 %stddev %change %stddev
 \  |\  
  0.01 ±  9%  +58125.6%   4.17 ±175%  
perf-sched.sch_delay.max.ms.schedule_timeout.rcu_gp_fqs_loop.rcu_gp_kthread.kthread
 89056-2.0%  87309proc-vmstat.nr_slab_unreclaimable
 97958 ±  7%  -9.7%  88449 ±  4%  sched_debug.cpu.avg_idle.stddev
  0.00 ± 12% +24.2%   0.00 ± 17%  
sched_debug.cpu.next_balance.stddev
   6391048-2.9%6208584will-it-scale.16.threads
399440-2.9% 388036will-it-scale.per_thread_ops
   6391048-2.9%6208584will-it-scale.workload
 19.99 ±  4%  -2.2   17.74
perf-profile.calltrace.cycles-pp.fput.do_poll.do_sys_poll.__x64_sys_poll.do_syscall_64
  1.27 ±  5%  +0.82.11 ±  3%  
perf-profile.calltrace.cycles-pp.__fdget.do_poll.do_sys_poll.__x64_sys_poll.do_syscall_64
 32.69 ±  4%  +5.0   37.70
perf-profile.calltrace.cycles-pp.__fget_light.do_poll.do_sys_poll.__x64_sys_poll.do_syscall_64
  0.00   +27.9   27.85
perf-profile.calltrace.cycles-pp.__get_file_rcu.__fget_light.do_poll.do_sys_poll.__x64_sys_poll
 20.00 ±  4%  -2.3   17.75
perf-profile.children.cycles-pp.fput
  0.24 ± 10%  -0.10.18 ±  2%  
perf-profile.children.cycles-pp.syscall_return_via_sysret
  1.48 ±  5%  +0.51.98 ±  3%  
perf-profile.children.cycles-pp.__fdget
 31.85 ±  4%  +6.0   37.86
perf-profile.children.cycles-pp.__fget_light
  0.00   +27.7   27.67
perf-profile.children.cycles-pp.__get_file_rcu
 30.90 ±  4% -20.6   10.35 ±  2%  
perf-profile.self.cycles-pp.__fget_light
 19.94 ±  4%  -2.4   17.53perf-profile.self.cycles-pp.fput
  9.81 ±  4%  -2.47.42 ±  2%  
perf-profile.self.cycles-pp.do_poll
  0.23 ± 11%  -0.10.17 ±  4%  
perf-profile.self.cycles-pp.syscall_return_via_sysret
  0.00   +26.5   26.48
perf-profile.self.cycles-pp.__get_file_rcu
 2.146e+10 ±  2%  +8.5%  2.329e+10 ±  2%  perf-stat.i.branch-instructions
  0.22 ± 14%  -0.00.19 ± 14%  perf-stat.i.branch-miss-rate%
 1.404e+10 ±  2%  +8.7%  1.526e+10 ±  2%  perf-stat.i.dTLB-stores
 70.87-2.3   68.59perf-stat.i.iTLB-load-miss-rate%
   5267608-5.5%4979133 ±  2%  perf-stat.i.iTLB-load-misses
   2102507+5.4%2215725perf-stat.i.iTLB-loads
 18791 ±  3% +10.5%  20757 ±  2%  
perf-stat.i.instructions-per-iTLB-miss
266.67 ±  2%  +6.8% 284.75 ±  2%  perf-stat.i.metric.M/sec
  0.01 ± 10% -10.5%   0.01 ±  5%  perf-stat.overall.MPKI
  0.19-0.00.17
perf-stat.overall.branch-miss-rate%
  0.65-3.1%   0.63perf-stat.overall.cpi
  0.00 ±  4%  -0.00.00 ±  4%  
perf-stat.overall.dTLB-store-miss-rate%
 71.48-2.3   69.21
perf-stat.overall.iTLB-load-miss-rate%
 18757   +10.0%  20629
perf-stat.overall.instructions-per-iTLB-miss
  1.54+3.2%   1.59perf-stat.overall.ipc
   4795147+6.4%5100406perf-stat.overall.path-length
  2.14e+10 ±  2%  +8.5%  2.322e+10 ±  2%  perf-stat.

[Intel-gfx] [drm-intel:for-linux-next-gt 1/6] drivers/gpu/drm/i915/i915_drm_client.h:81:1: warning: non-void function does not return a value

2023-11-19 Thread kernel test robot
tree:   git://anongit.freedesktop.org/drm-intel for-linux-next-gt
head:   3c7a5eb700661e8905ab4e50c2d09c6568125280
commit: e4ae85e364fc652ea15d85b0f3a6da304c9b5ce7 [1/6] drm/i915: Add ability 
for tracking buffer objects per client
config: i386-buildonly-randconfig-006-20231120 
(https://download.01.org/0day-ci/archive/20231120/202311201118.jmt74ras-...@intel.com/config)
compiler: clang version 16.0.4 (https://github.com/llvm/llvm-project.git 
ae42196bc493ffe877a7e3dff8be32035dea4d07)
reproduce (this is a W=1 build): 
(https://download.01.org/0day-ci/archive/20231120/202311201118.jmt74ras-...@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 
| Closes: 
https://lore.kernel.org/oe-kbuild-all/202311201118.jmt74ras-...@intel.com/

All warnings (new ones prefixed by >>):

   warning: unknown warning option '-Wrestrict' [-Wunknown-warning-option]
   warning: unknown warning option '-Wpacked-not-aligned'; did you mean 
'-Wpacked-non-pod'? [-Wunknown-warning-option]
   warning: unknown warning option '-Wformat-overflow'; did you mean 
'-Wshift-overflow'? [-Wunknown-warning-option]
   warning: unknown warning option '-Wformat-truncation' 
[-Wunknown-warning-option]
   warning: unknown warning option '-Wstringop-overflow'; did you mean 
'-Wshift-overflow'? [-Wunknown-warning-option]
   warning: unknown warning option '-Wstringop-truncation'; did you mean 
'-Wstring-concatenation'? [-Wunknown-warning-option]
   In file included from drivers/gpu/drm/i915/i915_debugfs_params.c:11:
   In file included from drivers/gpu/drm/i915/i915_drv.h:54:
>> drivers/gpu/drm/i915/i915_drm_client.h:81:1: warning: non-void function does 
>> not return a value [-Wreturn-type]
   }
   ^
   7 warnings generated.


vim +81 drivers/gpu/drm/i915/i915_drm_client.h

78  
79  static inline bool i915_drm_client_remove_object(struct 
drm_i915_gem_object *obj)
80  {
  > 81  }
82  #endif
83  

-- 
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki


Re: [Intel-gfx] [PATCH v2 03/11] drm/dp_mst: Add kunit tests for drm_dp_get_vc_payload_bw()

2023-11-18 Thread kernel test robot
Hi Imre,

kernel test robot noticed the following build warnings:

[auto build test WARNING on drm-tip/drm-tip]

url:
https://github.com/intel-lab-lkp/linux/commits/Imre-Deak/drm-dp_mst-Store-the-MST-PBN-divider-value-in-fixed-point-format/20231116-212936
base:   git://anongit.freedesktop.org/drm/drm-tip drm-tip
patch link:
https://lore.kernel.org/r/20231116131841.1588781-4-imre.deak%40intel.com
patch subject: [Intel-gfx] [PATCH v2 03/11] drm/dp_mst: Add kunit tests for 
drm_dp_get_vc_payload_bw()
config: hexagon-allyesconfig 
(https://download.01.org/0day-ci/archive/20231119/202311190743.k2u2vxvt-...@intel.com/config)
compiler: clang version 17.0.0 (https://github.com/llvm/llvm-project.git 
4a5ac14ee968ff0ad5d2cc1ffa0299048db4c88a)
reproduce (this is a W=1 build): 
(https://download.01.org/0day-ci/archive/20231119/202311190743.k2u2vxvt-...@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 
| Closes: 
https://lore.kernel.org/oe-kbuild-all/202311190743.k2u2vxvt-...@intel.com/

All warnings (new ones prefixed by >>):

   In file included from drivers/gpu/drm/tests/drm_dp_mst_helper_test.c:10:
   In file included from include/drm/display/drm_dp_mst_helper.h:26:
   In file included from include/drm/display/drm_dp_helper.h:27:
   In file included from include/linux/i2c.h:19:
   In file included from include/linux/regulator/consumer.h:35:
   In file included from include/linux/suspend.h:5:
   In file included from include/linux/swap.h:9:
   In file included from include/linux/memcontrol.h:13:
   In file included from include/linux/cgroup.h:26:
   In file included from include/linux/kernel_stat.h:9:
   In file included from include/linux/interrupt.h:11:
   In file included from include/linux/hardirq.h:11:
   In file included from ./arch/hexagon/include/generated/asm/hardirq.h:1:
   In file included from include/asm-generic/hardirq.h:17:
   In file included from include/linux/irq.h:20:
   In file included from include/linux/io.h:13:
   In file included from arch/hexagon/include/asm/io.h:337:
   include/asm-generic/io.h:547:31: warning: performing pointer arithmetic on a 
null pointer has undefined behavior [-Wnull-pointer-arithmetic]
 547 | val = __raw_readb(PCI_IOBASE + addr);
 |   ~~ ^
   include/asm-generic/io.h:560:61: warning: performing pointer arithmetic on a 
null pointer has undefined behavior [-Wnull-pointer-arithmetic]
 560 | val = __le16_to_cpu((__le16 __force)__raw_readw(PCI_IOBASE + 
addr));
 | ~~ ^
   include/uapi/linux/byteorder/little_endian.h:37:51: note: expanded from 
macro '__le16_to_cpu'
  37 | #define __le16_to_cpu(x) ((__force __u16)(__le16)(x))
 |   ^
   In file included from drivers/gpu/drm/tests/drm_dp_mst_helper_test.c:10:
   In file included from include/drm/display/drm_dp_mst_helper.h:26:
   In file included from include/drm/display/drm_dp_helper.h:27:
   In file included from include/linux/i2c.h:19:
   In file included from include/linux/regulator/consumer.h:35:
   In file included from include/linux/suspend.h:5:
   In file included from include/linux/swap.h:9:
   In file included from include/linux/memcontrol.h:13:
   In file included from include/linux/cgroup.h:26:
   In file included from include/linux/kernel_stat.h:9:
   In file included from include/linux/interrupt.h:11:
   In file included from include/linux/hardirq.h:11:
   In file included from ./arch/hexagon/include/generated/asm/hardirq.h:1:
   In file included from include/asm-generic/hardirq.h:17:
   In file included from include/linux/irq.h:20:
   In file included from include/linux/io.h:13:
   In file included from arch/hexagon/include/asm/io.h:337:
   include/asm-generic/io.h:573:61: warning: performing pointer arithmetic on a 
null pointer has undefined behavior [-Wnull-pointer-arithmetic]
 573 | val = __le32_to_cpu((__le32 __force)__raw_readl(PCI_IOBASE + 
addr));
 | ~~ ^
   include/uapi/linux/byteorder/little_endian.h:35:51: note: expanded from 
macro '__le32_to_cpu'
  35 | #define __le32_to_cpu(x) ((__force __u32)(__le32)(x))
 |   ^
   In file included from drivers/gpu/drm/tests/drm_dp_mst_helper_test.c:10:
   In file included from include/drm/display/drm_dp_mst_helper.h:26:
   In file included from include/drm/display/drm_dp_helper.h:27:
   In file included from include/linux/i2c.h:19:
   In file included from include/linux/regulator/consumer.h:35:
   In file included from include/linux/suspend.h:5:
   In file included from include/linux/swap.h:9:
   In file included from include/linux/memcontrol.h:13:
   In file included from i

Re: [Intel-gfx] [PATCH] drm/i915/gsc: Mark internal GSC engine with reserved uabi class

2023-11-15 Thread kernel test robot
Hi Tvrtko,

kernel test robot noticed the following build warnings:

[auto build test WARNING on drm-intel/for-linux-next-fixes]
[also build test WARNING on drm-tip/drm-tip drm/drm-next 
drm-exynos/exynos-drm-next drm-misc/drm-misc-next linus/master v6.7-rc1 
next-20231115]
[cannot apply to drm-intel/for-linux-next]
[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/Tvrtko-Ursulin/drm-i915-gsc-Mark-internal-GSC-engine-with-reserved-uabi-class/20231115-190507
base:   git://anongit.freedesktop.org/drm-intel for-linux-next-fixes
patch link:
https://lore.kernel.org/r/20231115110216.267138-1-tvrtko.ursulin%40linux.intel.com
patch subject: [PATCH] drm/i915/gsc: Mark internal GSC engine with reserved 
uabi class
config: x86_64-rhel-8.3-rust 
(https://download.01.org/0day-ci/archive/20231116/202311160136.etoh3ghf-...@intel.com/config)
compiler: clang version 16.0.4 (https://github.com/llvm/llvm-project.git 
ae42196bc493ffe877a7e3dff8be32035dea4d07)
reproduce (this is a W=1 build): 
(https://download.01.org/0day-ci/archive/20231116/202311160136.etoh3ghf-...@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 
| Closes: 
https://lore.kernel.org/oe-kbuild-all/202311160136.etoh3ghf-...@intel.com/

All warnings (new ones prefixed by >>):

>> drivers/gpu/drm/i915/gt/intel_engine_user.c:225:26: warning: result of 
>> comparison of constant -1 with expression of type 'u16' (aka 'unsigned 
>> short') is always false [-Wtautological-constant-out-of-range-compare]
   if (engine->uabi_class == I915_NO_UABI_CLASS) {
   ~~ ^  ~~
   drivers/gpu/drm/i915/gt/intel_engine_user.c:243:26: warning: result of 
comparison of constant -1 with expression of type 'u16' (aka 'unsigned short') 
is always false [-Wtautological-constant-out-of-range-compare]
   if (engine->uabi_class == I915_NO_UABI_CLASS)
   ~~ ^  ~~
   2 warnings generated.


vim +225 drivers/gpu/drm/i915/gt/intel_engine_user.c

   203  
   204  void intel_engines_driver_register(struct drm_i915_private *i915)
   205  {
   206  u16 name_instance, other_instance = 0;
   207  struct legacy_ring ring = {};
   208  struct list_head *it, *next;
   209  struct rb_node **p, *prev;
   210  LIST_HEAD(engines);
   211  
   212  sort_engines(i915, );
   213  
   214  prev = NULL;
   215  p = >uabi_engines.rb_node;
   216  list_for_each_safe(it, next, ) {
   217  struct intel_engine_cs *engine =
   218  container_of(it, typeof(*engine), uabi_list);
   219  
   220  if (intel_gt_has_unrecoverable_error(engine->gt))
   221  continue; /* ignore incomplete engines */
   222  
   223  GEM_BUG_ON(engine->class >= ARRAY_SIZE(uabi_classes));
   224  engine->uabi_class = uabi_classes[engine->class];
 > 225  if (engine->uabi_class == I915_NO_UABI_CLASS) {
   226  name_instance = other_instance++;
   227  } else {
   228  GEM_BUG_ON(engine->uabi_class >=
   229 
ARRAY_SIZE(i915->engine_uabi_class_count));
   230  name_instance =
   231  
i915->engine_uabi_class_count[engine->uabi_class]++;
   232  }
   233  engine->uabi_instance = name_instance;
   234  
   235  /*
   236   * Replace the internal name with the final user and 
log facing
   237   * name.
   238   */
   239  engine_rename(engine,
   240intel_engine_class_repr(engine->class),
   241name_instance);
   242  
   243  if (engine->uabi_class == I915_NO_UABI_CLASS)
   244  continue;
   245  
   246  rb_link_node(>uabi_node, prev, p);
   247  rb_insert_color(>uabi_node, 
>uabi_engines);
   248  
   249  GEM_BUG_ON(intel_engine_lookup_user(i915,
   250  engine->uabi_class,
   251  
engine->uabi_instance) != engine);
   252  
   253  /* Fix up the mapping to match default 
execbuf::user_map[] */
   254  add_legacy_ring(, engin

Re: [Intel-gfx] [PATCH 4/4] drm/dp_mst: Fix PBN divider calculation for UHBR rates

2023-11-13 Thread kernel test robot
Hi Imre,

kernel test robot noticed the following build errors:

[auto build test ERROR on drm-tip/drm-tip]

url:
https://github.com/intel-lab-lkp/linux/commits/Imre-Deak/drm-i915-dp-Fix-UHBR-link-M-N-values/20231114-043135
base:   git://anongit.freedesktop.org/drm/drm-tip drm-tip
patch link:
https://lore.kernel.org/r/20231113201110.510724-4-imre.deak%40intel.com
patch subject: [PATCH 4/4] drm/dp_mst: Fix PBN divider calculation for UHBR 
rates
config: i386-randconfig-002-20231114 
(https://download.01.org/0day-ci/archive/20231114/202311140621.sw31vg8m-...@intel.com/config)
compiler: gcc-12 (Debian 12.2.0-14) 12.2.0
reproduce (this is a W=1 build): 
(https://download.01.org/0day-ci/archive/20231114/202311140621.sw31vg8m-...@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 
| Closes: 
https://lore.kernel.org/oe-kbuild-all/202311140621.sw31vg8m-...@intel.com/

All errors (new ones prefixed by >>):

   ld: drivers/gpu/drm/display/drm_dp_mst_topology.o: in function 
`drm_dp_get_vc_payload_bw':
>> drivers/gpu/drm/display/drm_dp_mst_topology.c:3598: undefined reference to 
>> `__udivdi3'


vim +3598 drivers/gpu/drm/display/drm_dp_mst_topology.c

  3570  
  3571  /**
  3572   * drm_dp_get_vc_payload_bw - get the VC payload BW for an MST link
  3573   * @mgr: The _dp_mst_topology_mgr to use
  3574   * @link_rate: link rate in 10kbits/s units
  3575   * @link_lane_count: lane count
  3576   *
  3577   * Calculate the total bandwidth of a MultiStream Transport link. The 
returned
  3578   * value is in units of PBNs/(timeslots/1 MTP). This value can be used 
to
  3579   * convert the number of PBNs required for a given stream to the number 
of
  3580   * timeslots this stream requires in each MTP.
  3581   */
  3582  int drm_dp_get_vc_payload_bw(const struct drm_dp_mst_topology_mgr *mgr,
  3583   int link_rate, int link_lane_count)
  3584  {
  3585  int ret;
  3586  
  3587  if (link_rate == 0 || link_lane_count == 0)
  3588  drm_dbg_kms(mgr->dev, "invalid link rate/lane count: 
(%d / %d)\n",
  3589  link_rate, link_lane_count);
  3590  
  3591  /* See DP v2.0 2.6.4.2, 2.7.6.3 
VCPayload_Bandwidth_for_OneTimeSlotPer_MTP_Allocation */
  3592  /*
  3593   * TODO: Return the value with a higher precision, allowing a 
better
  3594   * slots per MTP allocation granularity. With the current 
returned
  3595   * value +1 slot/MTP can get allocated on UHBR links.
  3596   */
  3597  ret = mul_u32_u32(link_rate * link_lane_count,
> 3598
> drm_dp_bw_channel_coding_efficiency(drm_dp_is_uhbr_rate(link_rate))) /
  3599(100ULL * 8 * 5400);
  3600  
  3601  return ret;
  3602  }
  3603  EXPORT_SYMBOL(drm_dp_get_vc_payload_bw);
  3604  

-- 
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki


Re: [Intel-gfx] [PATCH 4/4] drm/dp_mst: Fix PBN divider calculation for UHBR rates

2023-11-13 Thread kernel test robot
Hi Imre,

kernel test robot noticed the following build errors:

[auto build test ERROR on drm-tip/drm-tip]

url:
https://github.com/intel-lab-lkp/linux/commits/Imre-Deak/drm-i915-dp-Fix-UHBR-link-M-N-values/20231114-043135
base:   git://anongit.freedesktop.org/drm/drm-tip drm-tip
patch link:
https://lore.kernel.org/r/20231113201110.510724-4-imre.deak%40intel.com
patch subject: [PATCH 4/4] drm/dp_mst: Fix PBN divider calculation for UHBR 
rates
config: i386-buildonly-randconfig-002-20231114 
(https://download.01.org/0day-ci/archive/20231114/202311140620.1ghqrb4g-...@intel.com/config)
compiler: gcc-12 (Debian 12.2.0-14) 12.2.0
reproduce (this is a W=1 build): 
(https://download.01.org/0day-ci/archive/20231114/202311140620.1ghqrb4g-...@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 
| Closes: 
https://lore.kernel.org/oe-kbuild-all/202311140620.1ghqrb4g-...@intel.com/

All errors (new ones prefixed by >>):

   ld: drivers/gpu/drm/display/drm_dp_mst_topology.o: in function 
`drm_dp_get_vc_payload_bw':
>> drm_dp_mst_topology.c:(.text+0x931): undefined reference to `__udivdi3'

-- 
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki


Re: [Intel-gfx] [PATCH v2] Remove custom dumb_map_offset implementations in i915 driver

2023-11-12 Thread kernel test robot



Hello,

kernel test robot noticed "BUG:unable_to_handle_page_fault_for_address" on:

commit: a09fc21ac1126b7a5542d2653aa2c319d3bbf5f4 ("[PATCH v2] Remove custom 
dumb_map_offset implementations in i915 driver")
url: 
https://github.com/intel-lab-lkp/linux/commits/Dipam-Turkar/Remove-custom-dumb_map_offset-implementations-in-i915-driver/2023-024912
base: git://anongit.freedesktop.org/drm-intel for-linux-next
patch link: 
https://lore.kernel.org/all/20231110184126.712310-1-dipamt1...@gmail.com/
patch subject: [PATCH v2] Remove custom dumb_map_offset implementations in i915 
driver

in testcase: phoronix-test-suite
version: 
with following parameters:

need_x: true
test: x11perf-1.1.1
option_a: 500px PutImage Square
cpufreq_governor: performance



compiler: gcc-12
test machine: 12 threads 1 sockets Intel(R) Core(TM) i7-8700 CPU @ 3.20GHz 
(Coffee Lake) with 32G memory

(please refer to attached dmesg/kmsg for entire log/backtrace)



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 
| Closes: 
https://lore.kernel.org/oe-lkp/202311131508.7fc7540b-oliver.s...@intel.com


[   53.192823][ T1574] BUG: unable to handle page fault for address: 
0004
[   53.200433][ T1574] #PF: supervisor read access in kernel mode
[   53.206290][ T1574] #PF: error_code(0x) - not-present page
[   53.212150][ T1574] PGD 0 P4D 0
[   53.215393][ T1574] Oops:  [#1] SMP PTI
[   53.219598][ T1574] CPU: 0 PID: 1574 Comm: Xorg Tainted: G S 
6.6.0-rc7-01630-ga09fc21ac112 #1
[   53.229545][ T1574] Hardware name: Dell Inc. OptiPlex 7060/0C96W1, BIOS 
1.4.2 06/11/2019
[ 53.237674][ T1574] RIP: 0010:i915_gem_mmap (arch/x86/include/asm/atomic.h:23 
include/linux/atomic/atomic-arch-fallback.h:444 
include/linux/atomic/atomic-instrumented.h:33 include/linux/refcount.h:147 
include/linux/refcount.h:152 include/linux/refcount.h:227 
include/linux/refcount.h:245 include/linux/kref.h:111 
drivers/gpu/drm/i915/gem/i915_gem_object.h:109 
drivers/gpu/drm/i915/gem/i915_gem_mman.c:1027) i915
[   53.239774][  T633] perf: 'sched' is not a perf-command. See 'perf --help'.
[ 53.243647][ T1574] Code: 00 85 d2 78 46 85 c9 78 42 31 f6 eb 85 48 83 fb 01 
19 c0 83 e0 f7 83 e8 0d e9 f5 fe ff ff 48 8b bb c0 00 00 00 48 85 ff 74 59 <8b> 
17 85 d2 74 53 8d 4a 01 89 d0 f0 0f b1 0f 75 59 85 d2 78 22 85
All code

   0:   00 85 d2 78 46 85   add%al,-0x7ab9872e(%rbp)
   6:   c9  leaveq 
   7:   78 42   js 0x4b
   9:   31 f6   xor%esi,%esi
   b:   eb 85   jmp0xff92
   d:   48 83 fb 01 cmp$0x1,%rbx
  11:   19 c0   sbb%eax,%eax
  13:   83 e0 f7and$0xfff7,%eax
  16:   83 e8 0dsub$0xd,%eax
  19:   e9 f5 fe ff ff  jmpq   0xff13
  1e:   48 8b bb c0 00 00 00mov0xc0(%rbx),%rdi
  25:   48 85 fftest   %rdi,%rdi
  28:   74 59   je 0x83
  2a:*  8b 17   mov(%rdi),%edx  <-- trapping 
instruction
  2c:   85 d2   test   %edx,%edx
  2e:   74 53   je 0x83
  30:   8d 4a 01lea0x1(%rdx),%ecx
  33:   89 d0   mov%edx,%eax
  35:   f0 0f b1 0f lock cmpxchg %ecx,(%rdi)
  39:   75 59   jne0x94
  3b:   85 d2   test   %edx,%edx
  3d:   78 22   js 0x61
  3f:   85  .byte 0x85

Code starting with the faulting instruction
===
   0:   8b 17   mov(%rdi),%edx
   2:   85 d2   test   %edx,%edx
   4:   74 53   je 0x59
   6:   8d 4a 01lea0x1(%rdx),%ecx
   9:   89 d0   mov%edx,%eax
   b:   f0 0f b1 0f lock cmpxchg %ecx,(%rdi)
   f:   75 59   jne0x6a
  11:   85 d2   test   %edx,%edx
  13:   78 22   js 0x37
  15:   85  .byte 0x85
[   53.243649][ T1574] RSP: 0018:c90002117d10 EFLAGS: 00010206
[   53.243650][ T1574] RAX: 0001 RBX: 88810452de98 RCX: 
0010
[   53.243651][ T1574] RDX: 0001 RSI: 77be RDI: 
0004
[   53.243652][ T1574] RBP: 888169b452e0 R08: c90002117cf0 R09: 

[   53.243653][ T1574] R10: 888108e0fe0c R11: 0008 R12: 
745e
[   53.243653][ T1574] R13: 77be R14: 0010 R15: 
888169b452e0
[   53.243654][ T1574] FS:  7f200cf59f00() GS:5360() 
knlGS:
[   53.250665][  T633]
[   53.270183][ T1574] CS:  0010 DS:  ES:  CR0: 800500

[Intel-gfx] [drm-intel:drm-intel-gt-next 6/6] drivers/gpu/drm/i915/i915_drm_client.c:92:9: sparse: sparse: incompatible types in comparison expression (different address spaces):

2023-11-10 Thread kernel test robot
tree:   git://anongit.freedesktop.org/drm-intel drm-intel-gt-next
head:   968853033d8aa4dbb80fbafa6f5d9b6a0ea21272
commit: 968853033d8aa4dbb80fbafa6f5d9b6a0ea21272 [6/6] drm/i915: Implement 
fdinfo memory stats printing
config: x86_64-randconfig-122-2023 
(https://download.01.org/0day-ci/archive/2023/20230610.h0m6ydi5-...@intel.com/config)
compiler: gcc-12 (Debian 12.2.0-14) 12.2.0
reproduce (this is a W=1 build): 
(https://download.01.org/0day-ci/archive/2023/20230610.h0m6ydi5-...@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 
| Closes: 
https://lore.kernel.org/oe-kbuild-all/20230610.h0m6ydi5-...@intel.com/

sparse warnings: (new ones prefixed by >>)
>> drivers/gpu/drm/i915/i915_drm_client.c:92:9: sparse: sparse: incompatible 
>> types in comparison expression (different address spaces):
>> drivers/gpu/drm/i915/i915_drm_client.c:92:9: sparse:struct list_head 
>> [noderef] __rcu *
>> drivers/gpu/drm/i915/i915_drm_client.c:92:9: sparse:struct list_head *
>> drivers/gpu/drm/i915/i915_drm_client.c:92:9: sparse: sparse: incompatible 
>> types in comparison expression (different address spaces):
>> drivers/gpu/drm/i915/i915_drm_client.c:92:9: sparse:struct list_head 
>> [noderef] __rcu *
>> drivers/gpu/drm/i915/i915_drm_client.c:92:9: sparse:struct list_head *

vim +92 drivers/gpu/drm/i915/i915_drm_client.c

72  
73  static void show_meminfo(struct drm_printer *p, struct drm_file *file)
74  {
75  struct drm_memory_stats stats[INTEL_REGION_UNKNOWN] = {};
76  struct drm_i915_file_private *fpriv = file->driver_priv;
77  struct i915_drm_client *client = fpriv->client;
78  struct drm_i915_private *i915 = fpriv->i915;
79  struct drm_i915_gem_object *obj;
80  struct intel_memory_region *mr;
81  struct list_head *pos;
82  unsigned int id;
83  
84  /* Public objects. */
85  spin_lock(>table_lock);
86  idr_for_each_entry(>object_idr, obj, id)
87  obj_meminfo(obj, stats);
88  spin_unlock(>table_lock);
89  
90  /* Internal objects. */
91  rcu_read_lock();
  > 92  list_for_each_rcu(pos, >objects_list) {
93  obj = i915_gem_object_get_rcu(list_entry(pos, 
typeof(*obj),
94   client_link));
95  if (!obj)
96  continue;
97  obj_meminfo(obj, stats);
98  i915_gem_object_put(obj);
99  }
   100  rcu_read_unlock();
   101  
   102  for_each_memory_region(mr, i915, id)
   103  drm_print_memory_stats(p,
   104 [id],
   105 DRM_GEM_OBJECT_RESIDENT |
   106 DRM_GEM_OBJECT_PURGEABLE,
   107 mr->uabi_name);
   108  }
   109  

-- 
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki


Re: [Intel-gfx] [PATCH] Remove custom dumb_map_offset implementations in i915 driver

2023-11-10 Thread kernel test robot
Hi Dipam,

kernel test robot noticed the following build warnings:

[auto build test WARNING on drm-tip/drm-tip]

url:
https://github.com/intel-lab-lkp/linux/commits/Dipam-Turkar/Remove-custom-dumb_map_offset-implementations-in-i915-driver/20231110-185942
base:   git://anongit.freedesktop.org/drm/drm-tip drm-tip
patch link:
https://lore.kernel.org/r/20231110105811.380646-1-dipamt1729%40gmail.com
patch subject: [Intel-gfx] [PATCH] Remove custom dumb_map_offset 
implementations in i915 driver
config: x86_64-randconfig-001-20231110 
(https://download.01.org/0day-ci/archive/2023/20230226.csxs1u1i-...@intel.com/config)
compiler: gcc-7 (Ubuntu 7.5.0-6ubuntu2) 7.5.0
reproduce (this is a W=1 build): 
(https://download.01.org/0day-ci/archive/2023/20230226.csxs1u1i-...@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 
| Closes: 
https://lore.kernel.org/oe-kbuild-all/20230226.csxs1u1i-...@intel.com/

All warnings (new ones prefixed by >>):

   drivers/gpu/drm/i915/gem/i915_gem_mman.c: In function 
'i915_gem_mmap_offset_ioctl':
   drivers/gpu/drm/i915/gem/i915_gem_mman.c:673:9: error: implicit declaration 
of function '__assign_mmap_offset_handle'; did you mean 
'i915_gem_mmap_offset_ioctl'? [-Werror=implicit-function-declaration]
 return __assign_mmap_offset_handle(file, args->handle, type, 
>offset);
^~~
i915_gem_mmap_offset_ioctl
   drivers/gpu/drm/i915/gem/i915_gem_mman.c: In function 'i915_gem_fb_mmap':
   drivers/gpu/drm/i915/gem/i915_gem_mman.c:896:9: error: implicit declaration 
of function 'mmap_offset_attach'; did you mean 'dma_free_attrs'? 
[-Werror=implicit-function-declaration]
  mmo = mmap_offset_attach(obj, mmap_type, NULL);
^~
dma_free_attrs
>> drivers/gpu/drm/i915/gem/i915_gem_mman.c:896:7: warning: assignment makes 
>> pointer from integer without a cast [-Wint-conversion]
  mmo = mmap_offset_attach(obj, mmap_type, NULL);
  ^
   cc1: some warnings being treated as errors


vim +896 drivers/gpu/drm/i915/gem/i915_gem_mman.c

eaee1c085863951 Nirmoy Das2023-04-04  874  
eaee1c085863951 Nirmoy Das2023-04-04  875  int i915_gem_fb_mmap(struct 
drm_i915_gem_object *obj, struct vm_area_struct *vma)
eaee1c085863951 Nirmoy Das2023-04-04  876  {
eaee1c085863951 Nirmoy Das2023-04-04  877   struct drm_i915_private *i915 = 
to_i915(obj->base.dev);
eaee1c085863951 Nirmoy Das2023-04-04  878   struct drm_device *dev = 
>drm;
eaee1c085863951 Nirmoy Das2023-04-04  879   struct i915_mmap_offset *mmo = 
NULL;
eaee1c085863951 Nirmoy Das2023-04-04  880   enum i915_mmap_type mmap_type;
eaee1c085863951 Nirmoy Das2023-04-04  881   struct i915_ggtt *ggtt = 
to_gt(i915)->ggtt;
eaee1c085863951 Nirmoy Das2023-04-04  882  
eaee1c085863951 Nirmoy Das2023-04-04  883   if (drm_dev_is_unplugged(dev))
eaee1c085863951 Nirmoy Das2023-04-04  884   return -ENODEV;
eaee1c085863951 Nirmoy Das2023-04-04  885  
eaee1c085863951 Nirmoy Das2023-04-04  886   /* handle ttm object */
eaee1c085863951 Nirmoy Das2023-04-04  887   if (obj->ops->mmap_ops) {
eaee1c085863951 Nirmoy Das2023-04-04  888   /*
eaee1c085863951 Nirmoy Das2023-04-04  889* ttm fault handler, 
ttm_bo_vm_fault_reserved() uses fake offset
eaee1c085863951 Nirmoy Das2023-04-04  890* to calculate page 
offset so set that up.
eaee1c085863951 Nirmoy Das2023-04-04  891*/
eaee1c085863951 Nirmoy Das2023-04-04  892   vma->vm_pgoff += 
drm_vma_node_start(>base.vma_node);
eaee1c085863951 Nirmoy Das2023-04-04  893   } else {
eaee1c085863951 Nirmoy Das2023-04-04  894   /* handle stolen and 
smem objects */
eaee1c085863951 Nirmoy Das2023-04-04  895   mmap_type = 
i915_ggtt_has_aperture(ggtt) ? I915_MMAP_TYPE_GTT : I915_MMAP_TYPE_WC;
eaee1c085863951 Nirmoy Das2023-04-04 @896   mmo = 
mmap_offset_attach(obj, mmap_type, NULL);
274d4b96b12f78c Dan Carpenter 2023-06-06  897   if (IS_ERR(mmo))
274d4b96b12f78c Dan Carpenter 2023-06-06  898   return 
PTR_ERR(mmo);
eaee1c085863951 Nirmoy Das2023-04-04  899   }
eaee1c085863951 Nirmoy Das2023-04-04  900  
eaee1c085863951 Nirmoy Das2023-04-04  901   /*
eaee1c085863951 Nirmoy Das2023-04-04  902* When we install vm_ops for 
mmap we are too late for
eaee1c085863951 Nirmoy Das2023-04-04  903* the vm_ops->open() which 
increases the ref_count of
eaee1c085863951 Nirmoy Das2023-04-04  904* this obj and then it gets 
decreased by the vm_ops->close().
eaee1c085863951 Nirmoy Das2023-04-04  905* To balance this increase the 
obj ref_count here.
eaee1c085863951 Nirmoy Das2023-04-04  906*/

  1   2   3   4   5   6   7   8   >