public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@lst.de>
To: Dan Williams <dan.j.williams@intel.com>
Cc: Christoph Hellwig <hch@lst.de>, Jens Axboe <axboe@fb.com>,
	linux-block@vger.kernel.org,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Al Viro <viro@zeniv.linux.org.uk>
Subject: Re: [PATCH 1/3] block: introduce device_add_disk()
Date: Thu, 10 Mar 2016 16:18:44 +0100	[thread overview]
Message-ID: <20160310151844.GA8334@lst.de> (raw)
In-Reply-To: <CAPcyv4jrWp4BKuSyxarTMy4eeezLTos6-MZMup5b4enKkE4N1w@mail.gmail.com>

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.

  reply	other threads:[~2016-03-10 15:18 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-25 20:04 [PATCH 0/3] Introduce device_add_disk() to kill gendisk.driverfs_dev Dan Williams
2016-02-25 20:04 ` [PATCH 1/3] block: introduce device_add_disk() Dan Williams
2016-03-10  8:09   ` Christoph Hellwig
2016-03-10 15:15     ` Dan Williams
2016-03-10 15:18       ` Christoph Hellwig [this message]
2016-03-10 15:27         ` Dan Williams
2016-02-25 20:04 ` [PATCH 2/3] block: convert to device_add_disk() Dan Williams
2016-02-25 20:04 ` [PATCH 3/3] block: remove ->driverfs_dev Dan Williams
2016-03-09 17:38 ` [PATCH 0/3] Introduce device_add_disk() to kill gendisk.driverfs_dev Dan Williams

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=20160310151844.GA8334@lst.de \
    --to=hch@lst.de \
    --cc=axboe@fb.com \
    --cc=dan.j.williams@intel.com \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=viro@zeniv.linux.org.uk \
    /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