public inbox for linux-next@vger.kernel.org 
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Roland Dreier <rdreier@cisco•com>, general@lists•openfabrics.org
Cc: linux-next@vger•kernel.org, Jack Morgenstein <jackm@dev•mellanox.co.il>
Subject: linux-next: infiniband tree build failure
Date: Fri, 8 May 2009 11:53:56 +1000	[thread overview]
Message-ID: <20090508115356.b97b8981.sfr@canb.auug.org.au> (raw)

[-- Attachment #1: Type: text/plain, Size: 595 bytes --]

Hi Roland,

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 :-(

I have used the version of the tree from next-20090507.
-- 
Cheers,
Stephen Rothwell                    sfr@canb•auug.org.au
http://www.canb.auug.org.au/~sfr/

[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]

             reply	other threads:[~2009-05-08  1:54 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-08  1:53 Stephen Rothwell [this message]
2009-05-08  4:36 ` [ofa-general] linux-next: infiniband tree build failure Roland Dreier
  -- strict thread matches above, loose matches on Subject: below --
2009-11-20  0:03 Stephen Rothwell
2009-11-20  0:19 ` Roland Dreier
2009-11-20  0:30   ` Sean Hefty
2009-11-20  0:43     ` Roland Dreier
2009-11-20  0:45     ` Roland Dreier
2009-11-20  0:52       ` Sean Hefty
2009-11-20  0:34   ` Stephen Rothwell
2009-04-29  4:01 Stephen Rothwell
2009-04-29 16:51 ` 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=20090508115356.b97b8981.sfr@canb.auug.org.au \
    --to=sfr@canb$(echo .)auug.org.au \
    --cc=general@lists$(echo .)openfabrics.org \
    --cc=jackm@dev$(echo .)mellanox.co.il \
    --cc=linux-next@vger$(echo .)kernel.org \
    --cc=rdreier@cisco$(echo .)com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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