From: Rajneesh Bhardwaj <rajneesh.bhardwaj@intel.com>
To: kbuild test robot <lkp@intel.com>
Cc: Shanth Murthy <shanth.murthy@intel.com>,
kbuild-all@01.org, platform-driver-x86@vger.kernel.org,
dvhart@infradead.org, andriy.shevchenko@linux.intel.com,
qipeng.zha@intel.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] platform/x86: intel_pmc_ipc: read s0ix residency API
Date: Tue, 7 Feb 2017 00:01:23 +0530 [thread overview]
Message-ID: <20170206183122.GA14651@rajaneesh-OptiPlex-9010> (raw)
In-Reply-To: <201702062146.dHHXqmBG%fengguang.wu@intel.com>
On Mon, Feb 06, 2017 at 10:01:43PM +0800, kbuild test robot wrote:
> Hi Shanth,
>
> [auto build test ERROR on tip/x86/core]
> [also build test ERROR on v4.10-rc7]
> [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/Shanth-Murthy/platform-x86-intel_pmc_ipc-read-s0ix-residency-API/20170206-213213
> config: i386-randconfig-x007-201706 (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/platform/x86/intel_pmc_ipc.c: In function 'gcr_data_readq':
> >> drivers/platform/x86/intel_pmc_ipc.c:193:9: error: implicit declaration of function 'readq' [-Werror=implicit-function-declaration]
> return readq(ipcdev.ipc_base + offset);
> ^~~~~
> cc1: some warnings being treated as errors
>
> vim +/readq +193 drivers/platform/x86/intel_pmc_ipc.c
>
> 187 {
> 188 return readl(ipcdev.ipc_base + IPC_READ_BUFFER + offset);
> 189 }
> 190
> 191 static inline u64 gcr_data_readq(u32 offset)
> 192 {
> > 193 return readq(ipcdev.ipc_base + offset);
Seems readq is not available for 32 bit configuration. Will send a fix soon.
> 194 }
> 195
> 196 static int intel_pmc_ipc_check_status(void)
>
> ---
> 0-DAY kernel test infrastructure Open Source Technology Center
> https://lists.01.org/pipermail/kbuild-all Intel Corporation
--
Best Regards,
Rajneesh
next prev parent reply other threads:[~2017-02-06 18:31 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-06 13:09 Shanth Murthy
2017-02-06 14:01 ` kbuild test robot
2017-02-06 18:31 ` Rajneesh Bhardwaj [this message]
2017-02-07 10:19 ` Andy Shevchenko
2017-02-08 12:02 ` Rajneesh Bhardwaj
2017-02-08 12:52 ` Andy Shevchenko
2017-02-09 6:47 ` Rajneesh Bhardwaj
2017-02-09 11:33 ` Andy Shevchenko
2017-02-09 12:02 ` Rajneesh Bhardwaj
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=20170206183122.GA14651@rajaneesh-OptiPlex-9010 \
--to=rajneesh.bhardwaj@intel.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=dvhart@infradead.org \
--cc=kbuild-all@01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=platform-driver-x86@vger.kernel.org \
--cc=qipeng.zha@intel.com \
--cc=shanth.murthy@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®