From: Guenter Roeck <linux@roeck-us.net>
To: Eddie James <eajames@linux.vnet.ibm.com>
Cc: kbuild-all@01.org, linux-kernel@vger.kernel.org,
linux-hwmon@vger.kernel.org, devicetree@vger.kernel.org,
jdelvare@suse.com, linux-doc@vger.kernel.org,
openbmc@lists.ozlabs.org, robh+dt@kernel.org,
gregkh@linuxfoundation.org, mark.rutland@arm.com, joel@jms.id.au,
benh@kernel.crashing.org
Subject: Re: [PATCH v5 05/10] hwmon: Add On-Chip Controller (OCC) hwmon driver
Date: Fri, 12 Oct 2018 05:46:58 -0700 [thread overview]
Message-ID: <20181012124658.GB11386@roeck-us.net> (raw)
In-Reply-To: <201809011808.kL7L1gpv%fengguang.wu@intel.com>
On Sat, Sep 01, 2018 at 08:06:16PM +0800, kbuild test robot wrote:
> Hi Eddie,
>
> I love your patch! Yet something to improve:
>
> [auto build test ERROR on hwmon/hwmon-next]
> [also build test ERROR on v4.19-rc1 next-20180831]
> [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/Eddie-James/hwmon-and-fsi-Add-On-Chip-Controller-Driver/20180831-165247
> base: https://git.kernel.org/pub/scm/linux/kernel/git/groeck/linux-staging.git hwmon-next
> config: arm64-allmodconfig (attached as .config)
> compiler: aarch64-linux-gnu-gcc (Debian 7.2.0-11) 7.2.0
> reproduce:
> wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
> chmod +x ~/bin/make.cross
> # save the attached .config to linux build tree
> GCC_VERSION=7.2.0 make.cross ARCH=arm64
>
> All errors (new ones prefixed by >>):
>
> drivers/hwmon/occ/p8_i2c.o: In function `init_module':
> >> p8_i2c.c:(.init.text+0x0): multiple definition of `init_module'
> drivers/hwmon/occ/p9_sbe.o:p9_sbe.c:(.init.text+0x0): first defined here
> drivers/hwmon/occ/p8_i2c.o: In function `cleanup_module':
> >> p8_i2c.c:(.exit.text+0x0): multiple definition of `cleanup_module'
> drivers/hwmon/occ/p9_sbe.o:p9_sbe.c:(.exit.text+0x0): first defined here
>
This will need to be fixed before I can pick up the series.
Each module must have only one set of module initialization
functions.
Guenter
> ---
> 0-DAY kernel test infrastructure Open Source Technology Center
> https://lists.01.org/pipermail/kbuild-all Intel Corporation
next prev parent reply other threads:[~2018-10-12 12:47 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-30 21:32 [PATCH v5 00/10] hwmon and fsi: Add On-Chip Controller Driver Eddie James
2018-08-30 21:32 ` [PATCH v5 01/10] dt-bindings: fsi: Add P9 OCC device documentation Eddie James
2018-09-10 18:16 ` Rob Herring
2018-09-12 7:56 ` Benjamin Herrenschmidt
2018-10-12 12:44 ` Guenter Roeck
2018-08-30 21:32 ` [PATCH v5 02/10] fsi: Add On-Chip Controller (OCC) driver Eddie James
2018-08-30 21:32 ` [PATCH v5 03/10] Documentation: hwmon: Add OCC documentation Eddie James
2018-08-31 23:01 ` Randy Dunlap
2018-08-30 21:32 ` [PATCH v5 04/10] dt-bindings: i2c: Add P8 OCC hwmon device documentation Eddie James
2018-08-30 21:32 ` [PATCH v5 05/10] hwmon: Add On-Chip Controller (OCC) hwmon driver Eddie James
2018-09-01 12:06 ` kbuild test robot
2018-10-12 12:46 ` Guenter Roeck [this message]
2018-08-30 21:32 ` [PATCH v5 06/10] hwmon (occ): Add command transport method for P8 and P9 Eddie James
2018-08-30 21:32 ` [PATCH v5 07/10] hwmon (occ): Parse OCC poll response Eddie James
2018-08-30 21:32 ` [PATCH v5 08/10] hwmon (occ): Add sensor types and versions Eddie James
2018-08-30 21:32 ` [PATCH v5 09/10] hwmon (occ): Add sensor attributes and register hwmon device Eddie James
2018-08-30 21:32 ` [PATCH v5 10/10] hwmon (occ): Add sysfs attributes for additional OCC data Eddie James
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=20181012124658.GB11386@roeck-us.net \
--to=linux@roeck-us.net \
--cc=benh@kernel.crashing.org \
--cc=devicetree@vger.kernel.org \
--cc=eajames@linux.vnet.ibm.com \
--cc=gregkh@linuxfoundation.org \
--cc=jdelvare@suse.com \
--cc=joel@jms.id.au \
--cc=kbuild-all@01.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-hwmon@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=openbmc@lists.ozlabs.org \
--cc=robh+dt@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