From: Dan Williams <dan.j.williams@intel.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
Jassi Brar <jassi.brar@samsung.com>
Subject: Re: linux-next: build failure after merge of the async_tx tree
Date: Sun, 23 May 2010 20:42:38 -0700 [thread overview]
Message-ID: <AANLkTilefCp0WI-gFvuuXM6qrCO98I3GPJdN0UO6hfLI@mail.gmail.com> (raw)
In-Reply-To: <20100524112405.3c62d22b.sfr@canb.auug.org.au>
On Sun, May 23, 2010 at 6:24 PM, Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> Hi Dan,
>
> After merging the async_tx tree, today's linux-next build (x86_64
> allmodconfig) failed like this:
>
> In file included from drivers/dma/pl330.c:19:
> include/linux/amba/pl330.h:15:32: error: asm/hardware/pl330.h: No such file or directory
Should have caught that in the review... changed the 'select PL330' to
a 'depends on PL300' and pushed it back out.
Thanks,
Dan
next prev parent reply other threads:[~2010-05-24 3:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-24 1:24 Stephen Rothwell
2010-05-24 1:59 ` Jassi Brar
2010-05-24 3:56 ` Stephen Rothwell
2010-05-24 3:42 ` Dan Williams [this message]
2010-05-24 3:55 ` Stephen Rothwell
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=AANLkTilefCp0WI-gFvuuXM6qrCO98I3GPJdN0UO6hfLI@mail.gmail.com \
--to=dan.j.williams@intel.com \
--cc=jassi.brar@samsung.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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
all inboxes | Powered by JetHome®