From: Peter Ujfalusi <peter.ujfalusi@ti.com>
To: kernel-janitors@vger.kernel.org
Subject: Re: [omap-dss2:work:omap5-dt 83/133] include/linux/of.h:318:1: error: unknown type name 'device_node
Date: Thu, 06 Sep 2012 07:48:05 +0000 [thread overview]
Message-ID: <50485535.6060203@ti.com> (raw)
Hi,
On 09/06/2012 06:51 AM, Fengguang Wu wrote:
> Hi Peter,
>
> FYI, kernel build failed on
Thank you for report. AFAIK this is a work in progress tree for OMAP DSS2
maintained by Tomi Valkeinen (I have put him to CC).
Regards,
Péter
>
> tree: git://gitorious.org/linux-omap-dss2/linux work/omap5-dt
> head: 73fc80a0ac6b4a62eab3ce20150167f5be0233e7
> commit: 3fc0d2ee0ac2c9f927b4e4aa5aca915d85ec56eb [83/133] dt: Add empty of_find_node_by_name() function
> config: x86_64-allyesdebian (attached as .config)
>
> All related error/warning messages:
>
> In file included from arch/x86/kernel/irq.c:7:0:
> include/linux/of.h:318:1: error: unknown type name 'device_node'
> --
> In file included from arch/x86/include/asm/prom.h:17:0,
> from arch/x86/kernel/setup.c:115:
> include/linux/of.h:318:1: error: unknown type name 'device_node'
> --
> In file included from arch/x86/include/asm/prom.h:17:0,
> from arch/x86/kernel/irqinit.c:27:
> include/linux/of.h:318:1: error: unknown type name 'device_node'
> --
> In file included from arch/x86/kernel/rtc.c:10:0:
> include/linux/of.h:318:1: error: unknown type name 'device_node'
> --
> In file included from include/linux/i2c.h:36:0,
> from include/linux/fb.h:5,
> from fs/compat_ioctl.c:44:
> include/linux/of.h:318:1: error: unknown type name 'device_node'
> --
> In file included from kernel/irq/irqdomain.c:11:0:
> include/linux/of.h:318:1: error: unknown type name 'device_node'
> --
> In file included from drivers/ata/sata_mv.c:68:0:
> include/linux/of.h:318:1: error: unknown type name 'device_node'
> --
> In file included from drivers/base/core.c:21:0:
> include/linux/of.h:318:1: error: unknown type name 'device_node'
> --
> In file included from include/linux/i2c.h:36:0,
> from include/linux/fb.h:5,
> from arch/x86/video/fbdev.c:9:
> include/linux/of.h:318:1: error: unknown type name 'device_node'
> --
> In file included from include/asm-generic/gpio.h:7:0,
> from include/linux/gpio.h:48,
> from drivers/gpio/gpiolib.c:10:
> include/linux/of.h:318:1: error: unknown type name 'device_node'
> --
> In file included from include/asm-generic/gpio.h:7:0,
> from include/linux/gpio.h:48,
> from drivers/gpio/devres.c:18:
> include/linux/of.h:318:1: error: unknown type name 'device_node'
> ..
>
> ---
> 0-DAY kernel build testing backend Open Source Technology Centre
> Fengguang Wu <wfg@linux.intel.com> Intel Corporation
>
--
To unsubscribe from this list: send the line "unsubscribe kernel-janitors" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next reply other threads:[~2012-09-06 7:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-06 7:48 Peter Ujfalusi [this message]
2012-09-06 7:55 ` [omap-dss2:work:omap5-dt 83/133] include/linux/of.h:318:1: error: unknown type name 'device_node Tomi Valkeinen
2012-09-06 8:45 ` Fengguang Wu
2012-09-06 8:58 ` Tomi Valkeinen
2012-09-06 9:06 ` Fengguang Wu
2012-09-06 9:24 ` Peter Ujfalusi
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=50485535.6060203@ti.com \
--to=peter.ujfalusi@ti.com \
--cc=kernel-janitors@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 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).