From: Roland Dreier <rdreier@cisco.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: general@lists.openfabrics.org, linux-next@vger.kernel.org
Subject: Re: [ofa-general] linux-next: infiniband tree build failure
Date: Thu, 07 May 2009 21:36:55 -0700 [thread overview]
Message-ID: <adatz3wqkgo.fsf@cisco.com> (raw)
In-Reply-To: <20090508115356.b97b8981.sfr@canb.auug.org.au> (Stephen Rothwell's message of "Fri, 8 May 2009 11:53:56 +1000")
> Today's linux-next build (x86_64 allmodconfig) failed like this:
>
> drivers/infiniband/hw/mlx4/mr.c: In function 'mlx4_ib_alloc_fast_reg_page_list':
> drivers/infiniband/hw/mlx4/mr.c:242: error: label 'err_free_mfrpl' used but not defined
>
> Caused by commit 88029ff3c862812b81745ae3d6557ede96e2d051 ("IB/mlx4:
> Don't overwrite fast registration page list when posting work request").
> Clearly not build tested :-(
My fault for editing after applying the patch. Fixed now.
Thanks,
Roland
prev parent reply other threads:[~2009-05-08 4:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-08 1:53 linux-next: infiniband tree build failure Stephen Rothwell
2009-05-08 4:36 ` Roland Dreier [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=adatz3wqkgo.fsf@cisco.com \
--to=rdreier@cisco.com \
--cc=general@lists.openfabrics.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;
as well as URLs for NNTP newsgroup(s).