The patch titled Subject: pps: return PTR_ERR on error in device_create has been added to the -mm tree. Its filename is pps-return-ptr_err-on-error-in-device_create.patch Before you just go and hit "reply", please: a) Consider who else should be cc'ed b) Prefer to cc a suitable mailing list as well c) Ideally: find the original patch on the mailing list and do a reply-to-all to that, adding suitable additional cc's *** Remember to use Documentation/SubmitChecklist when testing your code *** The -mm tree is included into linux-next and is updated there every 3-4 working days ------------------------------------------------------ From: Emil Goode <emilgoode@xxxxxxxxx> Subject: pps: return PTR_ERR on error in device_create We should return PTR_ERR if the call to the device_create function fails. Without this patch we instead return the value from a successful call to cdev_add if the call to device_create fails. Signed-off-by: Emil Goode <emilgoode@xxxxxxxxx> Acked-By: Devendra Naga <devendra.aaru@xxxxxxxxx> Cc: Alexander Gordeev <lasaine@xxxxxxxxxxxxx> Cc: Rodolfo Giometti <giometti@xxxxxxxxxxxx> Signed-off-by: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx> --- drivers/pps/pps.c | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff -puN drivers/pps/pps.c~pps-return-ptr_err-on-error-in-device_create drivers/pps/pps.c --- a/drivers/pps/pps.c~pps-return-ptr_err-on-error-in-device_create +++ a/drivers/pps/pps.c @@ -327,8 +327,10 @@ int pps_register_cdev(struct pps_device } pps->dev = device_create(pps_class, pps->info.dev, devt, pps, "pps%d", pps->id); - if (IS_ERR(pps->dev)) + if (IS_ERR(pps->dev)) { + err = PTR_ERR(pps->dev); goto del_cdev; + } pps->dev->release = pps_device_destruct; _ Subject: Subject: pps: return PTR_ERR on error in device_create Patches currently in -mm which might be from emilgoode@xxxxxxxxx are linux-next.patch pps-return-ptr_err-on-error-in-device_create.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