From: Dan Williams <dan.j.williams@intel.com>
To: axboe@fb.com
Cc: Keith Busch <keith.busch@intel.com>,
Ulf Hansson <ulf.hansson@linaro.org>,
"Martin K. Petersen" <martin.petersen@oracle.com>,
"Michael S. Tsirkin" <mst@redhat.com>,
Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>,
linux-kernel@vger.kernel.org, hch@lst.de,
James Bottomley <James.Bottomley@hansenpartnership.com>,
linux-block@vger.kernel.org,
Ross Zwisler <ross.zwisler@linux.intel.com>,
David Woodhouse <dwmw2@infradead.org>,
"David S. Miller" <davem@davemloft.net>
Subject: [PATCH v2 0/3] Introduce device_add_disk() to kill gendisk.driverfs_dev
Date: Fri, 11 Mar 2016 07:47:27 -0800 [thread overview]
Message-ID: <20160311154727.24401.87967.stgit@dwillia2-desk3.jf.intel.com> (raw)
Changes since v1: [1]
1/ Rebase on -next
2/ Drop the error return from device_add_disk() to keep the same error
semantics as add_disk() for now. (Christoph).
[1]: https://lkml.org/lkml/2016/2/25/664
---
Answer the "// FIXME: remove" include/linux/genhd.h. This should be
functionally equivalent to the previous state. These patches received a
build success notification from the kbuild robot across 43 configs.
---
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 | 18 +++++++++---------
drivers/block/cciss.c | 3 +--
drivers/block/floppy.c | 3 +--
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, 46 insertions(+), 72 deletions(-)
next reply other threads:[~2016-03-11 15:47 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-11 15:47 Dan Williams [this message]
2016-03-11 15:47 ` [PATCH v2 1/3] block: introduce device_add_disk() Dan Williams
2016-03-14 8:14 ` Johannes Thumshirn
2016-03-11 15:47 ` [PATCH v2 2/3] block: convert to device_add_disk() Dan Williams
2016-03-14 8:15 ` Johannes Thumshirn
2016-03-11 15:47 ` [PATCH v2 3/3] block: remove ->driverfs_dev Dan Williams
2016-03-14 8:15 ` Johannes Thumshirn
2016-03-11 16:35 ` [PATCH v2 0/3] Introduce device_add_disk() to kill gendisk.driverfs_dev Christoph Hellwig
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=20160311154727.24401.87967.stgit@dwillia2-desk3.jf.intel.com \
--to=dan.j.williams@intel.com \
--cc=James.Bottomley@hansenpartnership.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
all inboxes | Powered by JetHome®