The patch titled Subject: drivers/of/fdt.c: re-use kernel's kbasename() has been added to the -mm tree. Its filename is drivers-of-fdtc-re-use-kernels-kbasename.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: Andy Shevchenko <andriy.shevchenko@xxxxxxxxxxxxxxx> Subject: drivers/of/fdt.c: re-use kernel's kbasename() Signed-off-by: Andy Shevchenko <andriy.shevchenko@xxxxxxxxxxxxxxx> Acked-by: Grant Likely <grant.likely@xxxxxxxxxxxx> Cc: Rob Herring <rob.herring@xxxxxxxxxxx> Signed-off-by: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx> --- drivers/of/fdt.c | 10 ++-------- 1 file changed, 2 insertions(+), 8 deletions(-) diff -puN drivers/of/fdt.c~drivers-of-fdtc-re-use-kernels-kbasename drivers/of/fdt.c --- a/drivers/of/fdt.c~drivers-of-fdtc-re-use-kernels-kbasename +++ a/drivers/of/fdt.c @@ -486,14 +486,8 @@ int __init of_scan_flat_dt(int (*it)(uns depth++; pathp = (char *)p; p = ALIGN(p + strlen(pathp) + 1, 4); - if ((*pathp) == '/') { - char *lp, *np; - for (lp = NULL, np = pathp; *np; np++) - if ((*np) == '/') - lp = np+1; - if (lp != NULL) - pathp = lp; - } + if (*pathp == '/') + pathp = kbasename(pathp); rc = it(p, pathp, depth, data); if (rc != 0) break; _ Patches currently in -mm which might be from andriy.shevchenko@xxxxxxxxxxxxxxx are linux-next.patch string-introduce-helper-to-get-base-file-name-from-given-path.patch lib-dynamic_debug-use-kbasename.patch mm-use-kbasename.patch procfs-use-kbasename.patch procfs-use-kbasename-fix.patch trace-use-kbasename.patch drivers-of-fdtc-re-use-kernels-kbasename.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