From: Dan Williams <dan.j.williams@intel.com>
To: axboe@fb.com
Cc: linux-block@vger.kernel.org, Ulf Hansson <ulf.hansson@linaro.org>,
"Martin K. Petersen" <martin.petersen@oracle.com>,
Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>,
"James E.J. Bottomley" <JBottomley@odin.com>,
linux-kernel@vger.kernel.org,
"David S. Miller" <davem@davemloft.net>,
Keith Busch <keith.busch@intel.com>,
"Michael S. Tsirkin" <mst@redhat.com>,
Ross Zwisler <ross.zwisler@linux.intel.com>,
David Woodhouse <dwmw2@infradead.org>,
hch@lst.de
Subject: [PATCH 0/3] Introduce device_add_disk() to kill gendisk.driverfs_dev
Date: Thu, 25 Feb 2016 12:04:38 -0800 [thread overview]
Message-ID: <20160225200018.21975.30922.stgit@dwillia2-desk3.amr.corp.intel.com> (raw)
Answer the "// FIXME: remove" include/linux/genhd.h. This should be
functionally equivalent to the previous state. Now that the WARN_ON()
for the registration failure case is up-levelled to some drivers, they
can take on the follow on work to handle device_add_disk() failures.
Note, a full run from the kbuild robot is still pending. I'll post v2
if it reports anything against this set on top of current -next.
---
Dan Williams (3):
block: introduce device_add_disk()
block: convert to device_add_disk()
block: remove ->driverfs_dev
arch/powerpc/sysdev/axonram.c | 3 +--
arch/um/drivers/ubd_kern.c | 3 +--
block/genhd.c | 27 ++++++++++++---------------
drivers/block/cciss.c | 3 +--
drivers/block/floppy.c | 4 ++--
drivers/block/mtip32xx/mtip32xx.c | 5 ++---
drivers/block/ps3disk.c | 3 +--
drivers/block/ps3vram.c | 3 +--
drivers/block/rsxx/dev.c | 4 +---
drivers/block/skd_main.c | 8 +++-----
drivers/block/sunvdc.c | 3 +--
drivers/block/virtio_blk.c | 3 +--
drivers/block/xen-blkfront.c | 3 +--
drivers/ide/ide-cd.c | 3 +--
drivers/ide/ide-gd.c | 3 +--
drivers/memstick/core/ms_block.c | 3 +--
drivers/memstick/core/mspro_block.c | 3 +--
drivers/mmc/card/block.c | 3 +--
drivers/mtd/mtd_blkdevs.c | 4 +---
drivers/nvdimm/blk.c | 3 +--
drivers/nvdimm/btt.c | 3 +--
drivers/nvdimm/bus.c | 2 +-
drivers/nvdimm/pmem.c | 3 +--
drivers/nvme/host/core.c | 3 +--
drivers/s390/block/dasd_genhd.c | 3 +--
drivers/s390/block/dcssblk.c | 3 +--
drivers/s390/block/scm_blk.c | 3 +--
drivers/scsi/sd.c | 3 +--
drivers/scsi/sr.c | 3 +--
include/linux/genhd.h | 8 ++++++--
30 files changed, 50 insertions(+), 78 deletions(-)
next reply other threads:[~2016-02-25 20:06 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-25 20:04 Dan Williams [this message]
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
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=20160225200018.21975.30922.stgit@dwillia2-desk3.amr.corp.intel.com \
--to=dan.j.williams@intel.com \
--cc=JBottomley@odin.com \
--cc=axboe@fb.com \
--cc=davem@davemloft.net \
--cc=dwmw2@infradead.org \
--cc=hch@lst.de \
--cc=keith.busch@intel.com \
--cc=konrad.wilk@oracle.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=mst@redhat.com \
--cc=ross.zwisler@linux.intel.com \
--cc=ulf.hansson@linaro.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).