Re: [PATCH] gcc-plugins: Use swap() to simplify code

Hi Liao, kernel test robot noticed the following build errors: [auto build test ERROR on kees/for-next/hardening] [also build test ERROR on kees/for-next/kspp kees/for-next/pstore linus/master v6.16 next-20250806] [If your patch is applied to the wrong git tree, kindly drop us a note. And when

Re: [PATCH 3/3] ext4: refactor the inline directory conversion and new directory codepaths

Hi Theodore, kernel test robot noticed the following build warnings: [auto build test WARNING on tytso-ext4/dev] [also build test WARNING on linus/master v6.16-rc5 next-20250711] [If your patch is applied to the wrong git tree, kindly drop us a note. And when submitting patch, we suggest to use

Re: [PATCH v16 3/5] arm64: Kconfig.platforms: Add config for Marvell PXA1908 platform

Hi Duje, kernel test robot noticed the following build warnings: [auto build test WARNING on d7b8f8e20813f0179d8ef519541a3527e7661d3a] url: https://github.com/intel-lab-lkp/linux/commits/Duje-Mihanovi/dt-bindings-mmc-sdhci-pxa-restrict-pinctrl-to-pxav1/20250709-011510 base

Re: [PATCH 2/3] printk: kunit: support offstack cpumask

Hi Petr, kernel test robot noticed the following build errors: [auto build test ERROR on linux-next/master] [cannot apply to linus/master v6.16-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 doc

Re: [PATCH][next] fortify: add branch hints on unlikely fortify_panic paths

Hi Colin, kernel test robot noticed the following build warnings: [auto build test WARNING on kees/for-next/hardening] [also build test WARNING on kees/for-next/pstore kees/for-next/kspp linus/master v6.16-rc3 next-20250626] [If your patch is applied to the wrong git tree, kindly drop us a note

Re: [PATCH][next] fortify: add branch hints on unlikely fortify_panic paths

Hi Colin, kernel test robot noticed the following build errors: [auto build test ERROR on kees/for-next/hardening] [also build test ERROR on kees/for-next/pstore kees/for-next/kspp linus/master v6.16-rc3 next-20250626] [If your patch is applied to the wrong git tree, kindly drop us a note. And

Re: [PATCH] ACPI / sysfs: Replace deprecated and unsafe functions with sysfs_emit

Hello, kernel test robot noticed "WARNING:at_fs/sysfs/file.c:#sysfs_emit" on: commit: 74191212ddb1a82ed54ddd75fcd820f3df79abef ("[PATCH] ACPI / sysfs: Replace deprecated and unsafe functions with sysfs_emit") url: https://github.com/intel-lab-lkp/linux/commits/Brah

Re: [PATCH 09/11] power: supply: qcom_smbx: add smb5 support

Hi Casey, kernel test robot noticed the following build warnings: [auto build test WARNING on bc6e0ba6c9bafa6241b05524b9829808056ac4ad] url: https://github.com/intel-lab-lkp/linux/commits/Casey-Connolly/dt-bindings-power-supply-qcom-pmi89980-charger-add-pm8150b-and-7250b/20250619-230137

Re: [PATCH] panic: improve panic output from Rust panics

Hi Alice, kernel test robot noticed the following build errors: [auto build test ERROR on 19272b37aa4f83ca52bdf9c16d5d81bdd1354494] url: https://github.com/intel-lab-lkp/linux/commits/Alice-Ryhl/panic-improve-panic-output-from-Rust-panics/20250619-231923 base

Re: [PATCH v7 06/10] gpio: aggregator: export symbols of the GPIO forwarder library

Hi Thomas, kernel test robot noticed the following build warnings: [auto build test WARNING on d9946fe286439c2aeaa7953b8c316efe5b83d515] url: https://github.com/intel-lab-lkp/linux/commits/Thomas-Richard/gpiolib-add-support-to-register-sparse-pin-range/20250609-175445 base

Re: [PATCH v9 4/5] rust: add find_bit_benchmark_rust module.

Hi Burak, kernel test robot noticed the following build errors: [auto build test ERROR on akpm-mm/mm-nonmm-unstable] [also build test ERROR on kees/for-next/hardening kees/for-next/pstore kees/for-next/kspp linus/master v6.15] [cannot apply to rust/rust-next next-20250527] [If your patch is

Re: [PATCH] x86: string_32.h: Provide basic sanity checks for fallback memcpy()

Hi Kees, kernel test robot noticed the following build errors: [auto build test ERROR on tip/master] [also build test ERROR on tip/x86/core kees/for-next/pstore kees/for-next/kspp linus/master v6.15-rc7 next-20250523] [If your patch is applied to the wrong git tree, kindly drop us a note. And

Re: [PATCH] x86: string_32.h: Provide basic sanity checks for fallback memcpy()

Hi Kees, kernel test robot noticed the following build warnings: [auto build test WARNING on tip/master] [also build test WARNING on tip/x86/core kees/for-next/pstore kees/for-next/kspp linus/master v6.15-rc7 next-20250523] [If your patch is applied to the wrong git tree, kindly drop us a note

Re: [PATCH v3 08/12] reset: rzg2l-usbphy-ctrl: Add support for USB PWRRDY signal

Hi Claudiu, kernel test robot noticed the following build errors: [auto build test ERROR on next-20250521] [cannot apply to geert-renesas-devel/next pza/reset/next robh/for-next linus/master pza/imx-drm/next v6.15-rc7 v6.15-rc6 v6.15-rc5 v6.15-rc7] [If your patch is applied to the wrong git

Re: [PATCH v4 2/2] pinctrl: eswin: Add EIC7700 pinctrl driver

Hi Yulin, kernel test robot noticed the following build errors: [auto build test ERROR on linusw-pinctrl/devel] [also build test ERROR on linusw-pinctrl/for-next robh/for-next linus/master v6.15-rc7 next-20250521] [If your patch is applied to the wrong git tree, kindly drop us a note. And when

Re: [PATCH v8 3/5] rust: add bitmap API.

Hi Burak, kernel test robot noticed the following build errors: [auto build test ERROR on rust/rust-next] [also build test ERROR on akpm-mm/mm-nonmm-unstable kees/for-next/hardening kees/for-next/pstore kees/for-next/kspp linus/master v6.15-rc7] [cannot apply to next-20250516] [If your patch is

Re: [PATCH v2] ext4: replace strcpy() with '.' assignment

Hi Ethan, kernel test robot noticed the following build errors: [auto build test ERROR on 5723cc3450bccf7f98f227b9723b5c9f6b3af1c5] url: https://github.com/intel-lab-lkp/linux/commits/Ethan-Carter-Edwards/ext4-replace-strcpy-with-assignment/20250519-115601 base

Re: [PATCH v2] ext4: replace strcpy() with '.' assignment

Hi Ethan, kernel test robot noticed the following build warnings: [auto build test WARNING on 5723cc3450bccf7f98f227b9723b5c9f6b3af1c5] url: https://github.com/intel-lab-lkp/linux/commits/Ethan-Carter-Edwards/ext4-replace-strcpy-with-assignment/20250519-115601 base

Re: [PATCH v2] printk: ringbuffer: Add KUnit test

Hi Thomas, kernel test robot noticed the following build errors: [auto build test ERROR on 0af2f6be1b4281385b618cb86ad946eded089ac8] url: https://github.com/intel-lab-lkp/linux/commits/Thomas-Wei-schuh/printk-ringbuffer-Add-KUnit-test/20250506-200133 base

Re: [PATCH 2/2] pinctrl: eswin: Add eic7700 pinctrl driver

Hi luyulin, kernel test robot noticed the following build errors: [auto build test ERROR on linusw-pinctrl/devel] [also build test ERROR on linusw-pinctrl/for-next robh/for-next linus/master v6.15-rc5 next-20250507] [If your patch is applied to the wrong git tree, kindly drop us a note. And

Re: [PATCH][next] fanotify: Avoid a couple of -Wflex-array-member-not-at-end warnings

Hi Gustavo, kernel test robot noticed the following build warnings: [auto build test WARNING on jack-fs/fsnotify] [also build test WARNING on linus/master v6.15-rc5 next-20250507] [If your patch is applied to the wrong git tree, kindly drop us a note. And when submitting patch, we suggest to use

Re: [PATCH v5 01/12] gpiolib: add support to register sparse pin range

Hi Thomas, kernel test robot noticed the following build errors: [auto build test ERROR on 8a834b0ac9ceb354a6e0b8cf5b363edca8221bdd] url: https://github.com/intel-lab-lkp/linux/commits/Thomas-Richard/gpiolib-add-support-to-register-sparse-pin-range/20250506-232604 base

Re: [PATCH 2/3] lib/tests: Add randstruct KUnit test

Hi Kees, kernel test robot noticed the following build warnings: [auto build test WARNING on kees/for-next/hardening] [also build test WARNING on linus/master v6.15-rc3 next-20250424] [cannot apply to akpm-mm/mm-nonmm-unstable soc/for-next] [If your patch is applied to the wrong git tree, kindly

Re: [PATCH 2/3] lib/tests: Add randstruct KUnit test

Hi Kees, kernel test robot noticed the following build errors: [auto build test ERROR on kees/for-next/hardening] [also build test ERROR on linus/master v6.15-rc3 next-20250424] [cannot apply to akpm-mm/mm-nonmm-unstable soc/for-next] [If your patch is applied to the wrong git tree, kindly drop

Re: [PATCH 2/3] lib/tests: Add randstruct KUnit test

Hi Kees, kernel test robot noticed the following build warnings: [auto build test WARNING on kees/for-next/hardening] [also build test WARNING on linus/master v6.15-rc3 next-20250424] [cannot apply to akpm-mm/mm-nonmm-unstable soc/for-next] [If your patch is applied to the wrong git tree, kindly

Re: [PATCH net-next v4 3/8] mfd: Add Microchip ZL3073x support

Hi Ivan, kernel test robot noticed the following build warnings: [auto build test WARNING on net-next/main] url: https://github.com/intel-lab-lkp/linux/commits/Ivan-Vecera/dt-bindings-dpll-Add-DPLL-device-and-pin/20250424-235141 base: net-next/main patch link: https://lore.kernel.org

[linus:master] [ubsan/overflow] ed2b548f10: INFO:task_blocked_for_more_than#seconds

ailed :999 27% 269:998 dmesg.boot_failures so we still make out this report FYI what we observed in our tests. kernel test robot noticed "INFO:task_blocked_for_more_than#seconds" on: commit: ed2b548f1017586c44f50654ef9febb42d491f31 ("ubsan/overf

Re: [PATCH v2 04/14] mfd: zl3073x: Register itself as devlink device

Hi Ivan, kernel test robot noticed the following build warnings: [auto build test WARNING on robh/for-next] [also build test WARNING on linus/master v6.15-rc2 next-20250417] [cannot apply to lee-mfd/for-mfd-next lee-mfd/for-mfd-fixes horms-ipvs/master] [If your patch is applied to the wrong git

Re: [PATCH v2 04/14] mfd: zl3073x: Register itself as devlink device

Hi Ivan, kernel test robot noticed the following build warnings: [auto build test WARNING on robh/for-next] [also build test WARNING on linus/master v6.15-rc2 next-20250417] [cannot apply to lee-mfd/for-mfd-next lee-mfd/for-mfd-fixes horms-ipvs/master] [If your patch is applied to the wrong git

Re: [PATCH 1/2] lib/string: Improve strstarts() performance

Hi Zijun, kernel test robot noticed the following build errors: [auto build test ERROR on 0af2f6be1b4281385b618cb86ad946eded089ac8] url: https://github.com/intel-lab-lkp/linux/commits/Zijun-Hu/lib-string-Improve-strstarts-performance/20250407-212519 base

[linux-next:master] [hardening] d70da12453: WARNING:possible_circular_locking_dependency_detected_trinity-main_is_trying_to_acquire_lock:at:__perf_event_task_sched_out_but_task_is_already_holding_loc

set CONFIG_UPROBE_EVENTS=y CONFIG_BPF_EVENTS=y Hello, kernel test robot noticed "WARNING:possible_circular_locking_dependency_detected_trinity-main_is_trying_to_acquire_lock:at:__perf_event_task_sched_out_but_task_is_already_holding_lock:at:raw_spin_rq_lock_nested" o

Re: [PATCH v3] ARM: dts: nexus4: Initial dts

Hi David, kernel test robot noticed the following build errors: [auto build test ERROR on 0a2f889128969dab41861b6e40111aa03dc57014] url: https://github.com/intel-lab-lkp/linux/commits/David-Heidelberg-via-B4-Relay/ARM-dts-nexus4-Initial-dts/20250309-084753 base

Re: [PATCH v1] HID: usbhid: Eliminate recurrent out-of-bounds bug in usbhid_parse()

Hi Terry, kernel test robot noticed the following build warnings: [auto build test WARNING on 58c9bf3363e596d744f56616d407278ef5f97f5a] url: https://github.com/intel-lab-lkp/linux/commits/Terry-Junge/HID-usbhid-Eliminate-recurrent-out-of-bounds-bug-in-usbhid_parse/20250307-130514 base

Re: [PATCH v14 2/4] arm64: Kconfig.platforms: Add config for Marvell PXA1908 platform

Hi Duje, kernel test robot noticed the following build warnings: [auto build test WARNING on 5bc55a333a2f7316b58edc7573e8e893f7acb532] url: https://github.com/intel-lab-lkp/linux/commits/Duje-Mihanovi-via-B4-Relay/dt-bindings-marvell-Document-PXA1908-SoC-and-samsung-coreprimevelte/20250116

Re: [PATCH] fortify: turn strlen() into an inline function using __builtin_constant_p()

Hi Vincent, kernel test robot noticed the following build warnings: [auto build test WARNING on 9d89551994a430b50c4fffcb1e617a057fa76e20] url: https://github.com/intel-lab-lkp/linux/commits/Vincent-Mailhol/fortify-turn-strlen-into-an-inline-function-using-__builtin_constant_p/20250108

Re: [PATCH] fortify: turn strlen() into an inline function using __builtin_constant_p()

Hi Vincent, kernel test robot noticed the following build errors: [auto build test ERROR on 9d89551994a430b50c4fffcb1e617a057fa76e20] url: https://github.com/intel-lab-lkp/linux/commits/Vincent-Mailhol/fortify-turn-strlen-into-an-inline-function-using-__builtin_constant_p/20250108-223159

[linus:master] [fortify] 239d87327d: vm-scalability.throughput 17.3% improvement

Hello, kernel test robot noticed a 17.3% improvement of vm-scalability.throughput on: commit: 239d87327dcd361b0098038995f8908f3296864f ("fortify: Hide run-time copy size from value range tracking") https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git master te

Re: [PATCH 2/2] wifi: cfg80211: simplify cfg80211_mlme_register_mgmt()

Hello, kernel test robot noticed "BUG:sleeping_function_called_from_invalid_context_at_include/linux/sched/mm.h" on: commit: f3ec4051049a8cc013993b615303b283770c6482 ("[PATCH 2/2] wifi: cfg80211: simplify cfg80211_mlme_register_mgmt()") url: https://github.com/intel-l

Re: [PATCH] ovl: Check for NULL OVL_E() results

Hello, kernel test robot noticed "WARNING:at_fs/overlayfs/util.c:#ovl_path_type[overlay]" on: commit: d6b14141241121ff7761dc8dfb33d27284fc5331 ("[PATCH] ovl: Check for NULL OVL_E() results") url: https://github.com/intel-lab-lkp/linux/commits/Kees-Cook/ovl-Check-fo

Re: [PATCH] overflow: improve size_add/mul for 32bit systems

Hi Dan, kernel test robot noticed the following build errors: [auto build test ERROR on kees/for-next/hardening] [also build test ERROR on kees/for-next/pstore kees/for-next/kspp linus/master v6.12 next-20241121] [If your patch is applied to the wrong git tree, kindly drop us a note. And when

Re: [PATCH] overflow: improve size_add/mul for 32bit systems

Hi Dan, kernel test robot noticed the following build warnings: [auto build test WARNING on kees/for-next/hardening] [also build test WARNING on kees/for-next/pstore kees/for-next/kspp linus/master v6.12 next-20241121] [If your patch is applied to the wrong git tree, kindly drop us a note. And

Re: [PATCH] overflow: improve size_add/mul for 32bit systems

Hi Dan, kernel test robot noticed the following build warnings: [auto build test WARNING on kees/for-next/hardening] [also build test WARNING on kees/for-next/pstore kees/for-next/kspp linus/master v6.12 next-20241121] [If your patch is applied to the wrong git tree, kindly drop us a note. And

Re: [PATCH] scsi: Replace zero-length array with flexible array member

Hi Thorsten, kernel test robot noticed the following build errors: [auto build test ERROR on jejb-scsi/for-next] [also build test ERROR on mkp-scsi/for-next linus/master v6.12-rc6 next-20241108] [If your patch is applied to the wrong git tree, kindly drop us a note. And when submitting patch

[linus:master] [ubsan] 557f8c582a: UBSAN:signed-integer-overflow_in_fs/sync.c

his change then to find out the real first bad commits which introduce these issues. just made out below report FYI what we observed in our tests. kernel test robot noticed "UBSAN:signed-integer-overflow_in_fs/sync.c" on: commit: 557f8c582a9ba8abe6aa0fd734b6f342af106b26 ("ubsan

Re: [PATCH 2/2] wifi: ath12k: annotate channel of struct ath12k_wmi_scan_chan_list_arg with __counted_by

Hi Dmitry, kernel test robot noticed the following build errors: [auto build test ERROR on ath/ath-next] [also build test ERROR on wireless-next/main wireless/main linus/master v6.12-rc4 next-20241022] [If your patch is applied to the wrong git tree, kindly drop us a note. And when submitting

Re: [PATCH v1 1/2] mseal: Two fixes for madvise(MADV_DONTNEED) when sealed

Hi, kernel test robot noticed the following build errors: [auto build test ERROR on akpm-mm/mm-everything] [also build test ERROR on linus/master v6.12-rc3 next-20241018] [cannot apply to kees/for-next/pstore kees/for-next/kspp linux/master] [If your patch is applied to the wrong git tree

Re: [PATCH v1 1/2] mseal: Two fixes for madvise(MADV_DONTNEED) when sealed

Hi, kernel test robot noticed the following build errors: [auto build test ERROR on akpm-mm/mm-everything] [also build test ERROR on linus/master v6.12-rc3 next-20241018] [cannot apply to kees/for-next/pstore kees/for-next/kspp linux/master] [If your patch is applied to the wrong git tree

Re: [PATCH] hv: hyperv.h: Annotate vmbus_channel_gpadl_header with __counted_by()

Hi Thorsten, kernel test robot noticed the following build warnings: [auto build test WARNING on kees/for-next/pstore] [also build test WARNING on kees/for-next/kspp linus/master v6.12-rc3 next-20241015] [If your patch is applied to the wrong git tree, kindly drop us a note. And when submitting

Re: [PATCH] acl: Annotate struct posix_acl with __counted_by()

Hello, kernel test robot noticed "WARNING:at_lib/string_helpers.c:#__fortify_report" on: commit: 3d2d832826325210abb9849ee96634bf5a197517 ("[PATCH] acl: Annotate struct posix_acl with __counted_by()") url: https://github.com/intel-lab-lkp/linux/commits/Thorsten-Blum

Re: [PATCH -next] mmc: sdhci-cadence: Annotate struct sdhci_cdns_phy_param with __counted_by()

Hi Hongbo, kernel test robot noticed the following build errors: [auto build test ERROR on next-20240903] url: https://github.com/intel-lab-lkp/linux/commits/Hongbo-Li/mmc-sdhci-cadence-Annotate-struct-sdhci_cdns_phy_param-with-__counted_by/20240904-094207 base: next-20240903 patch link

Re: [PATCH V8 2/2] iio: proximity: aw96103: Add support for aw96103/aw96105 proximity sensor

Hi, kernel test robot noticed the following build errors: [auto build test ERROR on b78b25f69a1dfa79798f684ad34707b1da10a48f] url: https://github.com/intel-lab-lkp/linux/commits/wangshuaijie-awinic-com/dt-bindings-iio-aw96103-Add-bindings-for-aw96103-aw96105-sensor/20240826-130421 base

Re: [PATCH V8 2/2] iio: proximity: aw96103: Add support for aw96103/aw96105 proximity sensor

Hi, kernel test robot noticed the following build warnings: [auto build test WARNING on b78b25f69a1dfa79798f684ad34707b1da10a48f] url: https://github.com/intel-lab-lkp/linux/commits/wangshuaijie-awinic-com/dt-bindings-iio-aw96103-Add-bindings-for-aw96103-aw96105-sensor/20240826-130421 base

Re: [PATCH v2][next] wifi: iwlwifi: mvm: Use __counted_by() and avoid -Wfamnae warnings

Hi Gustavo, kernel test robot noticed the following build errors: [auto build test ERROR on wireless-next/main] [also build test ERROR on wireless/main linus/master v6.11-rc2 next-20240809] [If your patch is applied to the wrong git tree, kindly drop us a note. And when submitting patch, we

Re: [PATCH v2][next] wifi: iwlwifi: mvm: Use __counted_by() and avoid -Wfamnae warnings

Hi Gustavo, kernel test robot noticed the following build errors: [auto build test ERROR on wireless-next/main] [also build test ERROR on wireless/main linus/master v6.11-rc2 next-20240809] [If your patch is applied to the wrong git tree, kindly drop us a note. And when submitting patch, we

[linus:master] [kasan, fortify] 2e577732e8: BUG:KASAN:global-out-of-bounds_in_usb_copy_descriptors

Hello, we noticed this is a fix commit, however, we don't have enough knowledge to determine if new KASAN issue is expected actually after this fix. so we just made this report FYI what we observed in our tests. kernel test robot noticed "BUG:KASAN:glo

Re: [PATCH 1/3] fortify: use if_changed_dep to record header dependency in *.cmd files

Hi Masahiro, kernel test robot noticed the following build errors: [auto build test ERROR on linus/master] [also build test ERROR on v6.10 next-20240716] [cannot apply to akpm-mm/mm-nonmm-unstable kees/for-next/hardening kees/for-next/pstore kees/for-next/kspp] [If your patch is applied to the

Re: [PATCH v2] wifi: mac80211: Avoid address calculations via out of bounds array indexing

Hello, kernel test robot noticed "hwsim.autogo_force_diff_channel.fail" on: commit: f68b86b282be59dcb687700c3b9ede5cd16e36cf ("[PATCH v2] wifi: mac80211: Avoid address calculations via out of bounds array indexing") url: https://github.com/intel-lab-lkp/linux/commits/Ken

Re: [PATCH 1/2] exec: Add KUnit test for bprm_stack_limits()

Hi Kees, kernel test robot noticed the following build errors: [auto build test ERROR on kees/for-next/execve] [also build test ERROR on kees/for-next/pstore kees/for-next/kspp brauner-vfs/vfs.all linus/master vfs-idmapping/for-next v6.9 next-20240520] [If your patch is applied to the wrong git

Re: [PATCH 1/2] exec: Add KUnit test for bprm_stack_limits()

Hi Kees, kernel test robot noticed the following build errors: [auto build test ERROR on kees/for-next/execve] [also build test ERROR on kees/for-next/pstore kees/for-next/kspp brauner-vfs/vfs.all linus/master v6.9 next-20240520] [If your patch is applied to the wrong git tree, kindly drop us a

[linux-next:master] [mm/slab] 7bd230a266: WARNING:at_mm/util.c:#kvmalloc_node_noprof

ow is full report. kernel test robot noticed "WARNING:at_mm/util.c:#kvmalloc_node_noprof" on: commit: 7bd230a26648ac68ab3731ebbc449090f0ac6a37 ("mm/slab: enable slab allocation tagging for kmalloc and friends") https://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git

[linus:master] [fortify] 4ce615e798: kunit.fortify.alloc_size_kmalloc_dynamic_test.fail

Hello, kernel test robot noticed "kunit.fortify.alloc_size_kmalloc_dynamic_test.fail" on: commit: 4ce615e798a752d4431fcc52960478906dec2f0e ("fortify: Provide KUnit counters for failure testing") https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git master [

Re: [PATCH 1/1] arm64: syscall: Direct PRNG kstack randomization

Hi Jeremy, kernel test robot noticed the following build warnings: [auto build test WARNING on arm64/for-next/core] [also build test WARNING on arm/for-next arm/fixes kvmarm/next soc/for-next linus/master v6.8-rc7 next-20240307] [If your patch is applied to the wrong git tree, kindly drop us a

Re: [PATCH v1 8/8] kunit: Add tests for faults

Hi Mickaël, kernel test robot noticed the following build warnings: [auto build test WARNING on d206a76d7d2726f3b096037f2079ce0bd3ba329b] url: https://github.com/intel-lab-lkp/linux/commits/Micka-l-Sala-n/kunit-Run-tests-when-the-kernel-is-fully-setup/20240301-011020 base

Re: [PATCH v1 1/8] kunit: Run tests when the kernel is fully setup

Hi Mickaël, kernel test robot noticed the following build warnings: [auto build test WARNING on d206a76d7d2726f3b096037f2079ce0bd3ba329b] url: https://github.com/intel-lab-lkp/linux/commits/Micka-l-Sala-n/kunit-Run-tests-when-the-kernel-is-fully-setup/20240301-011020 base

Re: [PATCH v1 1/8] kunit: Run tests when the kernel is fully setup

Hi Mickaël, kernel test robot noticed the following build warnings: [auto build test WARNING on d206a76d7d2726f3b096037f2079ce0bd3ba329b] url: https://github.com/intel-lab-lkp/linux/commits/Micka-l-Sala-n/kunit-Run-tests-when-the-kernel-is-fully-setup/20240301-011020 base

[linux-next:master] BUILD REGRESSION e31185ce00a96232308300008db193416ceb9769

tree/branch: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master branch HEAD: e31185ce00a9623230838db193416ceb9769 Add linux-next specific files for 20240222 Error/Warning reports: https://lore.kernel.org/oe-kbuild-all/20240223.h9rfmyj4-...@intel.com https://lore

Re: [PATCH 1/4] arm: ptdump: Rename CONFIG_DEBUG_WX to CONFIG_ARM_DEBUG_WX

Hi Christophe, kernel test robot noticed the following build errors: [auto build test ERROR on powerpc/next] [also build test ERROR on powerpc/fixes s390/features tip/x86/mm linus/master v6.7 next-20240109] [If your patch is applied to the wrong git tree, kindly drop us a note. And when

Re: [PATCH 1/4] arm: ptdump: Rename CONFIG_DEBUG_WX to CONFIG_ARM_DEBUG_WX

Hi Christophe, kernel test robot noticed the following build errors: [auto build test ERROR on powerpc/next] [also build test ERROR on powerpc/fixes s390/features tip/x86/mm linus/master v6.7 next-20240109] [If your patch is applied to the wrong git tree, kindly drop us a note. And when

Re: [PATCH 2/4] arm64, powerpc, riscv, s390, x86: Refactor CONFIG_DEBUG_WX

Hi Christophe, kernel test robot noticed the following build errors: [auto build test ERROR on powerpc/next] [also build test ERROR on powerpc/fixes s390/features tip/x86/mm linus/master v6.7] [cannot apply to next-20240109] [If your patch is applied to the wrong git tree, kindly drop us a note

Re: [PATCH] lib/string: shrink lib/string.i via IWYU

Hi, kernel test robot noticed the following build errors: [auto build test ERROR on 33cc938e65a98f1d29d0a18403dbbee050dcad9a] url: https://github.com/intel-lab-lkp/linux/commits/tanzirh-google-com/lib-string-shrink-lib-string-i-via-IWYU/20231206-050121 base

Re: [PATCH v2 12/18] sysctl: treewide: constify the ctl_table argument of handlers

Hi Thomas, kernel test robot noticed the following build errors: [auto build test ERROR on netfilter-nf/main] [also build test ERROR on akpm-mm/mm-everything linus/master v6.7-rc4] [cannot apply to nf-next/master next-20231205] [If your patch is applied to the wrong git tree, kindly drop us a

Re: [PATCH v2 12/18] sysctl: treewide: constify the ctl_table argument of handlers

Hi Thomas, kernel test robot noticed the following build errors: [auto build test ERROR on netfilter-nf/main] [also build test ERROR on akpm-mm/mm-everything linus/master v6.7-rc4] [cannot apply to nf-next/master next-20231205] [If your patch is applied to the wrong git tree, kindly drop us a

Re: [PATCH 1/2] qnx4: Extract dir entry filename processing into helper

Hi Kees, kernel test robot noticed the following build warnings: [auto build test WARNING on linus/master] [also build test WARNING on v6.7-rc1 next-20231117] [If your patch is applied to the wrong git tree, kindly drop us a note. And when submitting patch, we suggest to use '--bas

Re: [PATCH 1/2] qnx4: Extract dir entry filename processing into helper

Hi Kees, kernel test robot noticed the following build errors: [auto build test ERROR on linus/master] [also build test ERROR on v6.7-rc1 next-20231117] [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 doc

Re: [PATCH] scsi: libfc: replace deprecated strncpy with memcpy

Hi Justin, kernel test robot noticed the following build errors: [auto build test ERROR on ffc253263a1375a65fa6c9f62a893e9767fbebfa] url: https://github.com/intel-lab-lkp/linux/commits/Justin-Stitt/scsi-libfc-replace-deprecated-strncpy-with-memcpy/20231031-063815 base

Re: [PATCH] scsi: libfc: replace deprecated strncpy with memcpy

Hi Justin, kernel test robot noticed the following build warnings: [auto build test WARNING on ffc253263a1375a65fa6c9f62a893e9767fbebfa] url: https://github.com/intel-lab-lkp/linux/commits/Justin-Stitt/scsi-libfc-replace-deprecated-strncpy-with-memcpy/20231031-063815 base

Re: [PATCH] usb: musb: Check requset->buf before use to avoid crash issue

Hi Xingxing, kernel test robot noticed the following build errors: [auto build test ERROR on usb/usb-testing] [also build test ERROR on usb/usb-next usb/usb-linus linus/master v6.6-rc7 next-20231027] [If your patch is applied to the wrong git tree, kindly drop us a note. And when submitting

Re: [PATCH v6 7/9] arm64: Kconfig.platforms: Add config for Marvell PXA1908 platform

Hi Duje, kernel test robot noticed the following build errors: [auto build test ERROR on 94f6f0550c625fab1f373bb86a6669b45e9748b3] url: https://github.com/intel-lab-lkp/linux/commits/Duje-Mihanovi/clk-mmp-Switch-to-use-struct-u32_fract-instead-of-custom-one/20231011-012919 base

Re: [PATCH 1/1] trace: Move readpos from seq_buf to trace_seq

Hi Matthew, kernel test robot noticed the following build warnings: [auto build test WARNING on kees/for-next/pstore] [also build test WARNING on kees/for-next/kspp linus/master v6.6-rc6 next-20231019] [If your patch is applied to the wrong git tree, kindly drop us a note. And when submitting

Re: [PATCH] PCI: pciehp: Prevent child devices from doing RPM on PCIe Link Down

Hi Kai-Heng, kernel test robot noticed the following build warnings: [auto build test WARNING on pci/next] [also build test WARNING on pci/for-linus linus/master v6.6-rc6 next-20231017] [If your patch is applied to the wrong git tree, kindly drop us a note. And when submitting patch, we suggest

Re: [PATCH v4 7/8] soc/tegra: fuse: Add ACPI support for Tegra194 and Tegra234

Hi Kartik, kernel test robot noticed the following build warnings: [auto build test WARNING on tegra/for-next] [also build test WARNING on kees/for-next/hardening akpm-mm/mm-everything linus/master v6.6-rc5 next-20231012] [If your patch is applied to the wrong git tree, kindly drop us a note

[linux-next:master] BUILD REGRESSION 33b64befb1a28bca3f5a9ed9807d2f87e976c63a

tree/branch: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master branch HEAD: 33b64befb1a28bca3f5a9ed9807d2f87e976c63a Add linux-next specific files for 20231004 Error/Warning reports: https://lore.kernel.org/oe-kbuild-all/202309122047.cri9yjrq-...@intel.com https://lore