From: kbuild test robot <lkp@intel.com>
To: Bartosz Golaszewski <bgolaszewski@baylibre.com>
Cc: kbuild-all@01.org, Wolfram Sang <wsa@the-dreams.de>,
linux-i2c <linux-i2c@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>, Andrew Lunn <andrew@lunn.ch>,
Bartosz Golaszewski <bgolaszewski@baylibre.com>
Subject: Re: [PATCH 08/13] eeprom: at24: call read and write routines via function pointers
Date: Thu, 24 Mar 2016 23:12:41 +0800 [thread overview]
Message-ID: <201603242348.7YdXqeef%fengguang.wu@intel.com> (raw)
In-Reply-To: <1458830767-23816-9-git-send-email-bgolaszewski@baylibre.com>
[-- Attachment #1: Type: text/plain, Size: 1533 bytes --]
Hi Bartosz,
[auto build test ERROR on next-20160324]
[cannot apply to v4.5-rc7 v4.5-rc6 v4.5-rc5 v4.5]
[if your patch is applied to the wrong git tree, please drop us a note to help improving the system]
url: https://github.com/0day-ci/linux/commits/Bartosz-Golaszewski/eeprom-support-for-at24cs-and-at24mac/20160324-230008
config: x86_64-randconfig-x012-201612 (attached as .config)
reproduce:
# save the attached .config to linux build tree
make ARCH=x86_64
All errors (new ones prefixed by >>):
drivers/misc/eeprom/at24.c: In function 'at24_probe':
>> drivers/misc/eeprom/at24.c:617:18: error: assignment from incompatible pointer type [-Werror=incompatible-pointer-types]
at24->read_func = at24_read;
^
drivers/misc/eeprom/at24.c:618:19: error: assignment from incompatible pointer type [-Werror=incompatible-pointer-types]
at24->write_func = at24_write;
^
cc1: some warnings being treated as errors
vim +617 drivers/misc/eeprom/at24.c
611 mutex_init(&at24->wrbuf_lock);
612 at24->use_smbus = use_smbus;
613 at24->use_smbus_write = use_smbus_write;
614 at24->chip = chip;
615 at24->num_addresses = num_addresses;
616
> 617 at24->read_func = at24_read;
618 at24->write_func = at24_write;
619
620 writable = !(chip.flags & AT24_FLAG_READONLY);
---
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: 20892 bytes --]
next prev parent reply other threads:[~2016-03-24 15:15 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-24 14:45 [PATCH 00/13] eeprom: support for at24cs and at24mac Bartosz Golaszewski
2016-03-24 14:45 ` [PATCH 01/13] eeprom: at24: remove a reduntant if Bartosz Golaszewski
2016-03-24 14:45 ` [PATCH 02/13] eeprom: at24: improve the device_id table readability Bartosz Golaszewski
2016-03-24 14:45 ` [PATCH 03/13] eeprom: at24: platform_data: use BIT() macro Bartosz Golaszewski
2016-03-24 14:45 ` [PATCH 04/13] eeprom: at24: make locking more fine-grained Bartosz Golaszewski
2016-03-24 14:45 ` [PATCH 05/13] eeprom: at24: replace msleep() with usleep_range() Bartosz Golaszewski
2016-03-24 14:46 ` [PATCH 06/13] eeprom: at24: add serial number flag Bartosz Golaszewski
2016-03-24 14:46 ` [PATCH 07/13] eeprom: at24: support reading of the serial number Bartosz Golaszewski
2016-03-24 14:46 ` [PATCH 08/13] eeprom: at24: call read and write routines via function pointers Bartosz Golaszewski
2016-03-24 15:12 ` kbuild test robot [this message]
2016-03-24 15:13 ` kbuild test robot
2016-03-24 14:46 ` [PATCH 09/13] eeprom: at24: use at24cs_serial_read() Bartosz Golaszewski
2016-03-24 14:46 ` [PATCH 10/13] eeprom: at24: add the at24cs series to the list of supported devices Bartosz Golaszewski
2016-03-24 14:46 ` [PATCH 11/13] eeprom: at24: add at24mac series flag Bartosz Golaszewski
2016-03-24 14:46 ` [PATCH 12/13] eeprom: at24: add support for at24mac series Bartosz Golaszewski
2016-03-24 14:46 ` [PATCH 13/13] eeprom: at24: add at24mac chips to the list of supported devices Bartosz Golaszewski
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=201603242348.7YdXqeef%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=andrew@lunn.ch \
--cc=bgolaszewski@baylibre.com \
--cc=kbuild-all@01.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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
all inboxes | Powered by JetHome®