From: kernel test robot <lkp@intel.com>
To: kbuild-all@lists.01.org
Subject: Re: [RFC PATCH v1 2/2] exynos-ufs: support command history
Date: Sat, 20 Jun 2020 23:26:48 +0800 [thread overview]
Message-ID: <202006202348.gy4UOmIn%lkp@intel.com> (raw)
In-Reply-To: <1592635992-35619-2-git-send-email-kwmad.kim@samsung.com>
[-- Attachment #1: Type: text/plain, Size: 1628 bytes --]
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: xtensa-allyesconfig (attached as .config)
compiler: xtensa-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=xtensa
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 >>):
>> xtensa-linux-ld: drivers/scsi/ufs/ufs-exynos-dbg.o:(.data+0x60): multiple definition of `exynos7_uic_attr'; drivers/scsi/ufs/ufs-exynos.o:(.data+0x120): first defined here
>> xtensa-linux-ld: drivers/scsi/ufs/ufs-exynos-dbg.o:(.bss+0x7a0): multiple definition of `exynos_ufs_drvs'; drivers/scsi/ufs/ufs-exynos.o:(.data+0x1c0): first defined here
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all(a)lists.01.org
[-- Attachment #2: config.gz --]
[-- Type: application/gzip, Size: 64405 bytes --]
next prev parent reply other threads:[~2020-06-20 15:26 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20200620070044epcas2p269e3c266c86c65dd0e894d8188036a30@epcas2p2.samsung.com>
2020-06-20 6:53 ` [RFC PATCH v1 1/2] ufs: introduce callbacks to get command information Kiwoong Kim
[not found] ` <CGME20200620070047epcas2p37229d52d479df9f64ee4fc14f469acf9@epcas2p3.samsung.com>
2020-06-20 6:53 ` [RFC PATCH v1 2/2] exynos-ufs: support command history Kiwoong Kim
2020-06-20 15:26 ` kernel test robot [this message]
2020-06-20 19:08 ` kernel test robot
2020-06-24 3:10 ` Bart Van Assche
2020-06-29 8:49 ` Kiwoong Kim
2020-06-29 10:08 ` Kiwoong Kim
2020-06-20 16:33 ` [RFC PATCH v1 1/2] ufs: introduce callbacks to get command information Bart Van Assche
2020-06-23 2:28 ` Kiwoong Kim
2020-06-24 2:53 ` Bart Van Assche
2020-06-22 11:35 ` Dan Carpenter
2020-06-22 11:35 ` Dan Carpenter
2020-06-25 14:05 ` Stanley Chu
2020-06-26 11:42 ` Kiwoong Kim
2020-06-26 12:29 ` Stanley Chu
2020-06-29 7:01 ` Kiwoong Kim
2020-06-29 7:11 ` Kiwoong Kim
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=202006202348.gy4UOmIn%lkp@intel.com \
--to=lkp@intel.com \
--cc=kbuild-all@lists.01.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.