[+cc linux-pci, Konstantin, since you're thinking about this area, too] The 0-day bot seems to remove mailing lists from the recipient list, which means reports like the one below don't become part of the public email thread and don't get connected to the patch in patchwork. I think this is a problem. For example here are Xuesong's original patch, the patch in patchwork, and the 0-day bot report: https://lore.kernel.org/all/20211027081312.53682-1-xuesong.chen@xxxxxxxxxxxxxxxxx/ https://patchwork.kernel.org/project/linux-pci/patch/20211027081312.53682-1-xuesong.chen@xxxxxxxxxxxxxxxxx/ https://lists.01.org/hyperkitty/list/kbuild-all@xxxxxxxxxxxx/thread/QISVC5TJIHTEMAPX7T7YXOZEDS5CBURY/ Neither the lore link nor the patchwork have any indication that the 0-day bot found a problem. It looks like the 0-day bot sent the report to all the individual recipients from the original patch, but it ADDED these recipients: llvm@xxxxxxxxxxxxxxx kbuild-all@xxxxxxxxxxxx and REMOVED these: linux-pci@xxxxxxxxxxxxxxx linux-acpi@xxxxxxxxxxxxxxx linux-arm-kernel@xxxxxxxxxxxxxxxxxxx linux-kernel@xxxxxxxxxxxxxxx Gmail filed Xuesong's original patch and the 0-day report as spam. That's a problem on my end, but the bigger problem is that I work from the patchwork queue, which has no indication of the problem. I'm sure you have a reason for removing the mailing lists. Should we revisit that? Should I be approaching this a different way? If a *person* responds to a patch on the list, I expect a reply-all so the response becomes part of the thread. Why should the 0-day bot be different? I added linux-pci to cc, but since the 0-day report didn't go to the list, I don't think this message will be threaded correctly on lore. It should be part of https://lore.kernel.org/all/20211027081035.53370-1-xuesong.chen@xxxxxxxxxxxxxxxxx/ On Thu, Oct 28, 2021 at 06:46:16AM +0800, kernel test robot wrote: > Hi Xuesong, > > Thank you for the patch! Perhaps something to improve: > > [auto build test WARNING on helgaas-pci/next] > [also build test WARNING on rafael-pm/linux-next tip/x86/core arm64/for-next/core v5.15-rc7 next-20211027] > [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] > > url: https://github.com/0day-ci/linux/commits/Xuesong-Chen/PCI-MCFG-Consolidate-the-separate-PCI-MCFG-table-entry-list/20211027-171229 > base: https://git.kernel.org/pub/scm/linux/kernel/git/helgaas/pci.git next > config: x86_64-randconfig-s022-20211027 (attached as .config) > compiler: gcc-9 (Debian 9.3.0-22) 9.3.0 > reproduce: > # apt-get install sparse > # sparse version: v0.6.4-dirty > # https://github.com/0day-ci/linux/commit/8fce66d9da6f8e55c5cf0dda4a13dba6bd51492d > git remote add linux-review https://github.com/0day-ci/linux > git fetch --no-tags linux-review Xuesong-Chen/PCI-MCFG-Consolidate-the-separate-PCI-MCFG-table-entry-list/20211027-171229 > git checkout 8fce66d9da6f8e55c5cf0dda4a13dba6bd51492d > # save the attached .config to linux build tree > make W=1 C=1 CF='-fdiagnostic-prefix -D__CHECK_ENDIAN__' O=build_dir ARCH=x86_64 SHELL=/bin/bash drivers/acpi/apei/ > > If you fix the issue, kindly add following tag as appropriate > Reported-by: kernel test robot <lkp@xxxxxxxxx> > > > sparse warnings: (new ones prefixed by >>) > >> drivers/acpi/apei/apei-base.c:453:5: sparse: sparse: symbol 'remove_quirk_mcfg_res' was not declared. Should it be static? > drivers/acpi/apei/apei-base.c:804:12: sparse: sparse: symbol 'arch_apei_enable_cmcff' was not declared. Should it be static? > drivers/acpi/apei/apei-base.c:811:13: sparse: sparse: symbol 'arch_apei_report_mem_error' was not declared. Should it be static? > > Please review and possibly fold the followup patch. > > --- > 0-DAY CI Kernel Test Service, Intel Corporation > https://lists.01.org/hyperkitty/list/kbuild-all@xxxxxxxxxxxx
