From: Alex Elder <elder@dreamhost.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Sage Weil <sage@newdream.net>,
linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
Josh Durgin <josh.durgin@dreamhost.com>
Subject: Re: linux-next: build failure after merge of the ceph tree
Date: Tue, 20 Mar 2012 23:24:11 -0500 [thread overview]
Message-ID: <4F6957EB.5030309@dreamhost.com> (raw)
In-Reply-To: <20120321124007.e879c834619c7bb9298d5694@canb.auug.org.au>
On 03/20/2012 08:40 PM, Stephen Rothwell wrote:
> Hi Sage,
>
> After merging the ceph tree, today's linux-next build (x86_64
> allmodconfig) failed like this:
>
> drivers/block/rbd.c: In function 'rbd_add':
> drivers/block/rbd.c:2384:2: error: 'struct rbd_image_header' has no member named 'snap_rwsem'
>
> Caused by commit dd2a081fb58f ("rbd: move snap_rwsem to the device,
> rename to header_rwsem") interacting with commit 0e805a1d8577 ("rbd:
> initialize snap_rwsem in rbd_add()") from Linus' tree.
>
> I used the ceph tree from next-20120320 for today.
I'll take a look at this tomorrow. I'm sorry my earlier
suggestion didn't address this.
-Alex
next prev parent reply other threads:[~2012-03-21 4:24 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-21 1:40 linux-next: build failure after merge of the ceph tree Stephen Rothwell
2012-03-21 4:24 ` Alex Elder [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-12-14 23:46 Stephen Rothwell
2013-09-27 1:31 Stephen Rothwell
2013-09-27 2:36 ` Dave Kleikamp
2013-09-26 1:15 Stephen Rothwell
2013-09-26 1:20 ` majianpeng
2013-09-26 1:26 ` Sage Weil
2010-11-16 23:43 Stephen Rothwell
2010-11-17 0:02 ` Sage Weil
2010-09-20 1:41 Stephen Rothwell
2010-09-20 2:53 ` Sage Weil
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=4F6957EB.5030309@dreamhost.com \
--to=elder@dreamhost.com \
--cc=josh.durgin@dreamhost.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sage@newdream.net \
--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