From: Roland Dreier <rdreier@cisco.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-rdma@vger.kernel.org, linux-next@vger.kernel.org,
linux-kernel@vger.kernel.org, Ben Hutchings <ben@decadent.org.uk>
Subject: Re: linux-next: build failure after merge of the infiniband tree
Date: Thu, 08 Jul 2010 20:46:14 -0700 [thread overview]
Message-ID: <ada4og9z5a1.fsf@roland-alpha.cisco.com> (raw)
In-Reply-To: <20100709110427.c05987cc.sfr@canb.auug.org.au> (Stephen Rothwell's message of "Fri, 9 Jul 2010 11:04:27 +1000")
> After merging the infiniband tree, today's linux-next build (x86_64
> allmodconfig) failed like this:
>
> make[2]: *** No rule to make target `firmware/qlogic/sd7220.fw', needed by `__fw_modbuild'. Stop.
Sorry, I took the version of the patch that Ralph sent me, instead of
Ben's original patch, and that version dropped the most important part,
namely the actual firmware file.
Should be fixed now.
--
Roland Dreier <rolandd@cisco.com> || For corporate legal information go to:
http://www.cisco.com/web/about/doing_business/legal/cri/index.html
next prev parent reply other threads:[~2010-07-09 3:47 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-09 1:04 linux-next: build failure after merge of the infiniband tree Stephen Rothwell
2010-07-09 3:05 ` Ben Hutchings
2010-07-09 3:46 ` Roland Dreier [this message]
2010-07-09 6:16 ` Stephen Rothwell
2011-10-11 3:49 Stephen Rothwell
2012-05-21 2:05 Stephen Rothwell
2012-05-21 14:04 ` Vipul Pandya
2012-05-21 16:03 ` Roland Dreier
2012-07-06 2:35 Stephen Rothwell
2012-07-06 3:58 ` Roland Dreier
2012-07-06 6:31 ` Hefty, Sean
2012-08-16 1:44 Stephen Rothwell
2012-08-16 4:07 ` Roland Dreier
2012-08-16 6:59 ` Stephen Rothwell
2012-12-19 22:44 Stephen Rothwell
2012-12-20 0:22 ` Roland Dreier
2012-12-20 9:58 ` Vipul Pandya
2014-12-16 1:47 Stephen Rothwell
2014-12-16 1:56 ` Roland Dreier
2014-12-16 2:22 ` Roland Dreier
2014-12-16 10:57 ` Or Gerlitz
2015-02-18 2:32 Stephen Rothwell
2015-02-18 3:01 ` Roland Dreier
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=ada4og9z5a1.fsf@roland-alpha.cisco.com \
--to=rdreier@cisco.com \
--cc=ben@decadent.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux-rdma@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;
as well as URLs for NNTP newsgroup(s).