From: kbuild test robot <fengguang.wu@intel.com>
To: Peter Rosin <peda@axentia.se>
Cc: kbuild-all@01.org, linux-i2c@vger.kernel.org,
Wolfram Sang <wsa@the-dreams.de>
Subject: [wsa:i2c/for-next 5/14] drivers/gpu/drm/drm_dp_helper.c:810: error: 'struct i2c_adapter' has no member named 'lock_bus'
Date: Fri, 26 Aug 2016 02:35:49 +0800 [thread overview]
Message-ID: <201608260244.9puAmxpw%fengguang.wu@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2120 bytes --]
tree: https://git.kernel.org/pub/scm/linux/kernel/git/wsa/linux.git i2c/for-next
head: 431f07e8b0097ded2ffb773d4ea6a797b2bc8bfe
commit: 24882319480379588d0cced458ed7dd670e93fc7 [5/14] i2c: move locking operations to their own struct
config: x86_64-randconfig-s0-08260201 (attached as .config)
compiler: gcc-4.4 (Debian 4.4.7-8) 4.4.7
reproduce:
git checkout 24882319480379588d0cced458ed7dd670e93fc7
# save the attached .config to linux build tree
make ARCH=x86_64
All errors (new ones prefixed by >>):
drivers/gpu/drm/drm_dp_helper.c: In function 'drm_dp_aux_init':
>> drivers/gpu/drm/drm_dp_helper.c:810: error: 'struct i2c_adapter' has no member named 'lock_bus'
>> drivers/gpu/drm/drm_dp_helper.c:811: error: 'struct i2c_adapter' has no member named 'trylock_bus'
>> drivers/gpu/drm/drm_dp_helper.c:812: error: 'struct i2c_adapter' has no member named 'unlock_bus'
vim +810 drivers/gpu/drm/drm_dp_helper.c
4f71d0cb Dave Airlie 2014-06-04 804 mutex_init(&aux->hw_mutex);
4f71d0cb Dave Airlie 2014-06-04 805
88759686 Thierry Reding 2013-12-12 806 aux->ddc.algo = &drm_dp_i2c_algo;
88759686 Thierry Reding 2013-12-12 807 aux->ddc.algo_data = aux;
88759686 Thierry Reding 2013-12-12 808 aux->ddc.retries = 3;
88759686 Thierry Reding 2013-12-12 809
0c2f6f1a Chris Wilson 2016-06-17 @810 aux->ddc.lock_bus = lock_bus;
0c2f6f1a Chris Wilson 2016-06-17 @811 aux->ddc.trylock_bus = trylock_bus;
0c2f6f1a Chris Wilson 2016-06-17 @812 aux->ddc.unlock_bus = unlock_bus;
acd8f414 Chris Wilson 2016-06-17 813 }
acd8f414 Chris Wilson 2016-06-17 814 EXPORT_SYMBOL(drm_dp_aux_init);
acd8f414 Chris Wilson 2016-06-17 815
:::::: The code at line 810 was first introduced by commit
:::::: 0c2f6f1a561136a09c5de91889d0aa35e13f73d4 drm: Pass the drm_dp_aux->hw_mutex to i2c for its locking
:::::: TO: Chris Wilson <chris@chris-wilson.co.uk>
:::::: CC: Daniel Vetter <daniel.vetter@ffwll.ch>
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all Intel Corporation
[-- Attachment #2: .config.gz --]
[-- Type: application/octet-stream, Size: 28128 bytes --]
reply other threads:[~2016-08-25 18:52 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=201608260244.9puAmxpw%fengguang.wu@intel.com \
--to=fengguang.wu@intel.com \
--cc=kbuild-all@01.org \
--cc=linux-i2c@vger.kernel.org \
--cc=peda@axentia.se \
--cc=wsa@the-dreams.de \
/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;
as well as URLs for NNTP newsgroup(s).