linux-kernel - Re: [PATCH] uio-howto.tmpl: use unique output names

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <20080624141938.GC3217@local>
Date:	Tue, 24 Jun 2008 16:19:38 +0200
From:	"Hans J. Koch" <hjk@...utronix.de>
To:	Mike Frysinger <vapier@...too.org>
Cc:	hjk@...utronix.de, linux-kernel@...r.kernel.org,
	akpm@...ux-foundation.org, gregkh@...e.de
Subject: Re: [PATCH] uio-howto.tmpl: use unique output names

(Added GregKH to Cc:)

On Sun, Jun 22, 2008 at 11:18:48PM -0400, Mike Frysinger wrote:
> 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@...too.org>

Signed-off-by: Hans J. Koch <hjk@...utronix.de>

> ---
>  Documentation/DocBook/uio-howto.tmpl |    2 +-
>  1 files changed, 1 insertions(+), 1 deletions(-)
> 
> diff --git a/Documentation/DocBook/uio-howto.tmpl b/Documentation/DocBook/uio-howto.tmpl
> index 3da4855..d38fbde 100644
> --- a/Documentation/DocBook/uio-howto.tmpl
> +++ b/Documentation/DocBook/uio-howto.tmpl
> @@ -69,7 +69,7 @@ GPL version 2.
>  </bookinfo>
>  
>  <chapter id="aboutthisdoc">
> -<?dbhtml filename="about.html"?>
> +<?dbhtml filename="aboutthis.html"?>
>  <title>About this document</title>
>  
>  <sect1 id="translations">
> -- 
> 1.5.5.3
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/