From: Patchwork <patchwork@emeril.freedesktop.org>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: ✗ Fi.CI.BAT: failure for ACPI et al: convert to use new UUID API
Date: Wed, 31 May 2017 19:45:46 -0000 [thread overview]
Message-ID: <20170531194546.13266.13039@emeril.freedesktop.org> (raw)
In-Reply-To: <20170531194152.65927-1-andriy.shevchenko@linux.intel.com>
== Series Details ==
Series: ACPI et al: convert to use new UUID API
URL : https://patchwork.freedesktop.org/series/25121/
State : failure
== Summary ==
CHK include/config/kernel.release
CHK include/generated/uapi/linux/version.h
CHK include/generated/utsrelease.h
CHK include/generated/bounds.h
CHK include/generated/timeconst.h
CHK include/generated/asm-offsets.h
CALL scripts/checksyscalls.sh
CHK scripts/mod/devicetable-offsets.h
CC init/main.o
In file included from ./include/linux/acpi.h:44:0,
from init/main.c:29:
./include/acpi/acpi_bus.h:64:47: error: unknown type name ‘guid_t’
bool acpi_check_dsm(acpi_handle handle, const guid_t *guid, u64 rev, u64 funcs);
^
./include/acpi/acpi_bus.h:65:64: error: unknown type name ‘guid_t’
union acpi_object *acpi_evaluate_dsm(acpi_handle handle, const guid_t *guid,
^
./include/acpi/acpi_bus.h:69:51: error: unknown type name ‘guid_t’
acpi_evaluate_dsm_typed(acpi_handle handle, const guid_t *guid, u64 rev,
^
scripts/Makefile.build:302: recipe for target 'init/main.o' failed
make[1]: *** [init/main.o] Error 1
Makefile:1016: recipe for target 'init' failed
make: *** [init] Error 2
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2017-05-31 19:45 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-31 19:41 [PATCH v2 0/5] ACPI et al: convert to use new UUID API Andy Shevchenko
2017-05-31 19:41 ` [PATCH v2 1/5] acpi, nfit: Switch to use new generic " Andy Shevchenko
2017-06-01 14:26 ` Dan Williams
2017-06-05 16:01 ` Christoph Hellwig
2017-06-05 16:18 ` Andy Shevchenko
2017-05-31 19:41 ` [PATCH v2 2/5] ACPI / APEI: " Andy Shevchenko
2017-05-31 23:56 ` kbuild test robot
2017-06-01 9:50 ` Andy Shevchenko
2017-06-05 16:01 ` Christoph Hellwig
2017-06-05 16:19 ` Andy Shevchenko
2017-06-05 16:22 ` Christoph Hellwig
2017-06-05 16:28 ` Andy Shevchenko
2017-05-31 19:41 ` [PATCH v2 3/5] ACPI / bus: " Andy Shevchenko
2017-05-31 22:42 ` Rafael J. Wysocki
2017-05-31 23:56 ` kbuild test robot
2017-06-01 0:05 ` kbuild test robot
2017-06-05 16:03 ` Christoph Hellwig
2017-06-05 16:20 ` Andy Shevchenko
2017-06-05 20:37 ` Rafael J. Wysocki
2017-06-06 9:58 ` Christoph Hellwig
2017-05-31 19:41 ` [PATCH v2 4/5] ACPI / extlog: " Andy Shevchenko
2017-06-05 16:06 ` Christoph Hellwig
2017-06-05 16:23 ` Andy Shevchenko
2017-06-05 21:23 ` Christoph Hellwig
2017-05-31 19:41 ` [PATCH v2 5/5] ACPI: Switch to use generic guid_t in acpi_evaluate_dsm() Andy Shevchenko
2017-05-31 20:21 ` Mark Brown
2017-05-31 22:42 ` Rafael J. Wysocki
2017-06-01 6:03 ` Christoph Hellwig
2017-06-01 0:08 ` kbuild test robot
2017-06-01 0:11 ` kbuild test robot
2017-06-01 14:12 ` Jarkko Sakkinen
2017-06-01 14:24 ` Dan Williams
2017-06-02 12:25 ` Adrian Hunter
2017-05-31 19:45 ` [PATCH v2 0/5] ACPI et al: convert to use new UUID API Christoph Hellwig
2017-05-31 19:45 ` Patchwork [this message]
2017-05-31 20:07 ` Andy Shevchenko
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=20170531194546.13266.13039@emeril.freedesktop.org \
--to=patchwork@emeril.freedesktop.org \
--cc=andriy.shevchenko@linux.intel.com \
--cc=intel-gfx@lists.freedesktop.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).