Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754075AbcDSNAM (ORCPT ); Tue, 19 Apr 2016 09:00:12 -0400 Received: from foss.arm.com ([217.140.101.70]:39772 "EHLO foss.arm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752506AbcDSNAK (ORCPT ); Tue, 19 Apr 2016 09:00:10 -0400 Subject: Re: [PATCH v4 1/5] ACPI / processor_idle: introduce ARCH_SUPPORTS_ACPI_PROCESSOR_CSTATE To: kbuild test robot References: <201604192041.pUqHza4O%fengguang.wu@intel.com> Cc: Sudeep Holla , kbuild-all@01.org, "Rafael J. Wysocki" , linux-acpi@vger.kernel.org, linux-kernel@vger.kernel.org, linux-arm-kernel@lists.infradead.org, Lorenzo Pieralisi , Al Stone , Prashanth Prakash , Ashwin Chaugule , x86@kernel.org, linux-ia64@vger.kernel.org From: Sudeep Holla Organization: ARM Message-ID: <57162BD5.90006@arm.com> Date: Tue, 19 Apr 2016 14:00:05 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.6.0 MIME-Version: 1.0 In-Reply-To: <201604192041.pUqHza4O%fengguang.wu@intel.com> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 933 Lines: 26 Hi, On 19/04/16 13:49, kbuild test robot wrote: > Hi, > > [auto build test ERROR on pm/linux-next] > [also build test ERROR on v4.6-rc4 next-20160419] > [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/Sudeep-Holla/ACPI-processor_idle-Add-ACPI-v6-0-LPI-support/20160419-203500 > base: https://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm.git linux-next > config: i386-randconfig-x000-201616 (attached as .config) > reproduce: > # save the attached .config to linux build tree > make ARCH=i386 > > Note: the linux-review/Sudeep-Holla/ACPI-processor_idle-Add-ACPI-v6-0-LPI-support/20160419-203500 HEAD c51fc2a756d7b0dce908a4ca043d1d458c400af5 builds fine. > It only hurts bisectibility. > Thanks for the report, it's now fixed locally. It will part of the next version. -- Regards, Sudeep