[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.DEB.2.00.0910050138351.9391@asgard.lang.hm>
Date: Mon, 5 Oct 2009 01:45:36 -0700 (PDT)
From: david@...g.hm
To: Jens Axboe <jens.axboe@...cle.com>
cc: Stephen Rothwell <sfr@...b.auug.org.au>,
linux-next@...r.kernel.org, linux-kernel@...r.kernel.org,
Philipp Reisner <philipp.reisner@...bit.com>,
drbd-dev@...bit.com
Subject: Re: linux-next: block/drbd tree build failure
On Mon, 5 Oct 2009, Jens Axboe wrote:
> 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.
what needs to happen to get drbd accepted at this point? It sounded like
they had the tree in good shape to be merged, except for the desire that
was expressed to have them re-work all existing raid implementations
before adding their code (and it sounded like that was not going to be
allowed to hold it up)
David Lang
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists