From: Jens Axboe <jens.axboe@oracle.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
Philipp Reisner <philipp.reisner@linbit.com>,
drbd-dev@linbit.com
Subject: Re: linux-next: block/drbd tree build failure
Date: Mon, 5 Oct 2009 08:31:38 +0200 [thread overview]
Message-ID: <20091005063138.GO26573@kernel.dk> (raw)
In-Reply-To: <20091005143552.977a2d4d.sfr@canb.auug.org.au>
On Mon, Oct 05 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: subscripted value is neither array nor pointer
> drivers/block/drbd/drbd_req.c: In function '_drbd_end_io_acct':
> drivers/block/drbd/drbd_req.c:56: error: subscripted value is neither array nor pointer
>
> I reported a similar error against the dbd tree, which was fixed, but now
> the commit that caused that error has been reverted and thus we get
> this :-(
>
> I have reverted the drbd commits from the block tree for today.
That's probably my fault, not drbd. I moved it to a new branch since it
isn't going into 2.6.32, and perhaps dropped that fix along the way.
I'll look into it.
--
Jens Axboe
next prev parent reply other threads:[~2009-10-05 6:32 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-05 3:35 linux-next: block/drbd tree build failure Stephen Rothwell
2009-10-05 6:31 ` Jens Axboe [this message]
2009-10-05 7:21 ` Stephen Rothwell
2009-10-05 7:29 ` Jens Axboe
2009-10-05 7:53 ` Stephen Rothwell
2009-10-05 7:55 ` Jens Axboe
2009-10-05 8:45 ` david
2009-10-05 8:49 ` Jens Axboe
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=20091005063138.GO26573@kernel.dk \
--to=jens.axboe@oracle.com \
--cc=drbd-dev@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