Linux block layer
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Yu Kuai <yukuai1@huaweicloud.com>,
	linux-block@vger.kernel.org, shinichiro.kawasaki@wdc.com,
	hch@infradead.org
Cc: oe-kbuild-all@lists.linux.dev, yukuai3@huawei.com,
	yangerkun@huawei.com, yi.zhang@huawei.com
Subject: Re: [PATCH blktests] dm: add a regression test
Date: Sat, 31 Dec 2022 06:24:11 +0800	[thread overview]
Message-ID: <202212310607.TCNdNAlM-lkp@intel.com> (raw)
In-Reply-To: <20221230065424.19998-1-yukuai1@huaweicloud.com>

Hi Yu,

Thank you for the patch! Perhaps something to improve:

[auto build test WARNING on linus/master]
[also build test WARNING on v6.2-rc1 next-20221226]
[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/Yu-Kuai/dm-add-a-regression-test/20221230-143530
patch link:    https://lore.kernel.org/r/20221230065424.19998-1-yukuai1%40huaweicloud.com
patch subject: [PATCH blktests] dm: add a regression test
reproduce:
        scripts/spdxcheck.py

If you fix the issue, kindly add following tag where applicable
| Reported-by: kernel test robot <lkp@intel.com>

spdxcheck warnings: (new ones prefixed by >>)
>> tests/dm/001: 2:27 Invalid License ID: GPL-3.0+
>> tests/dm/rc: 2:27 Invalid License ID: GPL-3.0+

-- 
0-DAY CI Kernel Test Service
https://01.org/lkp

  reply	other threads:[~2022-12-30 22:25 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-30  6:54 [PATCH blktests] dm: add a regression test Yu Kuai
2022-12-30 22:24 ` kernel test robot [this message]
2023-01-12  1:05 ` Shinichiro Kawasaki
2023-04-25  8:22   ` Yu Kuai
2023-04-25 12:15     ` Shin'ichiro Kawasaki
2023-04-25 17:24       ` Mike Snitzer
2023-04-26  8:42         ` Chaitanya Kulkarni
2023-04-26 12:13           ` Shin'ichiro Kawasaki

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=202212310607.TCNdNAlM-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=hch@infradead.org \
    --cc=linux-block@vger.kernel.org \
    --cc=oe-kbuild-all@lists.linux.dev \
    --cc=shinichiro.kawasaki@wdc.com \
    --cc=yangerkun@huawei.com \
    --cc=yi.zhang@huawei.com \
    --cc=yukuai1@huaweicloud.com \
    --cc=yukuai3@huawei.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox