From: kbuild test robot <lkp@intel.com>
Cc: kbuild-all@01.org, linux-kernel@vger.kernel.org,
linux-watchdog@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
kernel@savoirfairelinux.com, mark@embeddedarm.com,
kris@embeddedarm.com, horms+renesas@verge.net.au,
treding@nvidia.com, jonathanh@nvidia.com, f.fainelli@gmail.com,
fabio.estevam@nxp.com, kernel@pengutronix.de,
shawnguo@kernel.org, linux@armlinux.org.uk, linux@roeck-us.net,
wim@iguana.be, mark.rutland@arm.com, robh+dt@kernel.org,
damien.riegel@savoirfairelinux.com,
lucile.quirion@savoirfairelinux.com, olof@lixom.net,
arnd@arndb.de, suzuki.poulose@arm.com, linus.walleij@linaro.org,
will.deacon@arm.com, yamada.masahiro@socionext.com,
Sebastien Bourdelin <sebastien.bourdelin@savoirfairelinux.com>
Subject: Re: [PATCH 6/6] watchdog: ts4600: add driver for TS-4600 watchdog
Date: Thu, 15 Dec 2016 18:28:58 +0800 [thread overview]
Message-ID: <201612151847.aVsOJIuu%fengguang.wu@intel.com> (raw)
In-Reply-To: <20161214231237.17496-7-sebastien.bourdelin@savoirfairelinux.com>
[-- Attachment #1: Type: text/plain, Size: 1211 bytes --]
Hi Sebastien,
[auto build test ERROR on linus/master]
[also build test ERROR on v4.9]
[cannot apply to next-20161215]
[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/Sebastien-Bourdelin/of-documentation-add-bindings-documentation-for-TS-4600/20161215-072238
config: i386-allyesconfig (attached as .config)
compiler: gcc-6 (Debian 6.2.0-3) 6.2.0 20160901
reproduce:
# save the attached .config to linux build tree
make ARCH=i386
All errors (new ones prefixed by >>):
drivers/built-in.o: In function `ts4600_wdt_start':
>> ts4600_wdt.c:(.text+0x2333d64): undefined reference to `ts_nbus_write'
drivers/built-in.o: In function `ts4600_wdt_stop':
ts4600_wdt.c:(.text+0x2333d85): undefined reference to `ts_nbus_write'
drivers/built-in.o: In function `ts4600_wdt_probe':
ts4600_wdt.c:(.text+0x2333e66): undefined reference to `ts_nbus_write'
>> ts4600_wdt.c:(.text+0x2333ee9): undefined reference to `ts_nbus_is_ready'
---
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: 57052 bytes --]
next prev parent reply other threads:[~2016-12-15 10:28 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-14 23:12 [PATCH 0/6] Add board support for TS-4600 Sebastien Bourdelin
2016-12-14 23:12 ` [PATCH 1/6] of: documentation: add bindings documentation " Sebastien Bourdelin
[not found] ` <20161214231237.17496-2-sebastien.bourdelin-4ysUXcep3aM1wj+D4I0NRVaTQe2KTcn/@public.gmane.org>
2016-12-19 22:05 ` Rob Herring
[not found] ` <20161214231237.17496-1-sebastien.bourdelin-4ysUXcep3aM1wj+D4I0NRVaTQe2KTcn/@public.gmane.org>
2016-12-14 23:12 ` [PATCH 2/6] ARM: dts: TS-4600: add basic device tree Sebastien Bourdelin
2016-12-14 23:12 ` [PATCH 6/6] watchdog: ts4600: add driver for TS-4600 watchdog Sebastien Bourdelin
2016-12-15 10:28 ` kbuild test robot [this message]
2016-12-19 22:13 ` Rob Herring
[not found] ` <20161214231237.17496-7-sebastien.bourdelin-4ysUXcep3aM1wj+D4I0NRVaTQe2KTcn/@public.gmane.org>
2016-12-23 1:53 ` Guenter Roeck
2016-12-14 23:12 ` [PATCH 3/6] dt-bindings: bus: Add documentation for the Technologic Systems NBUS Sebastien Bourdelin
[not found] ` <20161214231237.17496-4-sebastien.bourdelin-4ysUXcep3aM1wj+D4I0NRVaTQe2KTcn/@public.gmane.org>
2016-12-19 22:12 ` Rob Herring
2016-12-14 23:12 ` [PATCH 4/6] bus: add driver " Sebastien Bourdelin
[not found] ` <20161214231237.17496-5-sebastien.bourdelin-4ysUXcep3aM1wj+D4I0NRVaTQe2KTcn/@public.gmane.org>
2016-12-30 7:58 ` Linus Walleij
[not found] ` <CACRpkdYHHrYY-fAPnNmV94ejFJ36rhSF0SqSVHkTNq+YCRNNZw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2017-02-01 19:56 ` Sebastien Bourdelin
[not found] ` <7bc0871f-ac0a-e8a0-0c84-a0e61b3991a8-4ysUXcep3aM1wj+D4I0NRVaTQe2KTcn/@public.gmane.org>
2017-02-03 13:51 ` Linus Walleij
[not found] ` <CACRpkdbAYyxTOq_ZAwjSJAhCbrzTaUMSG9N7t8Wq1ifTDFBLrQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2017-02-03 15:56 ` Sebastien Bourdelin
2016-12-14 23:12 ` [PATCH 5/6] ARM: dts: TS-4600: add NBUS support Sebastien Bourdelin
[not found] ` <20161214231237.17496-6-sebastien.bourdelin-4ysUXcep3aM1wj+D4I0NRVaTQe2KTcn/@public.gmane.org>
2016-12-30 8:01 ` Linus Walleij
2016-12-14 23:12 ` [PATCH 2/6] ARM: dts: TS-4600: add basic device tree Sebastien Bourdelin
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=201612151847.aVsOJIuu%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=arnd@arndb.de \
--cc=damien.riegel@savoirfairelinux.com \
--cc=devicetree@vger.kernel.org \
--cc=f.fainelli@gmail.com \
--cc=fabio.estevam@nxp.com \
--cc=horms+renesas@verge.net.au \
--cc=jonathanh@nvidia.com \
--cc=kbuild-all@01.org \
--cc=kernel@pengutronix.de \
--cc=kernel@savoirfairelinux.com \
--cc=kris@embeddedarm.com \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-watchdog@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=linux@roeck-us.net \
--cc=lucile.quirion@savoirfairelinux.com \
--cc=mark.rutland@arm.com \
--cc=mark@embeddedarm.com \
--cc=olof@lixom.net \
--cc=robh+dt@kernel.org \
--cc=sebastien.bourdelin@savoirfairelinux.com \
--cc=shawnguo@kernel.org \
--cc=suzuki.poulose@arm.com \
--cc=treding@nvidia.com \
--cc=will.deacon@arm.com \
--cc=wim@iguana.be \
--cc=yamada.masahiro@socionext.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