From: david@lang•hm
To: Jens Axboe <jens.axboe@oracle•com>
Cc: Stephen Rothwell <sfr@canb•auug.org.au>,
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 01:45:36 -0700 (PDT) [thread overview]
Message-ID: <alpine.DEB.2.00.0910050138351.9391@asgard.lang.hm> (raw)
In-Reply-To: <20091005063138.GO26573@kernel.dk>
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
next prev parent reply other threads:[~2009-10-05 8:45 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
[not found] ` <20091005143552.977a2d4d.sfr-3FnU+UHB4dNDw9hX6IcOSA@public.gmane.org>
2009-10-05 6:31 ` Jens Axboe
[not found] ` <20091005063138.GO26573-tSWWG44O7X1aa/9Udqfwiw@public.gmane.org>
2009-10-05 7:21 ` Stephen Rothwell
[not found] ` <20091005182103.0a391d15.sfr-3FnU+UHB4dNDw9hX6IcOSA@public.gmane.org>
2009-10-05 7:29 ` Jens Axboe
[not found] ` <20091005072929.GS26573-tSWWG44O7X1aa/9Udqfwiw@public.gmane.org>
2009-10-05 7:53 ` Stephen Rothwell
[not found] ` <20091005185340.742f6abc.sfr-3FnU+UHB4dNDw9hX6IcOSA@public.gmane.org>
2009-10-05 7:55 ` Jens Axboe
2009-10-05 8:45 ` david [this message]
[not found] ` <alpine.DEB.2.00.0910050138351.9391-Z4YwzcCRHZnr5h6Zg1Auow@public.gmane.org>
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=alpine.DEB.2.00.0910050138351.9391@asgard.lang.hm \
--to=david@lang$(echo .)hm \
--cc=drbd-dev@linbit$(echo .)com \
--cc=jens.axboe@oracle$(echo .)com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=philipp.reisner@linbit$(echo .)com \
--cc=sfr@canb$(echo .)auug.org.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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