From: kbuild test robot <lkp@intel.com>
To: Dou Liyang <douly.fnst@cn.fujitsu.com>
Cc: kbuild-all@01.org, linux-kernel@vger.kernel.org, x86@kernel.org,
linux-acpi@vger.kernel.org, lenb@kernel.org, rjw@rjwysocki.net,
tglx@linutronix.de, rafael@kernel.org,
indou.takao@jp.fujitsu.com,
Dou Liyang <douly.fnst@cn.fujitsu.com>
Subject: Re: [RESEND PATCH v2] acpi/processor: Fix the return value of acpi_processor_ids_walk()
Date: Thu, 23 Aug 2018 20:46:13 +0800 [thread overview]
Message-ID: <201808231911.FnMRVHjo%fengguang.wu@intel.com> (raw)
In-Reply-To: <20180822074453.26959-1-douly.fnst@cn.fujitsu.com>
[-- Attachment #1: Type: text/plain, Size: 2484 bytes --]
Hi Dou,
Thank you for the patch! Yet something to improve:
[auto build test ERROR on pm/linux-next]
[also build test ERROR on v4.18 next-20180822]
[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/Dou-Liyang/acpi-processor-Fix-the-return-value-of-acpi_processor_ids_walk/20180823-165002
base: https://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm.git linux-next
config: i386-randconfig-h0-08231413 (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=i386
All errors (new ones prefixed by >>):
drivers//acpi/acpi_processor.c: In function 'acpi_processor_ids_walk':
>> drivers//acpi/acpi_processor.c:646:3: error: implicit declaration of function 'acpi_ut_status_exit' [-Werror=implicit-function-declaration]
return_ACPI_STATUS(status);
^
cc1: some warnings being treated as errors
vim +/acpi_ut_status_exit +646 drivers//acpi/acpi_processor.c
632
633 static acpi_status __init acpi_processor_ids_walk(acpi_handle handle,
634 u32 lvl,
635 void *context,
636 void **rv)
637 {
638 acpi_status status;
639 acpi_object_type acpi_type;
640 unsigned long long uid;
641 union acpi_object object = { 0 };
642 struct acpi_buffer buffer = { sizeof(union acpi_object), &object };
643
644 status = acpi_get_type(handle, &acpi_type);
645 if (ACPI_FAILURE(status))
> 646 return_ACPI_STATUS(status);
647
648 switch (acpi_type) {
649 case ACPI_TYPE_PROCESSOR:
650 status = acpi_evaluate_object(handle, NULL, NULL, &buffer);
651 if (ACPI_FAILURE(status))
652 goto err;
653 uid = object.processor.proc_id;
654 break;
655
656 case ACPI_TYPE_DEVICE:
657 status = acpi_evaluate_integer(handle, "_UID", NULL, &uid);
658 if (ACPI_FAILURE(status))
659 goto err;
660 break;
661 default:
662 goto err;
663 }
664
665 processor_validated_ids_update(uid);
666 return AE_OK;
667
668 err:
669 /* Exit on error, but don't abort the namespace walk */
670 acpi_handle_info(handle, "Invalid processor object\n");
671 return AE_OK;
672
---
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: 32521 bytes --]
prev parent reply other threads:[~2018-08-23 12:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-22 7:44 [RESEND PATCH v2] acpi/processor: Fix the return value of acpi_processor_ids_walk() Dou Liyang
2018-08-23 11:57 ` kbuild test robot
2018-08-23 12:46 ` 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=201808231911.FnMRVHjo%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=douly.fnst@cn.fujitsu.com \
--cc=indou.takao@jp.fujitsu.com \
--cc=kbuild-all@01.org \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rafael@kernel.org \
--cc=rjw@rjwysocki.net \
--cc=tglx@linutronix.de \
--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).