From: Jens Axboe <jens.axboe@oracle.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org, drbd-dev@lists.linbit.com,
linux-kernel@vger.kernel.org, Alasdair G Kergon <agk@redhat.com>,
Philipp Reisner <philipp.reisner@linbit.com>
Subject: Re: [Drbd-dev] linux-next: block tree build failure
Date: Wed, 7 Oct 2009 08:33:54 +0200 [thread overview]
Message-ID: <20091007063354.GG5216@kernel.dk> (raw)
In-Reply-To: <20091007135505.df1f058c.sfr@canb.auug.org.au>
On Wed, Oct 07 2009, Stephen Rothwell wrote:
> Hi Jens,
>
> Today's linux-next build (x86_64 allmodconfig) failed like this:
>
> drivers/block/drbd/drbd_req.c: In function '_drbd_start_io_acct':
> drivers/block/drbd/drbd_req.c:43: error: lvalue required as increment operand
> drivers/block/drbd/drbd_req.c: In function '_drbd_end_io_acct':
> drivers/block/drbd/drbd_req.c:56: error: lvalue required as decrement operand
>
> This is back again :-(
>
> I have used the block tree from next-20091006 for today. I also had to
> use the device-mapper tree from next-20091006 since that is based on the
> block tree.
Irk darn, I fixed this up. Sorry about that, Stephen. It was due to the
in_flight counter being reverted for -rc3 and now back functional in my
upstream branch.
--
Jens Axboe
next prev parent reply other threads:[~2009-10-07 6:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-07 2:55 [Drbd-dev] linux-next: block tree build failure Stephen Rothwell
2009-10-07 6:33 ` Jens Axboe [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-09-23 4:51 Stephen Rothwell
2009-09-23 7:11 ` Lars Ellenberg
2009-09-23 7:32 ` Stephen Rothwell
2009-09-23 11:12 ` Lars Ellenberg
2009-09-23 11:56 ` 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=20091007063354.GG5216@kernel.dk \
--to=jens.axboe@oracle.com \
--cc=agk@redhat.com \
--cc=drbd-dev@lists.linbit.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=philipp.reisner@linbit.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