From: Jonathan Cameron <jic23@cam.ac.uk>
To: "linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>
Subject: Build issue.
Date: Fri, 01 Jul 2011 15:37:10 +0100 [thread overview]
Message-ID: <4E0DDB96.3090707@cam.ac.uk> (raw)
No time to look into this now, but linux next today is giving:
CHK include/linux/version.h
CHK include/generated/utsrelease.h
make[1]: `include/generated/mach-types.h' is up to date.
CALL scripts/checksyscalls.sh
CHK include/generated/compile.h
CC drivers/media/video/omap/omap_vout.o
drivers/media/video/omap/omap_vout.c: In function 'omap_vout_probe':
drivers/media/video/omap/omap_vout.c:2549:15: error: 'struct omap_dss_driver' has no member named 'set_update_mode'
drivers/media/video/omap/omap_vout.c:2550:12: error: 'struct omap_dss_driver' has no member named 'set_update_mode'
drivers/media/video/omap/omap_vout.c:2551:8: error: 'OMAP_DSS_UPDATE_MANUAL' undeclared (first use in this function)
drivers/media/video/omap/omap_vout.c:2551:8: note: each undeclared identifier is reported only once for each function it appears in
drivers/media/video/omap/omap_vout.c:2553:15: error: 'struct omap_dss_driver' has no member named 'set_update_mode'
drivers/media/video/omap/omap_vout.c:2554:12: error: 'struct omap_dss_driver' has no member named 'set_update_mode'
drivers/media/video/omap/omap_vout.c:2555:8: error: 'OMAP_DSS_UPDATE_AUTO' undeclared (first use in this function)
make[4]: *** [drivers/media/video/omap/omap_vout.o] Error 1
make[3]: *** [drivers/media/video/omap] Error 2
make[2]: *** [drivers/media/video] Error 2
make[1]: *** [drivers/media] Error 2
make: *** [drivers] Error 2
Have I missed a relevant patch?
next reply other threads:[~2011-07-01 14:29 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-01 14:37 Jonathan Cameron [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-02-01 2:13 Build issue Guillaume Zajac
2012-02-01 3:11 ` Marcel Holtmann
2019-10-17 20:34 build issue Astolfo Rueda
2019-10-18 3:21 ` Rebecca Cran
2019-10-19 7:11 ` Sitsofe Wheeler
2019-10-27 20:34 ` Sitsofe Wheeler
2019-10-28 14:22 ` Astolfo Rueda
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=4E0DDB96.3090707@cam.ac.uk \
--to=jic23@cam.ac.uk \
--cc=linux-omap@vger.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.