The patch titled uio-howto.tmpl: use unique output names has been added to the -mm tree. Its filename is uio-howtotmpl-use-unique-output-names.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 *** See http://www.zip.com.au/~akpm/linux/patches/stuff/added-to-mm.txt to find out what to do about this The current -mm tree may be found at http://userweb.kernel.org/~akpm/mmotm/ ------------------------------------------------------ Subject: uio-howto.tmpl: use unique output names From: Mike Frysinger <vapier@xxxxxxxxxx> The Userspace I/O HOWTO template sets two different sections with the same html output name (about.html). This clearly won't work, so change the first one to a unique "aboutthis.html" to prevent clobbering. Signed-off-by: Mike Frysinger <vapier@xxxxxxxxxx> Acked-by: Hans J. Koch <hjk@xxxxxxxxxxxxx> Cc: Greg KH <greg@xxxxxxxxx> Cc: Randy Dunlap <randy.dunlap@xxxxxxxxxx> Signed-off-by: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx> --- Documentation/DocBook/uio-howto.tmpl | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff -puN Documentation/DocBook/uio-howto.tmpl~uio-howtotmpl-use-unique-output-names Documentation/DocBook/uio-howto.tmpl --- a/Documentation/DocBook/uio-howto.tmpl~uio-howtotmpl-use-unique-output-names +++ a/Documentation/DocBook/uio-howto.tmpl @@ -75,7 +75,7 @@ GPL version 2. </bookinfo> <chapter id="aboutthisdoc"> -<?dbhtml filename="about.html"?> +<?dbhtml filename="aboutthis.html"?> <title>About this document</title> <sect1 id="translations"> _ Patches currently in -mm which might be from vapier@xxxxxxxxxx are uio-howtotmpl-use-standard-copyright-legal-markings.patch uio-howtotmpl-use-unique-output-names.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