linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: kbuild test robot <lkp@intel.com>
To: Irina Tirdea <irina.tirdea@intel.com>
Cc: kbuild-all@01.org, linux-clk@vger.kernel.org, x86@kernel.org,
	platform-driver-x86@vger.kernel.org,
	Stephen Boyd <sboyd@codeaurora.org>,
	Darren Hart <dvhart@infradead.org>,
	Thomas Gleixner <tglx@linutronix.de>,
	Michael Turquette <mturquette@baylibre.com>,
	Ingo Molnar <mingo@redhat.com>, "H. Peter Anvin" <hpa@zytor.com>,
	alsa-devel@alsa-project.org, Mark Brown <broonie@kernel.org>,
	Takashi Iwai <tiwai@suse.com>,
	Pierre-Louis Bossart <pierre-louis.bossart@intel.com>,
	"Rafael J. Wysocki" <rjw@rjwysocki.net>,
	Len Brown <lenb@kernel.org>,
	Irina Tirdea <irina.tirdea@intel.com>,
	linux-acpi@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v5 1/2] arch/x86/platform/atom: Move pmc_atom to drivers/platform/x86
Date: Thu, 8 Dec 2016 04:54:27 +0800	[thread overview]
Message-ID: <201612080438.LGk0sXyK%fengguang.wu@intel.com> (raw)
In-Reply-To: <1481125406-29097-2-git-send-email-irina.tirdea@intel.com>

[-- Attachment #1: Type: text/plain, Size: 969 bytes --]

Hi Irina,

[auto build test ERROR on tip/x86/core]
[also build test ERROR on v4.9-rc8]
[cannot apply to platform-drivers-x86/for-next next-20161207]
[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/Irina-Tirdea/Add-platform-clock-for-BayTrail-platforms/20161208-024855
config: x86_64-randconfig-b0-12080241 (attached as .config)
compiler: gcc-4.4 (Debian 4.4.7-8) 4.4.7
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 `lpss_iosf_enter_d3_state':
>> acpi_lpss.c:(.text+0x67797): undefined reference to `pmc_atom_read'
   acpi_lpss.c:(.text+0x677bb): undefined reference to `pmc_atom_read'

---
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: 24565 bytes --]

  reply	other threads:[~2016-12-07 20:55 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-07 15:43 [PATCH v5 0/2] Add platform clock for BayTrail platforms Irina Tirdea
2016-12-07 15:43 ` [PATCH v5 1/2] arch/x86/platform/atom: Move pmc_atom to drivers/platform/x86 Irina Tirdea
2016-12-07 20:54   ` kbuild test robot [this message]
2016-12-07 15:43 ` [PATCH v5 2/2] clk: x86: Add Atom PMC platform clocks Irina Tirdea
2016-12-09  0:25   ` Stephen Boyd
2016-12-09 18:09     ` Tirdea, Irina

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=201612080438.LGk0sXyK%fengguang.wu@intel.com \
    --to=lkp@intel.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@kernel.org \
    --cc=dvhart@infradead.org \
    --cc=hpa@zytor.com \
    --cc=irina.tirdea@intel.com \
    --cc=kbuild-all@01.org \
    --cc=lenb@kernel.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-clk@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=mturquette@baylibre.com \
    --cc=pierre-louis.bossart@intel.com \
    --cc=platform-driver-x86@vger.kernel.org \
    --cc=rjw@rjwysocki.net \
    --cc=sboyd@codeaurora.org \
    --cc=tglx@linutronix.de \
    --cc=tiwai@suse.com \
    --cc=x86@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;
as well as URLs for NNTP newsgroup(s).