From: Fengguang Wu <fengguang.wu@intel.com>
To: kernel-janitors@vger.kernel.org
Subject: [arm-soc:for-next 71/73] drivers/bus/omap_l3_noc.c:31:17: fatal error: soc.h: No such file or direct
Date: Wed, 19 Sep 2012 23:30:46 +0000 [thread overview]
Message-ID: <20120919233046.GB5607@localhost> (raw)
Hi Arnd,
FYI, kernel build failed on
tree: git://git.kernel.org/pub/scm/linux/kernel/git/arm/arm-soc.git for-next
head: 8ebc8820187f3c499a55a0faab82292c3db6df54
commit: cf3e885b8b87587b304e905201a50aee09de187e [71/73] Merge branch 'testing/__iomem' into for-next
config: arm-omap2plus_defconfig
drivers/bus/omap_l3_noc.c:31:17: fatal error: soc.h: No such file or directory
vim +31 drivers/bus/omap_l3_noc.c
21 * USA
22 */
23 #include <linux/module.h>
24 #include <linux/init.h>
25 #include <linux/io.h>
26 #include <linux/platform_device.h>
27 #include <linux/interrupt.h>
28 #include <linux/kernel.h>
29 #include <linux/slab.h>
30
> 31 #include "soc.h"
32 #include "omap_l3_noc.h"
33
34 /*
35 * Interrupt Handler for L3 error detection.
36 * 1) Identify the L3 clockdomain partition to which the error belongs to.
37 * 2) Identify the slave where the error information is logged
38 * 3) Print the logged information.
39 * 4) Add dump stack to provide kernel trace.
40 *
41 * Two Types of errors :
---
0-DAY kernel build testing backend Open Source Technology Centre
Fengguang Wu <wfg@linux.intel.com> Intel Corporation
next reply other threads:[~2012-09-19 23:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-19 23:30 Fengguang Wu [this message]
2012-09-20 12:45 ` [arm-soc:for-next 71/73] drivers/bus/omap_l3_noc.c:31:17: fatal error: soc.h: No such file or di Arnd Bergmann
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=20120919233046.GB5607@localhost \
--to=fengguang.wu@intel.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 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.