Linux RTC
 help / color / mirror / Atom feed
From: kbuild test robot <lkp@intel.com>
To: Gabriele Mazzotta <gabriele.mzt@gmail.com>
Cc: kbuild-all@01.org, alexandre.belloni@free-electrons.com,
	a.zummo@towertech.it, rtc-linux@googlegroups.com,
	linux-kernel@vger.kernel.org, matthew.garrett@nebula.com,
	Gabriele Mazzotta <gabriele.mzt@gmail.com>
Subject: [rtc-linux] Re: [PATCH v3 1/2] rtc-cmos: Clear ACPI-driven alarms upon resume
Date: Thu, 15 Sep 2016 04:12:03 +0800	[thread overview]
Message-ID: <201609150444.SoDJGLl1%fengguang.wu@intel.com> (raw)
In-Reply-To: <20160914190841.10684-1-gabriele.mzt@gmail.com>

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

Hi Gabriele,

[auto build test ERROR on abelloni/rtc-next]
[also build test ERROR on v4.8-rc6 next-20160914]
[if your patch is applied to the wrong git tree, please drop us a note to help improve the system]
[Suggest to use git(>=2.9.0) format-patch --base=<commit> (or --base=auto for convenience) to record what (public, well-known) commit your patch series was built on]
[Check https://git-scm.com/docs/git-format-patch for more information]

url:    https://github.com/0day-ci/linux/commits/Gabriele-Mazzotta/rtc-cmos-Clear-ACPI-driven-alarms-upon-resume/20160915-031802
base:   https://git.kernel.org/pub/scm/linux/kernel/git/abelloni/linux.git rtc-next
config: i386-defconfig (attached as .config)
compiler: gcc-6 (Debian 6.1.1-9) 6.1.1 20160705
reproduce:
        # save the attached .config to linux build tree
        make ARCH=i386 

All errors (new ones prefixed by >>):

   drivers/rtc/rtc-cmos.c: In function 'cmos_resume':
>> drivers/rtc/rtc-cmos.c:941:9: error: 'acpi_gbl_FADT' undeclared (first use in this function)
          !(acpi_gbl_FADT.flags & ACPI_FADT_FIXED_RTC)) {
            ^~~~~~~~~~~~~
   drivers/rtc/rtc-cmos.c:941:9: note: each undeclared identifier is reported only once for each function it appears in
>> drivers/rtc/rtc-cmos.c:941:31: error: 'ACPI_FADT_FIXED_RTC' undeclared (first use in this function)
          !(acpi_gbl_FADT.flags & ACPI_FADT_FIXED_RTC)) {
                                  ^~~~~~~~~~~~~~~~~~~
>> drivers/rtc/rtc-cmos.c:942:4: error: unknown type name 'acpi_status'
       acpi_status status;
       ^~~~~~~~~~~
>> drivers/rtc/rtc-cmos.c:943:4: error: unknown type name 'acpi_event_status'
       acpi_event_status rtc_status;
       ^~~~~~~~~~~~~~~~~
>> drivers/rtc/rtc-cmos.c:945:13: error: implicit declaration of function 'acpi_get_event_status' [-Werror=implicit-function-declaration]
       status = acpi_get_event_status(ACPI_EVENT_RTC,
                ^~~~~~~~~~~~~~~~~~~~~
>> drivers/rtc/rtc-cmos.c:945:35: error: 'ACPI_EVENT_RTC' undeclared (first use in this function)
       status = acpi_get_event_status(ACPI_EVENT_RTC,
                                      ^~~~~~~~~~~~~~
>> drivers/rtc/rtc-cmos.c:947:8: error: implicit declaration of function 'ACPI_FAILURE' [-Werror=implicit-function-declaration]
       if (ACPI_FAILURE(status)) {
           ^~~~~~~~~~~~
>> drivers/rtc/rtc-cmos.c:949:28: error: 'ACPI_EVENT_FLAG_SET' undeclared (first use in this function)
       } else if (rtc_status & ACPI_EVENT_FLAG_SET) {
                               ^~~~~~~~~~~~~~~~~~~
   In file included from include/acpi/acpi.h:64:0,
                    from include/linux/acpi.h:33,
                    from drivers/rtc/rtc-cmos.c:987:
   include/acpi/acpixf.h: At top level:
>> include/acpi/acpixf.h:705:5: error: conflicting types for 'acpi_get_event_status'
        acpi_get_event_status(u32 event,
        ^
   include/acpi/acpixf.h:95:2: note: in definition of macro 'ACPI_EXTERNAL_RETURN_STATUS'
     prototype;
     ^~~~~~~~~
   include/acpi/acpixf.h:704:1: note: in expansion of macro 'ACPI_HW_DEPENDENT_RETURN_STATUS'
    ACPI_HW_DEPENDENT_RETURN_STATUS(acpi_status
    ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
   drivers/rtc/rtc-cmos.c:945:13: note: previous implicit declaration of 'acpi_get_event_status' was here
       status = acpi_get_event_status(ACPI_EVENT_RTC,
                ^~~~~~~~~~~~~~~~~~~~~
   cc1: some warnings being treated as errors

vim +/acpi_gbl_FADT +941 drivers/rtc/rtc-cmos.c

   935				rtc_update_irq(cmos->rtc, 1, mask);
   936				tmp &= ~RTC_AIE;
   937				hpet_mask_rtc_irq_bit(RTC_AIE);
   938			} while (mask & RTC_AIE);
   939	
   940			if ((tmp & RTC_AIE) &&
 > 941			    !(acpi_gbl_FADT.flags & ACPI_FADT_FIXED_RTC)) {
 > 942				acpi_status status;
 > 943				acpi_event_status rtc_status;
   944	
 > 945				status = acpi_get_event_status(ACPI_EVENT_RTC,
   946							       &rtc_status);
 > 947				if (ACPI_FAILURE(status)) {
   948					dev_err(dev, "Could not get RTC status\n");
 > 949				} else if (rtc_status & ACPI_EVENT_FLAG_SET) {
   950					tmp &= ~RTC_AIE;
   951					CMOS_WRITE(tmp, RTC_CONTROL);
   952					rtc_update_irq(cmos->rtc, 1, mask);

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

-- 
You received this message because you are subscribed to "rtc-linux".
Membership options at http://groups.google.com/group/rtc-linux .
Please read http://groups.google.com/group/rtc-linux/web/checklist
before submitting a driver.
--- 
You received this message because you are subscribed to the Google Groups "rtc-linux" group.
To unsubscribe from this group and stop receiving emails from it, send an email to rtc-linux+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

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

  parent reply	other threads:[~2016-09-14 20:12 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-14 19:08 [rtc-linux] [PATCH v3 1/2] rtc-cmos: Clear ACPI-driven alarms upon resume Gabriele Mazzotta
2016-09-14 19:08 ` [rtc-linux] [PATCH v3 2/2] rtc-cmos: Restore alarm after resume Gabriele Mazzotta
2016-09-14 20:12 ` kbuild test robot [this message]
2016-09-14 22:49 ` [rtc-linux] Re: [PATCH v3 1/2] rtc-cmos: Clear ACPI-driven alarms upon resume kbuild test robot
2016-09-19 22:21 ` Alexandre Belloni

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=201609150444.SoDJGLl1%fengguang.wu@intel.com \
    --to=lkp@intel.com \
    --cc=a.zummo@towertech.it \
    --cc=alexandre.belloni@free-electrons.com \
    --cc=gabriele.mzt@gmail.com \
    --cc=kbuild-all@01.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=matthew.garrett@nebula.com \
    --cc=rtc-linux@googlegroups.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