make.cross
# save the attached .config to linux build tree
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-9.3.0 make.cross
ARCH=arm64
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot
All errors (new ones prefixed by >>):
>> driv
5b74808b6866933e6adc4d6475429e77c3ccbb23
# save the attached .config to linux build tree
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-9.3.0 make.cross
ARCH=microblaze
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot
All errors (new ones prefixed by >>):
I
appropriate
Reported-by: kernel test robot
All errors (new ones prefixed by >>):
>> kernel/debug/kdb/kdb_support.c:512:41: error: variable 'cpu' is
>> uninitialized when used here [-Werror,-Wuninitialized]
if (!kdb_task_has_cpu(p) || k
Reported-by: kernel test robot
All warnings (new ones prefixed by >>):
>> kernel/debug/kdb/kdb_support.c:512:41: warning: variable 'cpu' is
>> uninitialized when used here [-Wuninitialized]
if (!kdb_task_has_cpu(p) || k
/0day COMPILER=clang make.cross W=1
ARCH=riscv
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot
All warnings (new ones prefixed by >>):
In file included from kernel/debug/kdb/kdb_support.c:21:
In file included from include/linux/highme
/debug/kdb/
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot
All warnings (new ones prefixed by >>):
kernel/debug/kdb/kdb_main.c: In function 'kdb_lsmod':
>> kernel/debug/kdb/kdb_main.c:2027:38: warning: format '%p'
Hi Douglas,
kernel test robot noticed the following build warnings:
[auto build test WARNING on arm64/for-next/core]
[also build test WARNING on tip/irq/core arm-perf/for-next/perf linus/master
v6.5-rc7 next-20230823]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And
Hi Michael,
kernel test robot noticed the following build errors:
[auto build test ERROR on tty/tty-testing]
[also build test ERROR on tty/tty-next tty/tty-linus 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
Hi Michael,
kernel test robot noticed the following build errors:
[auto build test ERROR on tty/tty-testing]
[also build test ERROR on tty/tty-next tty/tty-linus 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
Hi Douglas,
kernel test robot noticed the following build warnings:
[auto build test WARNING on v6.10-rc4]
[also build test WARNING on linus/master next-20240618]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--bas
Hi Florian,
kernel test robot noticed the following build errors:
[auto build test ERROR on tip/master]
[also build test ERROR on tip/x86/core linus/master v6.11-rc3 next-20240815]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to
Hi Florian,
kernel test robot noticed the following build errors:
[auto build test ERROR on tip/master]
[also build test ERROR on tip/x86/core linus/master v6.11-rc3 next-20240816]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to
Hi Marcos,
kernel test robot noticed the following build warnings:
[auto build test WARNING on d0b3b7b22dfa1f4b515fd3a295b3fd958f9e81af]
url:
https://github.com/intel-lab-lkp/linux/commits/Marcos-Paulo-de-Souza/printk-nbcon-Export-console_is_usage-and-other-nbcon-symbols/20250713-131106
Hi Marcos,
kernel test robot noticed the following build errors:
[auto build test ERROR on d0b3b7b22dfa1f4b515fd3a295b3fd958f9e81af]
url:
https://github.com/intel-lab-lkp/linux/commits/Marcos-Paulo-de-Souza/printk-nbcon-Export-console_is_usage-and-other-nbcon-symbols/20250713-131106
base
Hi Fidal,
kernel test robot noticed the following build warnings:
[auto build test WARNING on linus/master]
[also build test WARNING on v6.17-rc4 next-20250904]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--bas
15 matches
Mail list logo
