search for: 49a2699

Displaying 3 results from an estimated 3 matches for "49a2699".

2016 Aug 17
0
[PATCH 15/15] block: Add FIXME comment to handle device_add_disk error
...ice *_dev) gendisk->disk_name, priv->model, priv->raw_capacity >> 11, get_capacity(gendisk) >> 11); + /* FIXME: handle error. */ device_add_disk(&dev->sbd.core, gendisk, NULL); return 0; diff --git a/drivers/block/ps3vram.c b/drivers/block/ps3vram.c index 49a2699..d82d87a 100644 --- a/drivers/block/ps3vram.c +++ b/drivers/block/ps3vram.c @@ -779,6 +779,7 @@ static int ps3vram_probe(struct ps3_system_bus_device *dev) dev_info(&dev->core, "%s: Using %lu MiB of GPU memory\n", gendisk->disk_name, get_capacity(gendisk) >> 11); +...
2016 Aug 17
20
[PATCH 00/15] Fix issue with KOBJ_ADD uevent versus disk attributes
This is an attempt to fix the issue that some disks' sysfs attributes are not ready at the time its KOBJ_ADD event is sent. The symptom is during device hotplug, udev may fail to find certain attributes, such as serial or wwn, of the disk. As a result the /dev/disk/by-id entries are not created. The cause is device_add_disk emits the uevent before returning, and the callers have to create
2016 Aug 17
20
[PATCH 00/15] Fix issue with KOBJ_ADD uevent versus disk attributes
This is an attempt to fix the issue that some disks' sysfs attributes are not ready at the time its KOBJ_ADD event is sent. The symptom is during device hotplug, udev may fail to find certain attributes, such as serial or wwn, of the disk. As a result the /dev/disk/by-id entries are not created. The cause is device_add_disk emits the uevent before returning, and the callers have to create