From: Jani Nikula <jani.nikula@linux.intel.com>
To: Patchwork <patchwork@emeril.freedesktop.org>,
Rajat Jain <rajatja@google.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: ✗ Fi.CI.BUILD: failure for drm: Add support for integrated privacy screens
Date: Thu, 24 Oct 2019 10:01:14 +0300 [thread overview]
Message-ID: <87blu6eif9.fsf@intel.com> (raw)
In-Reply-To: <20191024014832.27072.65879@emeril.freedesktop.org>
On Thu, 24 Oct 2019, Patchwork <patchwork@emeril.freedesktop.org> wrote:
> == Series Details ==
>
> Series: drm: Add support for integrated privacy screens
> URL : https://patchwork.freedesktop.org/series/68472/
> State : failure
>
> == Summary ==
>
> CALL scripts/checksyscalls.sh
> CALL scripts/atomic/check-atomics.sh
> DESCEND objtool
> CHK include/generated/compile.h
> Kernel: arch/x86/boot/bzImage is ready (#1)
> Building modules, stage 2.
> MODPOST 122 modules
> ERROR: "drm_privacy_screen_present" [drivers/gpu/drm/i915/i915.ko] undefined!
This means you need to EXPORT_SYMBOL(drm_privacy_screen_present).
BR,
Jani.
> scripts/Makefile.modpost:93: recipe for target '__modpost' failed
> make[1]: *** [__modpost] Error 1
> Makefile:1282: recipe for target 'modules' failed
> make: *** [modules] Error 2
>
> _______________________________________________
> Intel-gfx mailing list
> Intel-gfx@lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/intel-gfx
--
Jani Nikula, Intel Open Source Graphics Center
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
WARNING: multiple messages have this Message-ID (diff)
From: Jani Nikula <jani.nikula@linux.intel.com>
To: Patchwork <patchwork@emeril.freedesktop.org>,
Rajat Jain <rajatja@google.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [Intel-gfx] ✗ Fi.CI.BUILD: failure for drm: Add support for integrated privacy screens
Date: Thu, 24 Oct 2019 10:01:14 +0300 [thread overview]
Message-ID: <87blu6eif9.fsf@intel.com> (raw)
Message-ID: <20191024070114.N35_HC-QwDEKSYPAKpEwjnTVzF_DzdGvotJ-IPOLtqs@z> (raw)
In-Reply-To: <20191024014832.27072.65879@emeril.freedesktop.org>
On Thu, 24 Oct 2019, Patchwork <patchwork@emeril.freedesktop.org> wrote:
> == Series Details ==
>
> Series: drm: Add support for integrated privacy screens
> URL : https://patchwork.freedesktop.org/series/68472/
> State : failure
>
> == Summary ==
>
> CALL scripts/checksyscalls.sh
> CALL scripts/atomic/check-atomics.sh
> DESCEND objtool
> CHK include/generated/compile.h
> Kernel: arch/x86/boot/bzImage is ready (#1)
> Building modules, stage 2.
> MODPOST 122 modules
> ERROR: "drm_privacy_screen_present" [drivers/gpu/drm/i915/i915.ko] undefined!
This means you need to EXPORT_SYMBOL(drm_privacy_screen_present).
BR,
Jani.
> scripts/Makefile.modpost:93: recipe for target '__modpost' failed
> make[1]: *** [__modpost] Error 1
> Makefile:1282: recipe for target 'modules' failed
> make: *** [modules] Error 2
>
> _______________________________________________
> Intel-gfx mailing list
> Intel-gfx@lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/intel-gfx
--
Jani Nikula, Intel Open Source Graphics Center
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2019-10-24 7:01 UTC|newest]
Thread overview: 55+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-23 0:12 [PATCH] drm: Add support for integrated privacy screens Rajat Jain
2019-10-23 0:12 ` [Intel-gfx] " Rajat Jain
2019-10-23 9:21 ` Daniel Vetter
2019-10-23 9:21 ` [Intel-gfx] " Daniel Vetter
2019-10-24 1:48 ` ✗ Fi.CI.BUILD: failure for " Patchwork
2019-10-24 1:48 ` [Intel-gfx] " Patchwork
2019-10-24 7:01 ` Jani Nikula [this message]
2019-10-24 7:01 ` Jani Nikula
2019-10-24 18:18 ` Rajat Jain
2019-10-24 18:18 ` [Intel-gfx] " Rajat Jain
2019-10-24 11:06 ` [PATCH] " Pavel Machek
2019-10-24 11:06 ` [Intel-gfx] " Pavel Machek
2019-10-24 11:20 ` Thierry Reding
2019-10-24 11:20 ` [Intel-gfx] " Thierry Reding
2019-10-24 20:45 ` Rajat Jain
2019-10-25 11:36 ` Thierry Reding
2019-10-25 11:36 ` [Intel-gfx] " Thierry Reding
2019-10-25 19:00 ` Rajat Jain
2019-10-25 19:00 ` [Intel-gfx] " Rajat Jain
2019-10-25 19:03 ` Daniel Vetter
2019-10-25 19:03 ` [Intel-gfx] " Daniel Vetter
2019-10-28 8:12 ` Pekka Paalanen
2019-10-28 8:12 ` [Intel-gfx] " Pekka Paalanen
2019-10-26 11:07 ` Daniel Stone
2019-10-26 11:07 ` Daniel Stone
2019-10-26 17:18 ` Daniel Vetter
2019-10-26 17:18 ` Daniel Vetter
2019-10-24 18:57 ` kbuild test robot
2019-10-24 18:57 ` [Intel-gfx] " kbuild test robot
2019-10-24 19:44 ` kbuild test robot
2019-10-24 19:44 ` [Intel-gfx] " kbuild test robot
2019-11-04 19:41 ` [PATCH v2 1/3] drm/i915: Move the code to populate ACPI device ID into intel_acpi Rajat Jain
2019-11-04 19:41 ` [Intel-gfx] " Rajat Jain
2019-11-04 19:41 ` [PATCH v2 2/3] drm/i915: Lookup and attach ACPI device node for connectors Rajat Jain
2019-11-04 19:41 ` [Intel-gfx] " Rajat Jain
2019-11-20 14:50 ` Jani Nikula
2019-11-20 14:50 ` [Intel-gfx] " Jani Nikula
2019-12-05 9:34 ` Rajat Jain
2019-11-04 19:41 ` [PATCH v2 3/3] drm/i915: Add support for integrated privacy screens Rajat Jain
2019-11-04 19:41 ` [Intel-gfx] " Rajat Jain
2019-11-12 19:12 ` Rajat Jain
2019-11-12 19:12 ` [Intel-gfx] " Rajat Jain
2019-11-12 19:12 ` Rajat Jain
2019-11-12 19:12 ` [Intel-gfx] " Rajat Jain
2019-11-20 15:10 ` Jani Nikula
2019-11-20 15:10 ` [Intel-gfx] " Jani Nikula
2019-11-20 21:35 ` Rajat Jain
2019-11-20 21:35 ` [Intel-gfx] " Rajat Jain
2019-11-20 15:04 ` Jani Nikula
2019-11-20 15:04 ` [Intel-gfx] " Jani Nikula
2019-12-05 9:34 ` Rajat Jain
2019-12-20 20:39 ` Rajat Jain
2019-11-20 14:40 ` [PATCH v2 1/3] drm/i915: Move the code to populate ACPI device ID into intel_acpi Jani Nikula
2019-11-20 14:40 ` [Intel-gfx] " Jani Nikula
2019-12-05 9:34 ` Rajat Jain
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=87blu6eif9.fsf@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=patchwork@emeril.freedesktop.org \
--cc=rajatja@google.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