From: Randy Dunlap <randy.dunlap@oracle.com>
To: Dave Young <hidave.darkstar@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH][DOC]hpet.txt broken link fix
Date: Tue, 10 Jul 2007 19:42:47 -0700 [thread overview]
Message-ID: <20070710194247.a41fc2d1.randy.dunlap@oracle.com> (raw)
In-Reply-To: <20070711100417.GA2013@darkstar.te-china.tietoenator.com>
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@gmail.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 ***
next prev parent reply other threads:[~2007-07-11 2:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-11 10:04 [PATCH][DOC]hpet.txt broken link fix Dave Young
2007-07-11 2:42 ` Randy Dunlap [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-07-11 11:25 Dave Young
2007-07-11 4:52 ` Randy Dunlap
2007-07-18 3:03 ` Dave Young
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20070710194247.a41fc2d1.randy.dunlap@oracle.com \
--to=randy.dunlap@oracle.com \
--cc=hidave.darkstar@gmail.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox