From: Finn Thain <fthain@telegraphics.com.au>
To: "Justin P. Mattock" <justinmattock@gmail.com>
Cc: trivial@kernel.org, linux-kernel@vger.kernel.org,
jkosina@suse.cz, "Maciej W. Rozycki" <macro@linux-mips.org>,
Geert Uytterhoeven <geert@linux-m68k.org>,
Randy Dunlap <rdunlap@xenotime.net>,
Matt Turner <mattst88@gmail.com>,
Dimitry Torokhov <dmitry.torokhov@gmail.com>,
Mike Frysinger <vapier.adi@gmail.com>
Subject: Re: [PATCH v5]update broken web addresses in the kernel.
Date: Fri, 1 Oct 2010 23:12:01 +1000 (EST) [thread overview]
Message-ID: <alpine.OSX.2.00.1010012250340.382@localhost> (raw)
In-Reply-To: <1285854709-7488-2-git-send-email-justinmattock@gmail.com>
On Thu, 30 Sep 2010, Justin P. Mattock wrote:
> diff --git a/drivers/hwmon/hwmon-vid.c b/drivers/hwmon/hwmon-vid.c
> index bf0862a..897702d 100644
> --- a/drivers/hwmon/hwmon-vid.c
> +++ b/drivers/hwmon/hwmon-vid.c
> @@ -38,7 +38,7 @@
> * available at http://developer.intel.com/.
> *
> * AMD Athlon 64 and AMD Opteron Processors, AMD Publication 26094,
> - * http://www.amd.com/us-en/assets/content_type/white_papers_and_tech_docs/26094.PDF
> + * http://developer.amd.com/documentation/articles/pages/1212200690_2.aspx
That pdf has moved this URL:
http://support.amd.com/us/Processor_TechDocs/26094.PDF
> * Table 74. VID Code Voltages
> * This corresponds to an arbitrary VRM code of 24 in the functions below.
> * These CPU models (K8 revision <= E) have 5 VID pins. See also:
Regards,
Finn
next prev parent reply other threads:[~2010-10-01 13:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-30 13:51 [PATCH 1/2 v4]Update broken web addresses in arch directory Justin P. Mattock
2010-09-30 13:51 ` [PATCH v5]update broken web addresses in the kernel Justin P. Mattock
2010-10-01 13:12 ` Finn Thain [this message]
2010-10-01 12:47 ` [PATCH 1/2 v4]Update broken web addresses in arch directory Finn Thain
2010-10-01 16:13 ` Justin P. Mattock
2010-10-02 3:55 ` Finn Thain
2010-10-02 4:00 ` Justin P. Mattock
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=alpine.OSX.2.00.1010012250340.382@localhost \
--to=fthain@telegraphics.com.au \
--cc=dmitry.torokhov@gmail.com \
--cc=geert@linux-m68k.org \
--cc=jkosina@suse.cz \
--cc=justinmattock@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=macro@linux-mips.org \
--cc=mattst88@gmail.com \
--cc=rdunlap@xenotime.net \
--cc=trivial@kernel.org \
--cc=vapier.adi@gmail.com \
/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