All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arnd Bergmann <arnd@arndb.de>
To: kernel-janitors@vger.kernel.org
Subject: Re: [arm-soc:for-next 71/73] drivers/bus/omap_l3_noc.c:31:17: fatal error: soc.h: No such file or di
Date: Thu, 20 Sep 2012 12:45:39 +0000	[thread overview]
Message-ID: <201209201245.39433.arnd@arndb.de> (raw)
In-Reply-To: <20120919233046.GB5607@localhost>

On Wednesday 19 September 2012, Fengguang Wu wrote:
> 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
> 

Thanks a lot for the report, I already found the same problem myself
but didn't have the time to fix it up yesterday. Same for the other
one on omap2plus_defconfig.

	Arnd

      reply	other threads:[~2012-09-20 12:45 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-19 23:30 [arm-soc:for-next 71/73] drivers/bus/omap_l3_noc.c:31:17: fatal error: soc.h: No such file or direct Fengguang Wu
2012-09-20 12:45 ` Arnd Bergmann [this message]

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=201209201245.39433.arnd@arndb.de \
    --to=arnd@arndb.de \
    --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.