From: "Justin P. Mattock" <justinmattock@gmail.com>
To: "Maciej W. Rozycki" <macro@linux-mips.org>
Cc: trivial@kernel.org, linux-alpha@vger.kernel.org,
linux-kernel@vger.kernel.org, jkosina@suse.cz
Subject: Re: [PATCH 82/91] arch/mips/Kconfig Update broken web addresses in the arch directory.
Date: Thu, 02 Sep 2010 15:10:10 -0700 [thread overview]
Message-ID: <4C8020C2.2080204@gmail.com> (raw)
In-Reply-To: <alpine.LFD.2.00.1009022247190.410@eddie.linux-mips.org>
On 09/02/2010 02:53 PM, Maciej W. Rozycki wrote:
> On Thu, 2 Sep 2010, Justin P. Mattock wrote:
>
>> The below patch updates a broken web address that is no longer
>> working due to company buyout, and/or change of location.
>> (Please have a look through, and let me know if any of them
>> need to be changed, and I'll resend an updated patch).
>>
>> Signed-off-by: Justin P. Mattock<justinmattock@gmail.com>
>>
>> ---
>> arch/mips/Kconfig | 3 ++-
>> 1 files changed, 2 insertions(+), 1 deletions(-)
>>
>> diff --git a/arch/mips/Kconfig b/arch/mips/Kconfig
>> index 3ad59dd..984b14e 100644
>> --- a/arch/mips/Kconfig
>> +++ b/arch/mips/Kconfig
>> @@ -2178,7 +2178,8 @@ config TC
>> TurboChannel is a DEC (now Compaq (now HP)) bus for Alpha and MIPS
>> processors. Documentation on writing device drivers for TurboChannel
>> is available at:
>> - <http://www.cs.arizona.edu/computer.help/policy/DIGITAL_unix/AA-PS3HD-TET1_html/TITLE.html>.
>> + <http://web.archive.org/web/*/http://www.cs.arizona.edu/computer.help/
>> + policy/DIGITAL_unix/AA-PS3HD-TET1_html/TITLE.html>.
>>
>> #config ACCESSBUS
>> # bool "Access.Bus support"
>
> This is more<linux-mips@linux-mips.org>; we don't have TURBOchannel
> support for the Alpha (yet?).
>
> Anyway, a better source should be available; let me see. Also the
> original document could not have been the most appropriate one -- it looks
> more like a Digital Unix reference, while a set of hardware- and
> firmware-level documents used to be available for TURBOchannel devices
> (and HP probably still publishes them by inertia ;) ).
>
> Either way, thanks for tracking down these broken links.
>
> Maciej
>
I'm not sure about the turbo'ness :-)
the webarchive had it there so I just used it.(some sites actually are
not even archived to my amazement) in any case I'll use what you posted
and resend and the proper time.
Justin P. Mattock
next prev parent reply other threads:[~2010-09-02 22:10 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-02 21:13 [PATCH 76/91] arch/mips/math-emu/sp_modf.c Update broken web addresses in the arch directory Justin P. Mattock
2010-09-02 21:13 ` [PATCH 77/91] arch/mips/math-emu/dp_logb.c " Justin P. Mattock
2010-09-02 21:13 ` [PATCH 78/91] arch/mips/math-emu/sp_tlong.c " Justin P. Mattock
2010-09-02 21:13 ` [PATCH 79/91] arch/mips/math-emu/dp_flong.c " Justin P. Mattock
2010-09-02 21:13 ` [PATCH 80/91] arch/mips/math-emu/ieee754dp.h " Justin P. Mattock
2010-09-02 21:13 ` [PATCH 81/91] arch/mips/math-emu/sp_fdp.c " Justin P. Mattock
2010-09-02 21:13 ` [PATCH 82/91] arch/mips/Kconfig " Justin P. Mattock
2010-09-02 21:53 ` Maciej W. Rozycki
2010-09-02 22:10 ` Justin P. Mattock [this message]
2010-09-02 21:13 ` [PATCH 83/91] arch/powerpc/include/asm/hydra.h " Justin P. Mattock
2010-09-02 21:13 ` [PATCH 84/91] arch/sh/cchips/Kconfig " Justin P. Mattock
2010-09-02 21:13 ` [PATCH 85/91] arch/um/os-Linux/start_up.c " Justin P. Mattock
2010-09-02 21:13 ` [PATCH 86/91] arch/x86/kernel/microcode_core.c " Justin P. Mattock
2010-09-02 21:13 ` [PATCH 87/91] arch/x86/kernel/cpu/cpufreq/powernow-k8.c " Justin P. Mattock
2010-09-02 21:13 ` [PATCH 88/91] arch/x86/kernel/cpu/amd.c " Justin P. Mattock
2010-09-02 21:13 ` [PATCH 89/91] arch/x86/kernel/apm_32.c " Justin P. Mattock
2010-09-02 21:13 ` [PATCH 90/91] arch/x86/kernel/microcode_intel.c " Justin P. Mattock
2010-09-02 21:13 ` [PATCH 91/91] arch/x86/math-emu/README " 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=4C8020C2.2080204@gmail.com \
--to=justinmattock@gmail.com \
--cc=jkosina@suse.cz \
--cc=linux-alpha@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=macro@linux-mips.org \
--cc=trivial@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;
as well as URLs for NNTP newsgroup(s).