review.tizen.org Git - platform/adaptation/renesas_rcar/renesas

projects / platform / adaptation / renesas_rcar / renesas_kernel.git / commit

author	Stefan Weinhuber <wein@de.ibm.com>
	Wed, 5 Jan 2011 11:48:03 +0000 (12:48 +0100)
committer	Martin Schwidefsky <sky@mschwide.boeblingen.de.ibm.com>
	Wed, 5 Jan 2011 11:47:30 +0000 (12:47 +0100)
commit	a4d26c6aeceea330ee5e0fb6b017d57e3b252d29
tree	eed358de48ff28e4fba73d9925abafa2699a7b6c	tree \| snapshot
parent	ef19298b406f93af4bb249f0776deb8366e97532	commit \| diff

[S390] dasd: do path verification for paths added at runtime

When a new path is added at runtime, the CIO layer will call the drivers
path_event callback. The DASD device driver uses this callback to trigger
a path verification for the new path. The driver will use only those
paths for I/O, which have been successfully verified.

Signed-off-by: Stefan Weinhuber <wein@de.ibm.com>
Signed-off-by: Martin Schwidefsky <schwidefsky@de.ibm.com>

Domain: System / Uncategorized;

RSS Atom

drivers/s390/block/dasd.c		diff \| blob \| history
drivers/s390/block/dasd_3990_erp.c		diff \| blob \| history
drivers/s390/block/dasd_devmap.c		diff \| blob \| history
drivers/s390/block/dasd_diag.c		diff \| blob \| history
drivers/s390/block/dasd_eckd.c		diff \| blob \| history
drivers/s390/block/dasd_eckd.h		diff \| blob \| history
drivers/s390/block/dasd_erp.c		diff \| blob \| history
drivers/s390/block/dasd_fba.c		diff \| blob \| history
drivers/s390/block/dasd_int.h		diff \| blob \| history