linux-input.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: kbuild test robot <lkp@intel.com>
Cc: kbuild-all@01.org, linux-input@vger.kernel.org,
	linux-kernel@vger.kernel.org,
	Andrew Duggan <aduggan@synaptics.com>,
	Dmitry Torokhov <dmitry.torokhov@gmail.com>,
	Linus Walleij <linus.walleij@linaro.org>,
	Jiri Kosina <jikos@kernel.org>,
	Benjamin Tissoires <benjamin.tissoires@redhat.com>,
	Vincent Huang <vincent.huang@tw.synaptics.com>,
	Nick Dyer <nick.dyer@itdev.co.uk>
Subject: Re: [PATCH v2] HID: rmi: Make hid-rmi a transport driver for synaptics-rmi4
Date: Sat, 4 Jun 2016 04:11:08 +0800	[thread overview]
Message-ID: <201606040447.LMmbn7qw%fengguang.wu@intel.com> (raw)
In-Reply-To: <1464979306-2771-1-git-send-email-aduggan@synaptics.com>

[-- Attachment #1: Type: text/plain, Size: 1633 bytes --]

Hi,

[auto build test ERROR on hid/for-next]
[also build test ERROR on v4.7-rc1 next-20160603]
[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/Andrew-Duggan/HID-rmi-Make-hid-rmi-a-transport-driver-for-synaptics-rmi4/20160604-024428
base:   https://git.kernel.org/pub/scm/linux/kernel/git/jikos/hid.git for-next
config: x86_64-randconfig-s4-06040320 (attached as .config)
compiler: gcc-6 (Debian 6.1.1-1) 6.1.1 20160430
reproduce:
        # save the attached .config to linux build tree
        make ARCH=x86_64 

All errors (new ones prefixed by >>):

>> drivers/hid/hid-rmi.c:572:2: error: unknown field 'dribble' specified in initializer
     .dribble = RMI_REG_STATE_OFF,
     ^
>> drivers/hid/hid-rmi.c:572:13: error: 'RMI_REG_STATE_OFF' undeclared here (not in a function)
     .dribble = RMI_REG_STATE_OFF,
                ^~~~~~~~~~~~~~~~~
>> drivers/hid/hid-rmi.c:573:2: error: unknown field 'palm_detect' specified in initializer
     .palm_detect = RMI_REG_STATE_OFF,
     ^

vim +/dribble +572 drivers/hid/hid-rmi.c

   566		return 0;
   567	}
   568	
   569	static struct rmi_2d_sensor_platform_data rmi_hid_2d_sensor_data = {
   570		.sensor_type = rmi_sensor_touchpad,
   571		.axis_align.flip_y = true,
 > 572		.dribble = RMI_REG_STATE_OFF,
 > 573		.palm_detect = RMI_REG_STATE_OFF,
   574	};
   575	
   576	static struct rmi_f30_data rmi_hid_f30_data = {

---
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: 27009 bytes --]

  reply	other threads:[~2016-06-03 20:12 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-03 18:41 [PATCH v2] HID: rmi: Make hid-rmi a transport driver for synaptics-rmi4 Andrew Duggan
2016-06-03 20:11 ` kbuild test robot [this message]
2016-06-06  9:25   ` Jiri Kosina
2016-06-15  7:23 ` Jiri Kosina
2016-06-15  9:41   ` Benjamin Tissoires
2016-06-16  0:05     ` Andrew Duggan
2016-06-15  9:54 ` Benjamin Tissoires
2016-06-15 23:51   ` Andrew Duggan

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=201606040447.LMmbn7qw%fengguang.wu@intel.com \
    --to=lkp@intel.com \
    --cc=aduggan@synaptics.com \
    --cc=benjamin.tissoires@redhat.com \
    --cc=dmitry.torokhov@gmail.com \
    --cc=jikos@kernel.org \
    --cc=kbuild-all@01.org \
    --cc=linus.walleij@linaro.org \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nick.dyer@itdev.co.uk \
    --cc=vincent.huang@tw.synaptics.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;
as well as URLs for NNTP newsgroup(s).