[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAA9_cmfuFyFp4X+5zC86LJfSa-0AUVkUO+MJFvXBtvGxCEedfw@mail.gmail.com>
Date: Wed, 9 Mar 2016 09:38:12 -0800
From: Dan Williams <dan.j.williams@...el.com>
To: Jens Axboe <axboe@...com>
Cc: linux-block@...r.kernel.org, Ulf Hansson <ulf.hansson@...aro.org>,
"Martin K. Petersen" <martin.petersen@...cle.com>,
Konrad Rzeszutek Wilk <konrad.wilk@...cle.com>,
"James E.J. Bottomley" <JBottomley@...n.com>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
"David S. Miller" <davem@...emloft.net>,
Keith Busch <keith.busch@...el.com>,
"Michael S. Tsirkin" <mst@...hat.com>,
Ross Zwisler <ross.zwisler@...ux.intel.com>,
David Woodhouse <dwmw2@...radead.org>,
Christoph Hellwig <hch@....de>
Subject: Re: [PATCH 0/3] Introduce device_add_disk() to kill gendisk.driverfs_dev
On Thu, Feb 25, 2016 at 12:04 PM, Dan Williams <dan.j.williams@...el.com> wrote:
> 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
>
Yes, no, maybe so for 4.6?
Powered by blists - more mailing lists