Hi Kiwoong,

[FYI, it's a private test report for your RFC patch.]
[auto build test ERROR on scsi/for-next]
[also build test ERROR on mkp-scsi/for-next next-20200618]
[cannot apply to v5.8-rc1]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use  as documented in
https://git-scm.com/docs/git-format-patch]

url:    https://github.com/0day-ci/linux/commits/Kiwoong-Kim/ufs-introduce-callbacks-to-get-command-information/20200620-150310
base:   https://git.kernel.org/pub/scm/linux/kernel/git/jejb/scsi.git for-next
config: riscv-allyesconfig (attached as .config)
compiler: riscv64-linux-gcc (GCC) 9.3.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
        # save the attached .config to linux build tree
        COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-9.3.0 make.cross ARCH=riscv 

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

All errors (new ones prefixed by >>):

>> riscv64-linux-ld: drivers/scsi/ufs/ufs-exynos-dbg.o:(.data+0x48): multiple definition of `exynos7_uic_attr'; drivers/scsi/ufs/ufs-exynos.o:ufs-exynos.c:(.data+0x1b8): first defined here
   riscv64-linux-ld: drivers/scsi/ufs/ufs-exynos-dbg.o: in function `.LANCHOR0':
>> ufs-exynos-dbg.c:(.bss+0x770): multiple definition of `exynos_ufs_drvs'; drivers/scsi/ufs/ufs-exynos.o:ufs-exynos.c:(.data+0x178): first defined here

---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all(a)lists.01.org