From: kbuild test robot <lkp@intel.com>
To: Vincent Cheng <vincent.cheng.xh@renesas.com>
Cc: kbuild-all@lists.01.org, linux-kernel@vger.kernel.org,
Richard Cochran <richardcochran@gmail.com>
Subject: drivers/ptp/ptp_clockmatrix.c:107: undefined reference to `i2c_transfer'
Date: Thu, 12 Dec 2019 03:46:13 +0800 [thread overview]
Message-ID: <201912120320.EFaJtEf4%lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2205 bytes --]
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head: 6794862a16ef41f753abd75c03a152836e4c8028
commit: 3a6ba7dc7799355557938fbdc15a558236011429 ptp: Add a ptp clock driver for IDT ClockMatrix.
date: 5 weeks ago
config: i386-randconfig-b001-20191211 (attached as .config)
compiler: gcc-7 (Debian 7.5.0-1) 7.5.0
reproduce:
git checkout 3a6ba7dc7799355557938fbdc15a558236011429
# save the attached .config to linux build tree
make ARCH=i386
If you fix the issue, kindly add following tag
Reported-by: kbuild test robot <lkp@intel.com>
All errors (new ones prefixed by >>):
ld: drivers/ptp/ptp_clockmatrix.o: in function `idtcm_xfer':
>> drivers/ptp/ptp_clockmatrix.c:107: undefined reference to `i2c_transfer'
ld: drivers/ptp/ptp_clockmatrix.o: in function `idtcm_driver_init':
>> drivers/ptp/ptp_clockmatrix.c:1425: undefined reference to `i2c_register_driver'
ld: drivers/ptp/ptp_clockmatrix.o: in function `idtcm_driver_exit':
>> drivers/ptp/ptp_clockmatrix.c:1425: undefined reference to `i2c_del_driver'
vim +107 drivers/ptp/ptp_clockmatrix.c
86
87 static int idtcm_xfer(struct idtcm *idtcm,
88 u8 regaddr,
89 u8 *buf,
90 u16 count,
91 bool write)
92 {
93 struct i2c_client *client = idtcm->client;
94 struct i2c_msg msg[2];
95 int cnt;
96
97 msg[0].addr = client->addr;
98 msg[0].flags = 0;
99 msg[0].len = 1;
100 msg[0].buf = ®addr;
101
102 msg[1].addr = client->addr;
103 msg[1].flags = write ? 0 : I2C_M_RD;
104 msg[1].len = count;
105 msg[1].buf = buf;
106
> 107 cnt = i2c_transfer(client->adapter, msg, 2);
108
109 if (cnt < 0) {
110 dev_err(&client->dev, "i2c_transfer returned %d\n", cnt);
111 return cnt;
112 } else if (cnt != 2) {
113 dev_err(&client->dev,
114 "i2c_transfer sent only %d of %d messages\n", cnt, 2);
115 return -EIO;
116 }
117
118 return 0;
119 }
120
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org Intel Corporation
[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 34351 bytes --]
next reply other threads:[~2019-12-11 19:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-11 19:46 kbuild test robot [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-12-11 11:49 kbuild test robot
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=201912120320.EFaJtEf4%lkp@intel.com \
--to=lkp@intel.com \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=richardcochran@gmail.com \
--cc=vincent.cheng.xh@renesas.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
all inboxes | Powered by JetHome®