From: kbuild test robot <lkp@intel.com>
To: Sayali Lokhande <sayalil@codeaurora.org>
Cc: kbuild-all@01.org, subhashj@codeaurora.org, cang@codeaurora.org,
vivek.gautam@codeaurora.org, rnayak@codeaurora.org,
vinholikatti@gmail.com, jejb@linux.vnet.ibm.com,
martin.petersen@oracle.com, asutoshd@codeaurora.org,
evgreen@chromium.org, riteshh@codeaurora.org,
linux-scsi@vger.kernel.org,
Sayali Lokhande <sayalil@codeaurora.org>,
open list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH V6] scsi: ufs: Add configfs support for UFS provisioning
Date: Mon, 16 Jul 2018 22:28:19 +0800 [thread overview]
Message-ID: <201807162221.qK2jPQub%fengguang.wu@intel.com> (raw)
In-Reply-To: <1531734237-27421-2-git-send-email-sayalil@codeaurora.org>
[-- Attachment #1: Type: text/plain, Size: 1754 bytes --]
Hi Sayali,
Thank you for the patch! Yet something to improve:
[auto build test ERROR on mkp-scsi/for-next]
[also build test ERROR on v4.18-rc5 next-20180716]
[if your patch is applied to the wrong git tree, please drop us a note to help improve the system]
url: https://github.com/0day-ci/linux/commits/Sayali-Lokhande/scsi-ufs-Add-configfs-support-for-UFS-provisioning/20180716-212258
base: https://git.kernel.org/pub/scm/linux/kernel/git/mkp/scsi.git for-next
config: i386-randconfig-x005-201828 (attached as .config)
compiler: gcc-7 (Debian 7.3.0-16) 7.3.0
reproduce:
# save the attached .config to linux build tree
make ARCH=i386
All errors (new ones prefixed by >>):
drivers/scsi/ufs/ufs-sysfs.o: In function `ufshcd_configfs_init':
>> drivers/scsi/ufs/ufshcd.h:900: multiple definition of `ufshcd_configfs_init'
drivers/scsi/ufs/ufshcd.o:drivers/scsi/ufs/ufshcd.h:900: first defined here
drivers/scsi/ufs/ufs-sysfs.o: In function `ufshcd_configfs_exit':
>> drivers/scsi/ufs/ufshcd.h:905: multiple definition of `ufshcd_configfs_exit'
drivers/scsi/ufs/ufshcd.o:drivers/scsi/ufs/ufshcd.h:905: first defined here
vim +900 drivers/scsi/ufs/ufshcd.h
893
894 /* Expose UFS configfs API's */
895 #ifdef CONFIG_UFS_PROVISION
896 int ufshcd_configfs_init(struct ufs_hba *hba, const char *name);
897 void ufshcd_configfs_exit(void);
898 #else
899 int ufshcd_configfs_init(struct ufs_hba *hba, const char *name)
> 900 {
901 return 0;
902 }
903
904 void ufshcd_configfs_exit(void)
> 905 {
906 }
907 #endif
908
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all Intel Corporation
[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 32099 bytes --]
next prev parent reply other threads:[~2018-07-16 14:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1531734237-27421-1-git-send-email-sayalil@codeaurora.org>
2018-07-16 9:43 ` Sayali Lokhande
2018-07-16 14:02 ` Bart Van Assche
2018-07-16 14:28 ` kbuild test robot [this message]
2018-07-16 15:28 ` kbuild test robot
2018-07-17 13:06 ` Adrian Hunter
2018-07-30 8:00 ` Sayali Lokhande
2018-07-17 21:00 ` Evan Green
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=201807162221.qK2jPQub%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=asutoshd@codeaurora.org \
--cc=cang@codeaurora.org \
--cc=evgreen@chromium.org \
--cc=jejb@linux.vnet.ibm.com \
--cc=kbuild-all@01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=riteshh@codeaurora.org \
--cc=rnayak@codeaurora.org \
--cc=sayalil@codeaurora.org \
--cc=subhashj@codeaurora.org \
--cc=vinholikatti@gmail.com \
--cc=vivek.gautam@codeaurora.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®