From: kbuild test robot <lkp@intel.com>
To: Kuppuswamy Sathyanarayanan <sathyanarayanan.kuppuswamy@linux.intel.com>
Cc: kbuild-all@01.org, andy@infradead.org, qipeng.zha@intel.com,
dvhart@infradead.org, david.e.box@linux.intel.com,
rajneesh.bhardwaj@intel.com,
sathyanarayanan.kuppuswamy@linux.intel.com,
platform-driver-x86@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 3/4] watchdog: iTCO_wdt: Fix PMC GCR memory mapping failure
Date: Mon, 20 Mar 2017 10:52:31 +0800 [thread overview]
Message-ID: <201703201035.ghLGuxMG%fengguang.wu@intel.com> (raw)
In-Reply-To: <2c41b3b6344f9cb455ac57e1e41aa229adb2867d.1489710235.git.sathyanarayanan.kuppuswamy@linux.intel.com>
[-- Attachment #1: Type: text/plain, Size: 1311 bytes --]
Hi Kuppuswamy,
[auto build test ERROR on linus/master]
[also build test ERROR on v4.11-rc3 next-20170310]
[cannot apply to platform-drivers-x86/for-next tip/x86/core]
[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/Kuppuswamy-Sathyanarayanan/platform-x86-intel_pmc_ipc-fix-gcr-offset/20170320-032638
config: x86_64-randconfig-h0-03200816 (attached as .config)
compiler: gcc-4.9 (Debian 4.9.4-2) 4.9.4
reproduce:
# save the attached .config to linux build tree
make ARCH=x86_64
All errors (new ones prefixed by >>):
drivers/built-in.o: In function `iTCO_wdt_unset_NO_REBOOT_bit':
>> iTCO_wdt.c:(.text+0x3b6f0f): undefined reference to `intel_pmc_gcr_read'
>> iTCO_wdt.c:(.text+0x3b6f24): undefined reference to `intel_pmc_gcr_write'
iTCO_wdt.c:(.text+0x3b6f2e): undefined reference to `intel_pmc_gcr_read'
drivers/built-in.o: In function `iTCO_wdt_set_NO_REBOOT_bit':
iTCO_wdt.c:(.text+0x3b729e): undefined reference to `intel_pmc_gcr_read'
iTCO_wdt.c:(.text+0x3b72d1): undefined reference to `intel_pmc_gcr_write'
---
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: 30932 bytes --]
next prev parent reply other threads:[~2017-03-20 2:53 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-16 3:32 [PATCH v1 1/1] platform/x86: intel_pmc_ipc: fix io mem mapping size Kuppuswamy Sathyanarayanan
2017-03-16 14:52 ` Rajneesh Bhardwaj
2017-03-16 16:05 ` Andy Shevchenko
2017-03-16 18:13 ` Rajneesh Bhardwaj
2017-03-16 20:12 ` Andy Shevchenko
2017-03-16 21:15 ` sathyanarayanan kuppuswamy
2017-03-16 18:50 ` sathyanarayanan kuppuswamy
2017-03-16 19:20 ` Rajneesh Bhardwaj
2017-03-16 21:05 ` sathyanarayanan kuppuswamy
2017-03-17 0:41 ` [PATCH v2 1/4] platform/x86: intel_pmc_ipc: fix gcr offset Kuppuswamy Sathyanarayanan
2017-03-17 0:41 ` [PATCH v2 2/4] platform/x86: intel_pmc_ipc: Add pmc gcr read/write api's Kuppuswamy Sathyanarayanan
2017-03-17 11:26 ` Rajneesh Bhardwaj
2017-03-17 17:11 ` sathyanarayanan kuppuswamy
2017-03-17 0:41 ` [PATCH v2 3/4] watchdog: iTCO_wdt: Fix PMC GCR memory mapping failure Kuppuswamy Sathyanarayanan
2017-03-17 11:43 ` Rajneesh Bhardwaj
2017-03-17 13:40 ` Guenter Roeck
2017-03-17 14:05 ` Rajneesh Bhardwaj
2017-03-17 14:25 ` Andy Shevchenko
2017-03-17 17:37 ` sathyanarayanan kuppuswamy
2017-03-17 18:38 ` Andy Shevchenko
2017-03-17 18:50 ` sathyanarayanan kuppuswamy
2017-03-17 17:24 ` sathyanarayanan kuppuswamy
2017-03-17 17:50 ` Guenter Roeck
2017-03-17 18:39 ` sathyanarayanan kuppuswamy
2017-03-17 17:15 ` sathyanarayanan kuppuswamy
2017-03-20 2:52 ` kbuild test robot [this message]
2017-03-17 0:41 ` [PATCH v2 4/4] platform/x86: intel_pmc_ipc: remove iTCO GCR mem resource Kuppuswamy Sathyanarayanan
2017-03-17 11:47 ` Rajneesh Bhardwaj
2017-03-17 11:13 ` [PATCH v2 1/4] platform/x86: intel_pmc_ipc: fix gcr offset Rajneesh Bhardwaj
2017-03-17 17:06 ` sathyanarayanan kuppuswamy
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=201703201035.ghLGuxMG%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=andy@infradead.org \
--cc=david.e.box@linux.intel.com \
--cc=dvhart@infradead.org \
--cc=kbuild-all@01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=platform-driver-x86@vger.kernel.org \
--cc=qipeng.zha@intel.com \
--cc=rajneesh.bhardwaj@intel.com \
--cc=sathyanarayanan.kuppuswamy@linux.intel.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
all inboxes | Powered by JetHome®