linux-kernel - Re: [PATCH][DOC]hpet.txt broken link fix

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]

Date:	Tue, 10 Jul 2007 19:42:47 -0700
From:	Randy Dunlap <randy.dunlap@...cle.com>
To:	Dave Young <hidave.darkstar@...il.com>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: [PATCH][DOC]hpet.txt broken link fix

On Wed, 11 Jul 2007 10:04:17 +0000 Dave Young wrote:

> The specification link in hpet document is broken.

OK.  Sadly it's a moving target.
Thanks.

> Signed-off-by: Dave Young <hidave.darkstar@...il.com> 
> 
> ---
> Documentation/hpet.txt |    2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff -pur linux/Documentation/hpet.txt linux.new/Documentation/hpet.txt
> --- linux/Documentation/hpet.txt	2007-07-11 09:37:24.000000000 +0000
> +++ linux.new/Documentation/hpet.txt	2007-07-11 09:46:33.000000000 +0000
> @@ -5,7 +5,7 @@ for the 8254 and Real Time Clock (RTC) p
>  Each HPET can have up to 32 timers.  It is possible to configure the
>  first two timers as legacy replacements for 8254 and RTC periodic timers.
>  A specification done by Intel and Microsoft can be found at
> -<http://www.intel.com/hardwaredesign/hpetspec.htm>.
> +<http://www.intel.com/technology/architecture/hpetspec.htm>.
>  
>  The driver supports detection of HPET driver allocation and initialization
>  of the HPET before the driver module_init routine is called.  This enables


---
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***
-
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/