search for: 4f49a97

Displaying 3 results from an estimated 3 matches for "4f49a97".

2016 Aug 17
0
[PATCH 15/15] block: Add FIXME comment to handle device_add_disk error
...h(struct macio_dev *mdev, disk->flags |= GENHD_FL_REMOVABLE; sprintf(disk->disk_name, "fd%d", index); set_capacity(disk, 2880); + /* FIXME: handle error. */ device_add_disk(NULL, disk, NULL); return 0; diff --git a/drivers/block/sx8.c b/drivers/block/sx8.c index 507dea8..4f49a97 100644 --- a/drivers/block/sx8.c +++ b/drivers/block/sx8.c @@ -1333,6 +1333,7 @@ static void carm_fsm_task (struct work_struct *work) struct gendisk *disk = port->disk; set_capacity(disk, port->capacity); + /* FIXME: handle error. */ device_add_disk(NULL, disk, NULL);...
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