Commit 95c09f03 authored by Julian Wiedmann's avatar Julian Wiedmann Committed by Vasily Gorbik
Browse files

s390/ap: wire up bus->probe and bus->remove 



Hijacking the device_driver's probe/remove callbacks for purely
bus-internal logic is a very unconvential construct. Instead just set
up our callbacks in the AP bus struct, and really_probe() will call them
in the same way as before.

Signed-off-by: default avatarJulian Wiedmann <jwi@linux.ibm.com>
Reviewed-by: default avatarHarald Freudenberger <freude@linux.ibm.com>
Signed-off-by: default avatarVasily Gorbik <gor@linux.ibm.com>
parent 3b4dd968

drivers/s390/crypto/ap_bus.c

+2 −2
Original line number Diff line number Diff line
@@ -885,8 +885,6 @@ int ap_driver_register(struct ap_driver *ap_drv, struct module *owner, 
	struct device_driver *drv = &ap_drv->driver;



	drv->bus = &ap_bus_type;

	drv->probe = ap_device_probe;

	drv->remove = ap_device_remove;

	drv->owner = owner;

	drv->name = name;

	return driver_register(drv);
@@ -1319,6 +1317,8 @@ static struct bus_type ap_bus_type = { 
	.bus_groups = ap_bus_groups,

	.match = &ap_bus_match,

	.uevent = &ap_uevent,

	.probe = ap_device_probe,

	.remove = ap_device_remove,

};



/**