All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jens Axboe <jens.axboe-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org>
To: david-gFPdbfVZQbY@public.gmane.org
Cc: Stephen Rothwell <sfr-3FnU+UHB4dNDw9hX6IcOSA@public.gmane.org>,
	linux-next-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	drbd-dev-cunTk1MwBs8qoQakbn7OcQ@public.gmane.org,
	linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	Philipp Reisner
	<philipp.reisner-63ez5xqkn6DQT0dZR+AlfA@public.gmane.org>
Subject: Re: linux-next: block/drbd tree build failure
Date: Mon, 5 Oct 2009 10:49:50 +0200	[thread overview]
Message-ID: <20091005084949.GU26573@kernel.dk> (raw)
In-Reply-To: <alpine.DEB.2.00.0910050138351.9391-Z4YwzcCRHZnr5h6Zg1Auow@public.gmane.org>

On Mon, Oct 05 2009, david-gFPdbfVZQbY@public.gmane.org wrote:
> 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)

Linus said he was happy to merge it, but that .32 had slipped now
unfortunately. Usually it's not a problem to merge drivers later than
-rc1, but the discussion surrounding drdb makes it less of a no brainer.

So I expect to merge drbd for .33.

-- 
Jens Axboe

WARNING: multiple messages have this Message-ID (diff)
From: Jens Axboe <jens.axboe@oracle.com>
To: david@lang.hm
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
	linux-next@vger.kernel.org, drbd-dev@lists.linbit.com,
	linux-kernel@vger.kernel.org,
	Philipp Reisner <philipp.reisner@linbit.com>
Subject: Re: [Drbd-dev] linux-next: block/drbd tree build failure
Date: Mon, 5 Oct 2009 10:49:50 +0200	[thread overview]
Message-ID: <20091005084949.GU26573@kernel.dk> (raw)
In-Reply-To: <alpine.DEB.2.00.0910050138351.9391@asgard.lang.hm>

On Mon, Oct 05 2009, david@lang.hm wrote:
> 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)

Linus said he was happy to merge it, but that .32 had slipped now
unfortunately. Usually it's not a problem to merge drivers later than
-rc1, but the discussion surrounding drdb makes it less of a no brainer.

So I expect to merge drbd for .33.

-- 
Jens Axboe


WARNING: multiple messages have this Message-ID (diff)
From: Jens Axboe <jens.axboe@oracle.com>
To: david@lang.hm
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 10:49:50 +0200	[thread overview]
Message-ID: <20091005084949.GU26573@kernel.dk> (raw)
In-Reply-To: <alpine.DEB.2.00.0910050138351.9391@asgard.lang.hm>

On Mon, Oct 05 2009, david@lang.hm wrote:
> 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)

Linus said he was happy to merge it, but that .32 had slipped now
unfortunately. Usually it's not a problem to merge drivers later than
-rc1, but the discussion surrounding drdb makes it less of a no brainer.

So I expect to merge drbd for .33.

-- 
Jens Axboe


  parent reply	other threads:[~2009-10-05  8:49 UTC|newest]

Thread overview: 23+ 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  3:35 ` Stephen Rothwell
2009-10-05  3:35 ` [Drbd-dev] " Stephen Rothwell
     [not found] ` <20091005143552.977a2d4d.sfr-3FnU+UHB4dNDw9hX6IcOSA@public.gmane.org>
2009-10-05  6:31   ` Jens Axboe
2009-10-05  6:31     ` Jens Axboe
2009-10-05  6:31     ` [Drbd-dev] " Jens Axboe
     [not found]     ` <20091005063138.GO26573-tSWWG44O7X1aa/9Udqfwiw@public.gmane.org>
2009-10-05  7:21       ` Stephen Rothwell
2009-10-05  7:21         ` Stephen Rothwell
2009-10-05  7:21         ` [Drbd-dev] " Stephen Rothwell
     [not found]         ` <20091005182103.0a391d15.sfr-3FnU+UHB4dNDw9hX6IcOSA@public.gmane.org>
2009-10-05  7:29           ` Jens Axboe
2009-10-05  7:29             ` Jens Axboe
2009-10-05  7:29             ` [Drbd-dev] " Jens Axboe
     [not found]             ` <20091005072929.GS26573-tSWWG44O7X1aa/9Udqfwiw@public.gmane.org>
2009-10-05  7:53               ` Stephen Rothwell
2009-10-05  7:53                 ` Stephen Rothwell
2009-10-05  7:53                 ` [Drbd-dev] " Stephen Rothwell
     [not found]                 ` <20091005185340.742f6abc.sfr-3FnU+UHB4dNDw9hX6IcOSA@public.gmane.org>
2009-10-05  7:55                   ` Jens Axboe
2009-10-05  7:55                     ` Jens Axboe
2009-10-05  7:55                     ` [Drbd-dev] " Jens Axboe
2009-10-05  8:45     ` david
2009-10-05  8:45       ` [Drbd-dev] " david
     [not found]       ` <alpine.DEB.2.00.0910050138351.9391-Z4YwzcCRHZnr5h6Zg1Auow@public.gmane.org>
2009-10-05  8:49         ` Jens Axboe [this message]
2009-10-05  8:49           ` Jens Axboe
2009-10-05  8:49           ` [Drbd-dev] " 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=20091005084949.GU26573@kernel.dk \
    --to=jens.axboe-qhclzuegtsvqt0dzr+alfa@public.gmane.org \
    --cc=david-gFPdbfVZQbY@public.gmane.org \
    --cc=drbd-dev-cunTk1MwBs8qoQakbn7OcQ@public.gmane.org \
    --cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=linux-next-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=philipp.reisner-63ez5xqkn6DQT0dZR+AlfA@public.gmane.org \
    --cc=sfr-3FnU+UHB4dNDw9hX6IcOSA@public.gmane.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.