From: Roland Dreier <roland@kernel.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: "linux-rdma@vger.kernel.org" <linux-rdma@vger.kernel.org>,
linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
Mike Marciniszyn <mike.marciniszyn@intel.com>
Subject: Re: linux-next: build failure after merge of the infiniband tree
Date: Tue, 17 Feb 2015 19:01:13 -0800 [thread overview]
Message-ID: <CAL1RGDV7VmjQ6NbrhDHYPPBJH2L-5zkMdA-x-mZFpETc9NxMiA@mail.gmail.com> (raw)
In-Reply-To: <20150218133221.7aa89df7@canb.auug.org.au>
On Tue, Feb 17, 2015 at 6:32 PM, Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> After merging the livepatching tree, today's linux-next build (powerpc
> allyesconfig) failed like this:
>
> In file included from drivers/infiniband/hw/qib/qib_cq.c:41:0:
> drivers/infiniband/hw/qib/qib.h: In function 'qib_flush_wc':
> drivers/infiniband/hw/qib/qib.h:1470:1: error: expected ';' before '}' token
> }
> ^
>
> and it went badly down hill from there :-(
Weird, I could have sworn I fixed that before I pushed the tree out.
Anyway I'll try adding the missing ';' again and push it out again :(
next prev parent reply other threads:[~2015-02-18 3:01 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-18 2:32 linux-next: build failure after merge of the infiniband tree Stephen Rothwell
2015-02-18 3:01 ` Roland Dreier [this message]
-- strict thread matches above, loose matches on Subject: below --
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
2012-12-19 22:44 Stephen Rothwell
2012-12-20 0:22 ` Roland Dreier
2012-12-20 9:58 ` Vipul Pandya
2012-08-16 1:44 Stephen Rothwell
2012-08-16 4:07 ` Roland Dreier
2012-08-16 6:59 ` Stephen Rothwell
2012-07-06 2:35 Stephen Rothwell
2012-07-06 3:58 ` Roland Dreier
2012-07-06 6:31 ` Hefty, Sean
2012-05-21 2:05 Stephen Rothwell
2012-05-21 14:04 ` Vipul Pandya
2012-05-21 16:03 ` Roland Dreier
2011-10-11 3:49 Stephen Rothwell
2010-07-09 1:04 Stephen Rothwell
2010-07-09 3:05 ` Ben Hutchings
2010-07-09 3:46 ` Roland Dreier
2010-07-09 6:16 ` 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=CAL1RGDV7VmjQ6NbrhDHYPPBJH2L-5zkMdA-x-mZFpETc9NxMiA@mail.gmail.com \
--to=roland@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=mike.marciniszyn@intel.com \
--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).