public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: Mike Christie <michael.christie@oracle.com>
To: kernel test robot <lkp@intel.com>,
	bvanassche@acm.org, mwilck@suse.com, hch@lst.de,
	martin.petersen@oracle.com, linux-scsi@vger.kernel.org,
	james.bottomley@hansenpartnership.com
Cc: kbuild-all@lists.01.org
Subject: Re: [PATCH v5 35/35] scsi: Add kunit tests for scsi_check_passthrough
Date: Mon, 24 Oct 2022 13:39:49 -0500	[thread overview]
Message-ID: <d2ee2cd6-ee75-9ccf-ac08-c096711bedab@oracle.com> (raw)
In-Reply-To: <202210231450.rSoaGXfs-lkp@intel.com>

On 10/23/22 1:32 AM, kernel test robot wrote:
> Hi Mike,
> 
> I love your patch! Yet something to improve:
> 
> [auto build test ERROR on jejb-scsi/for-next]
> [also build test ERROR on groeck-staging/hwmon-next linus/master v6.1-rc1 next-20221021]
> [cannot apply to mkp-scsi/for-next]
> [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/Mike-Christie/Allow-scsi_execute-users-to-control-retries/20221023-111103
> base:   https://git.kernel.org/pub/scm/linux/kernel/git/jejb/scsi.git for-next
> patch link:    https://lore.kernel.org/r/20221023030403.33845-36-michael.christie%40oracle.com
> patch subject: [PATCH v5 35/35] scsi: Add kunit tests for scsi_check_passthrough
> config: arc-randconfig-r025-20221023
> compiler: arc-elf-gcc (GCC) 12.1.0
> reproduce (this is a W=1 build):
>         wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
>         chmod +x ~/bin/make.cross
>         # https://github.com/intel-lab-lkp/linux/commit/5c568c0893302315545f701ffe9d0aa2afb276d4
>         git remote add linux-review https://github.com/intel-lab-lkp/linux
>         git fetch --no-tags linux-review Mike-Christie/Allow-scsi_execute-users-to-control-retries/20221023-111103
>         git checkout 5c568c0893302315545f701ffe9d0aa2afb276d4
>         # save the config file
>         mkdir build_dir && cp config build_dir/.config
>         COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-12.1.0 make.cross W=1 O=build_dir ARCH=arc SHELL=/bin/bash
> 
> If you fix the issue, kindly add following tag where applicable
> | Reported-by: kernel test robot <lkp@intel.com>
> 
> All errors (new ones prefixed by >>):
> 
>    arc-elf-ld: drivers/scsi/scsi_error.o: in function `scsi_test_error_check_passthough':
>>> drivers/scsi/scsi_error_test.c:139: undefined reference to `kunit_binary_assert_format'
>>> arc-elf-ld: drivers/scsi/scsi_error_test.c:139: undefined reference to `kunit_binary_assert_format'

Looks like I didn't test the case where scsi is built into the kernel but
kunit is built as a module. Will fix in a v6 posting.


      reply	other threads:[~2022-10-24 20:29 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-23  3:03 [PATCH v5 00/35] Allow scsi_execute users to control retries Mike Christie
2022-10-23  3:03 ` [PATCH v5 01/35] scsi: Add helper to prep sense during error handling Mike Christie
2022-10-23  3:03 ` [PATCH v5 02/35] scsi: Allow passthrough to override what errors to retry Mike Christie
2022-10-23  3:03 ` [PATCH v5 03/35] scsi: Add struct for args to execution functions Mike Christie
2022-10-23  3:03 ` [PATCH v5 04/35] scsi: Add scsi_failure field to scsi_exec_args Mike Christie
2022-10-23  3:03 ` [PATCH v5 05/35] scsi: libata: Convert to scsi_exec_req Mike Christie
2022-10-23  3:03 ` [PATCH v5 06/35] hwmon: drivetemp: " Mike Christie
2022-10-23  3:03 ` [PATCH v5 07/35] scsi: ch: " Mike Christie
2022-10-23  3:03 ` [PATCH v5 08/35] scsi: scsi_dh: " Mike Christie
2022-10-23  3:03 ` [PATCH v5 09/35] scsi: core: " Mike Christie
2022-10-23  3:03 ` [PATCH v5 10/35] scsi: spi: " Mike Christie
2022-10-23  3:03 ` [PATCH v5 11/35] scsi: sd: " Mike Christie
2022-10-23  3:03 ` [PATCH v5 12/35] scsi: zbc: " Mike Christie
2022-10-23  3:03 ` [PATCH v5 13/35] scsi: ses: " Mike Christie
2022-10-23  3:03 ` [PATCH v5 14/35] scsi: sr: " Mike Christie
2022-10-23  3:03 ` [PATCH v5 15/35] scsi: virtio_scsi: " Mike Christie
2022-10-23  3:03 ` [PATCH v5 16/35] scsi: target_core_pscsi: " Mike Christie
2022-10-23  3:03 ` [PATCH v5 17/35] scsi: ufshcd: " Mike Christie
2022-10-23  3:03 ` [PATCH v5 18/35] scsi: cxlflash: " Mike Christie
2022-10-23  3:03 ` [PATCH v5 19/35] scsi: Remove scsi_execute functions Mike Christie
2022-10-23  3:03 ` [PATCH v5 20/35] scsi: Have scsi-ml retry scsi_probe_lun errors Mike Christie
2022-10-23  3:03 ` [PATCH v5 21/35] scsi: retry INQUIRY after timeout Mike Christie
2022-10-23  3:03 ` [PATCH v5 22/35] scsi: Have scsi-ml retry read_capacity_16 errors Mike Christie
2022-10-23  3:03 ` [PATCH v5 23/35] scsi: Have scsi-ml retry sd_spinup_disk errors Mike Christie
2022-10-23  3:03 ` [PATCH v5 24/35] scsi: hp_sw: Have scsi-ml retry scsi_exec_req errors Mike Christie
2022-10-23  3:03 ` [PATCH v5 25/35] scsi: rdac: Have scsi-ml retry send_mode_select errors Mike Christie
2022-10-23  3:03 ` [PATCH v5 26/35] scsi: spi: Have scsi-ml retry spi_execute errors Mike Christie
2022-10-23  3:03 ` [PATCH v5 27/35] scsi: sd: Have scsi-ml retry sd_sync_cache errors Mike Christie
2022-10-23  3:03 ` [PATCH v5 28/35] scsi: ch: Have scsi-ml retry ch_do_scsi errors Mike Christie
2022-10-23  3:03 ` [PATCH v5 29/35] scsi: Have scsi-ml retry scsi_mode_sense errors Mike Christie
2022-10-23  3:03 ` [PATCH v5 30/35] scsi: Have scsi-ml retry scsi_report_lun_scan errors Mike Christie
2022-10-23  3:03 ` [PATCH v5 31/35] scsi: sd: Have sd_pr_command retry UAs Mike Christie
2022-10-23  3:04 ` [PATCH v5 32/35] scsi: sd: Have scsi-ml retry read_capacity_10 errors Mike Christie
2022-10-23  3:04 ` [PATCH v5 33/35] scsi: ses: Have scsi-ml retry scsi_exec_req errors Mike Christie
2022-10-23  3:04 ` [PATCH v5 34/35] scsi: sr: Have scsi-ml retry get_sectorsize errors Mike Christie
2022-10-23  3:04 ` [PATCH v5 35/35] scsi: Add kunit tests for scsi_check_passthrough Mike Christie
2022-10-23  6:32   ` kernel test robot
2022-10-24 18:39     ` Mike Christie [this message]

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=d2ee2cd6-ee75-9ccf-ac08-c096711bedab@oracle.com \
    --to=michael.christie@oracle.com \
    --cc=bvanassche@acm.org \
    --cc=hch@lst.de \
    --cc=james.bottomley@hansenpartnership.com \
    --cc=kbuild-all@lists.01.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=lkp@intel.com \
    --cc=martin.petersen@oracle.com \
    --cc=mwilck@suse.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