mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: kbuild test robot <lkp@intel.com>
To: Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>
Cc: kbuild-all@01.org, rjw@rjwysocki.net, tony.luck@intel.com,
	bp@alien8.de, tglx@linutronix.de, mingo@redhat.com,
	hpa@zytor.com, lenb@kernel.org, linux-edac@vger.kernel.org,
	linux-kernel@vger.kernel.org,
	Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>
Subject: Re: [PATCH] acpi: Issue _OSC call for native thermal interrupt handling
Date: Thu, 17 Mar 2016 07:52:03 +0800	[thread overview]
Message-ID: <201603170745.zu1nGmOB%fengguang.wu@intel.com> (raw)
In-Reply-To: <1458167119-7686-1-git-send-email-srinivas.pandruvada@linux.intel.com>

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

Hi Srinivas,

[auto build test ERROR on pm/linux-next]
[also build test ERROR on v4.5 next-20160316]
[if your patch is applied to the wrong git tree, please drop us a note to help improving the system]

url:    https://github.com/0day-ci/linux/commits/Srinivas-Pandruvada/acpi-Issue-_OSC-call-for-native-thermal-interrupt-handling/20160317-063443
base:   https://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm.git linux-next
config: ia64-allnoconfig (attached as .config)
reproduce:
        wget https://git.kernel.org/cgit/linux/kernel/git/wfg/lkp-tests.git/plain/sbin/make.cross -O ~/bin/make.cross
        chmod +x ~/bin/make.cross
        # save the attached .config to linux build tree
        make.cross ARCH=ia64 

All errors (new ones prefixed by >>):

   drivers/acpi/acpi_processor.c: In function 'acpi_set_hwp_native_thermal_lvt_osc':
>> drivers/acpi/acpi_processor.c:510:2: error: implicit declaration of function 'static_cpu_has' [-Werror=implicit-function-declaration]
     if (!static_cpu_has(X86_FEATURE_HWP))
     ^
>> drivers/acpi/acpi_processor.c:510:22: error: 'X86_FEATURE_HWP' undeclared (first use in this function)
     if (!static_cpu_has(X86_FEATURE_HWP))
                         ^
   drivers/acpi/acpi_processor.c:510:22: note: each undeclared identifier is reported only once for each function it appears in
   cc1: some warnings being treated as errors

vim +/static_cpu_has +510 drivers/acpi/acpi_processor.c

   504			.cap.pointer = capbuf,
   505		};
   506	
   507		if (acpi_hwp_native_thermal_lvt_set)
   508			return AE_OK;
   509	
 > 510		if (!static_cpu_has(X86_FEATURE_HWP))
   511			return AE_OK;
   512	
   513		capbuf[0] = 0x0000;

---
0-DAY kernel test infrastructure                Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all                   Intel Corporation

[-- Attachment #2: .config.gz --]
[-- Type: application/octet-stream, Size: 5481 bytes --]

      parent reply	other threads:[~2016-03-16 23:53 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-16 22:25 Srinivas Pandruvada
2016-03-16 22:48 ` Rafael J. Wysocki
2016-03-16 22:58   ` Srinivas Pandruvada
2016-03-16 23:52 ` kbuild test robot [this message]

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=201603170745.zu1nGmOB%fengguang.wu@intel.com \
    --to=lkp@intel.com \
    --cc=bp@alien8.de \
    --cc=hpa@zytor.com \
    --cc=kbuild-all@01.org \
    --cc=lenb@kernel.org \
    --cc=linux-edac@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=rjw@rjwysocki.net \
    --cc=srinivas.pandruvada@linux.intel.com \
    --cc=tglx@linutronix.de \
    --cc=tony.luck@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®