From: Pavel Machek <pavel@ucw.cz>
To: hans.verkuil@cisco.com, mchehab+samsung@kernel.org,
kernel list <linux-kernel@vger.kernel.org>
Subject: Re: v4.19-rc0: compile problem in ./include/media/cec.h:82:24:
Date: Wed, 22 Aug 2018 23:12:12 +0200 [thread overview]
Message-ID: <20180822211212.GA30897@amd> (raw)
In-Reply-To: <20180822204426.GA23832@amd>
[-- Attachment #1: Type: text/plain, Size: 1296 bytes --]
Hi!
> I'm getting this in -rc0:
>
> CC drivers/gpu/drm/ttm/ttm_tt.o
> In file included from ./include/media/cec-notifier.h:13:0,
> from drivers/gpu/drm/i915/intel_drv.h:42,
> from
> drivers/gpu/drm/i915/i915_trace.h:11,
> from drivers/gpu/drm/i915/i915_drv.h:2667,
> from
> drivers/gpu/drm/i915/i915_irq.c:36:
> ./include/media/cec.h:82:24: error: ‘CEC_EVENT_PIN_5V_HIGH’
> undeclared here (not in a function)
> #define CEC_NUM_EVENTS CEC_EVENT_PIN_5V_HIGH
> ^
> ./include/media/cec.h:94:26: note: in
> expansion of macro ‘CEC_NUM_EVENTS’
> struct list_head events[CEC_NUM_EVENTS]; /* queued events */
> ^
> CC drivers/input/serio/serport.o
>
> Reverting 4786b0d6f3ca6da8db02b0a58cd2b785cb0b80ab seems to help.
No, sorry, it does not. I was confused. Let me try
HDMI CEC support (MEDIA_CEC_SUPPORT) [N/y/?] (NEW) y
No change.
Let me add
#include <uapi/linux/cec.h>
into include/media/cec.h... no.
Any ideas?
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]
next prev parent reply other threads:[~2018-08-22 21:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-22 20:44 v4.19-rc0: compile problem in ./include/media/cec.h:82:24: Pavel Machek
2018-08-22 21:12 ` Pavel Machek [this message]
2018-08-23 6:38 ` Hans Verkuil
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=20180822211212.GA30897@amd \
--to=pavel@ucw.cz \
--cc=hans.verkuil@cisco.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mchehab+samsung@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.