[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CAPcyv4hBoONhZHpaA-sjo=Lbo+x6=VvScWXv7YKu6TeFvqT-jA@mail.gmail.com>
Date: Thu, 10 Mar 2016 07:27:23 -0800
From: Dan Williams <dan.j.williams@...el.com>
To: Christoph Hellwig <hch@....de>
Cc: Jens Axboe <axboe@...com>, linux-block@...r.kernel.org,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Al Viro <viro@...iv.linux.org.uk>
Subject: Re: [PATCH 1/3] block: introduce device_add_disk()
On Thu, Mar 10, 2016 at 7:18 AM, Christoph Hellwig <hch@....de> wrote:
> On Thu, Mar 10, 2016 at 07:15:19AM -0800, Dan Williams wrote:
>> > How are the callers expected to unwind after already having added the
>> > disk?
>>
>> True, I overlooked making add_disk() unwind-able, will re-spin...
>
> I think this will take more work than we can finish in the next
> days. It would be good to simply respin it without adding the error
> propagation.
Sounds good.
Powered by blists - more mailing lists