The patch titled scsi: a4000: correct driver unregistration in case of failure has been removed from the -mm tree. Its filename was scsi-a4000-correct-driver-unregistration-in-case-of-failure.patch This patch was dropped because it was merged into mainline or a subsystem tree The current -mm tree may be found at http://userweb.kernel.org/~akpm/mmotm/ ------------------------------------------------------ Subject: scsi: a4000: correct driver unregistration in case of failure From: Geert Uytterhoeven <geert@xxxxxxxxxxxxxx> commit 7a192ec334cab9fafe3a8665a65af398b0e24730 ("platform driver: fix incorrect use of 'platform_bus_type' with 'struct device_driver') turned a driver_UNregister into platform_driver_REGISTER. Correct this to platform_driver_UNregister. Signed-off-by: Geert Uytterhoeven <geert@xxxxxxxxxxxxxx> Cc: Ming Lei <tom.leiming@xxxxxxxxx> Cc: Greg Kroah-Hartman <gregkh@xxxxxxx> Cc: "James E.J. Bottomley" <James.Bottomley@xxxxxxxxxxxxxxxxxxxxx> Signed-off-by: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx> --- drivers/scsi/a4000t.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff -puN drivers/scsi/a4000t.c~scsi-a4000-correct-driver-unregistration-in-case-of-failure drivers/scsi/a4000t.c --- a/drivers/scsi/a4000t.c~scsi-a4000-correct-driver-unregistration-in-case-of-failure +++ a/drivers/scsi/a4000t.c @@ -129,7 +129,7 @@ static int __init a4000t_scsi_init(void) a4000t_scsi_device = platform_device_register_simple("a4000t-scsi", -1, NULL, 0); if (IS_ERR(a4000t_scsi_device)) { - platform_driver_register(&a4000t_scsi_driver); + platform_driver_unregister(&a4000t_scsi_driver); return PTR_ERR(a4000t_scsi_device); } _ Patches currently in -mm which might be from geert@xxxxxxxxxxxxxx are linux-next.patch time-create-arch_gettimeoffset-infrastructure-for-use-in-the-generic-timekeeping-core.patch m68k-count-can-reach-51-not-50.patch kmap_types-make-most-arches-use-generic-header-file.patch flat-fix-data-sections-alignment.patch -- To unsubscribe from this list: send the line "unsubscribe mm-commits" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html