From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Roland Dreier <rdreier@cisco.com>
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: Fri, 9 Jul 2010 16:16:24 +1000 [thread overview]
Message-ID: <20100709161624.b27e8d7a.sfr@canb.auug.org.au> (raw)
In-Reply-To: <ada4og9z5a1.fsf@roland-alpha.cisco.com>
[-- Attachment #1: Type: text/plain, Size: 455 bytes --]
Hi Roland,
On Thu, 08 Jul 2010 20:46:14 -0700 Roland Dreier <rdreier@cisco.com> wrote:
>
> 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.
Thanks, I will pick it up on Monday.
--
Cheers,
Stephen Rothwell sfr@canb.auug.org.au
http://www.canb.auug.org.au/~sfr/
[-- Attachment #2: Type: application/pgp-signature, Size: 490 bytes --]
next prev parent reply other threads:[~2010-07-09 6:16 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
2010-07-09 6:16 ` Stephen Rothwell [this message]
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=20100709161624.b27e8d7a.sfr@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=ben@decadent.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=rdreier@cisco.com \
/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).