linux-input.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: kbuild test robot <lkp@intel.com>
To: Alexandru Ardelean <alexandru.ardelean@analog.com>
Cc: kbuild-all@lists.01.org, linux-input@vger.kernel.org,
	linux-kernel@vger.kernel.org, dmitry.torokhov@gmail.com,
	Lars-Peter Clausen <lars@metafoo.de>,
	Alexandru Ardelean <alexandru.ardelean@analog.com>
Subject: Re: [PATCH 2/2] input: adp5589: Add basic devicetree support
Date: Thu, 31 Oct 2019 11:06:19 +0800	[thread overview]
Message-ID: <201910311024.3yjFSzoC%lkp@intel.com> (raw)
In-Reply-To: <20191029112836.9188-2-alexandru.ardelean@analog.com>

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

Hi Alexandru,

I love your patch! Perhaps something to improve:

[auto build test WARNING on input/next]
[also build test WARNING on next-20191030]
[cannot apply to v5.4-rc5]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system. BTW, we also suggest to use '--base' option to specify the
base tree in git format-patch, please see https://stackoverflow.com/a/37406982]

url:    https://github.com/0day-ci/linux/commits/Alexandru-Ardelean/input-adp5589-Add-default-platform-data/20191031-073612
base:   https://git.kernel.org/pub/scm/linux/kernel/git/dtor/input.git next
config: x86_64-kexec (attached as .config)
compiler: gcc-7 (Debian 7.4.0-14) 7.4.0
reproduce:
        # save the attached .config to linux build tree
        make ARCH=x86_64 

If you fix the issue, kindly add following tag
Reported-by: kbuild test robot <lkp@intel.com>

All warnings (new ones prefixed by >>):

   drivers/input/keyboard/adp5589-keys.c: In function 'adp5589_i2c_get_driver_data':
>> drivers/input/keyboard/adp5589-keys.c:1004:10: warning: cast from pointer to integer of different size [-Wpointer-to-int-cast]
      return (int)match->data;
             ^

vim +1004 drivers/input/keyboard/adp5589-keys.c

   989	
   990	static int adp5589_i2c_get_driver_data(struct i2c_client *i2c,
   991					       const struct i2c_device_id *id)
   992	{
   993		const struct of_device_id *match;
   994	
   995		if (id)
   996			return id->driver_data;
   997	
   998		if (!IS_ENABLED(CONFIG_OF) || !i2c->dev.of_node)
   999			return -ENODEV;
  1000	
  1001		match = of_match_node(i2c->dev.driver->of_match_table,
  1002				      i2c->dev.of_node);
  1003		if (match)
> 1004			return (int)match->data;
  1005	
  1006		return -ENODEV;
  1007	}
  1008	

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

  reply	other threads:[~2019-10-31  3:07 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-29 11:28 [PATCH 1/2] input: adp5589: Add default platform data Alexandru Ardelean
2019-10-29 11:28 ` [PATCH 2/2] input: adp5589: Add basic devicetree support Alexandru Ardelean
2019-10-31  3:06   ` kbuild test robot [this message]
2019-10-29 13:57 ` [PATCH 1/2] input: adp5589: Add default platform data Ardelean, Alexandru

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=201910311024.3yjFSzoC%lkp@intel.com \
    --to=lkp@intel.com \
    --cc=alexandru.ardelean@analog.com \
    --cc=dmitry.torokhov@gmail.com \
    --cc=kbuild-all@lists.01.org \
    --cc=lars@metafoo.de \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).