Hi LKP team, blktests's CONTRIBUTING.md says that blktests patches should be sent either on GitHub, or to linux-block with the "PATCH blktests" subject prefix. I just sent such a patch, and because it was just adding a file, the kernel test robot happily applied and tested it as if it was a kernel patch, which naturally resulted in it finding problems. Maybe the kernel test robot should skip patches starting with "[PATCH blktests]"? n Fri, Mar 31, 2023 at 03:22:28AM +0800, kernel test robot wrote: > Hi Alyssa, > > Thank you for the patch! Perhaps something to improve: > > [auto build test WARNING on linus/master] > [also build test WARNING on v6.3-rc4 next-20230330] > [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/Alyssa-Ross/loop-009-add-test-for-loop-partition-uvents/20230331-001157 > patch link: https://lore.kernel.org/r/20230330160247.16030-1-hi%40alyssa.is > patch subject: [PATCH blktests] loop/009: add test for loop partition uvents > reproduce: > scripts/spdxcheck.py > > If you fix the issue, kindly add following tag where applicable > | Reported-by: kernel test robot <lkp@xxxxxxxxx> > | Link: https://lore.kernel.org/oe-kbuild-all/202303310316.QS2vADHM-lkp@xxxxxxxxx/ > > spdxcheck warnings: (new ones prefixed by >>) > >> tests/loop/009: 2:27 Invalid License ID: GPL-3.0+ > > -- > 0-DAY CI Kernel Test Service > https://github.com/intel/lkp-tests
Attachment:
signature.asc
Description: PGP signature
