public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Thomas Weber <weber@corscience.de>
To: "Justin P. Mattock" <justinmattock@gmail.com>
Cc: trivial@kernel.org, linux-doc@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 85/85]Documentation/networking/README.ipw2100 update web address.
Date: Wed, 21 Jul 2010 11:16:11 +0200	[thread overview]
Message-ID: <4C46BADB.9080308@corscience.de> (raw)
In-Reply-To: <1279688153-29571-10-git-send-email-justinmattock@gmail.com>

Am 21.07.2010 06:55, schrieb Justin P. Mattock:
> The patch below updates a broken web address.
> 
> Signed-off-by: Justin P. Mattock <justinmattock@gmail.com>
> 
> ---
>  Documentation/networking/README.ipw2100 |    2 +-
>  1 files changed, 1 insertions(+), 1 deletions(-)
> 
> diff --git a/Documentation/networking/README.ipw2100 b/Documentation/networking/README.ipw2100
> index f3fcaa4..306540e 100644
> --- a/Documentation/networking/README.ipw2100
> +++ b/Documentation/networking/README.ipw2100
> @@ -72,7 +72,7 @@ such, if you are interested in deploying or shipping a driver as part of
>  solution intended to be used for purposes other than development, please
>  obtain a tested driver from Intel Customer Support at:
>  
> -http://support.intel.com/support/notebook/sb/CS-006408.htm
> +http://support.intel.com
>  
>  
>  1. Introduction

The best result I could find on Intel website

http://www.intel.com/support/wireless/sb/CS-006408.htm

replaces notebook with wireless.

Thomas

  reply	other threads:[~2010-07-21  9:17 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-21  4:55 [PATCH 76/76]Documentation/networking/fore200e.txt update web address Justin P. Mattock
2010-07-21  4:55 ` [PATCH 77/77]Documentation/networking/tlan.txt " Justin P. Mattock
2010-07-21  4:55 ` [PATCH 78/78]Documentation/networking/arcnet.txt update web addresses Justin P. Mattock
2010-07-21  4:55 ` [PATCH 79/79]Documentation/networking/udplite.txt update web address Justin P. Mattock
2010-07-21  4:55 ` [PATCH 80/80]Documentation/networking/README.ipw2200 " Justin P. Mattock
2010-07-21  4:55 ` [PATCH 81/81]Documentation/networking/3c509.txt " Justin P. Mattock
2010-07-21  4:55 ` [PATCH 82/82]Documentation/networking/s2io.txt update wbe address Justin P. Mattock
2010-07-21  9:05   ` Thomas Weber
2010-07-21 13:34     ` Justin P. Mattock
2010-07-21  4:55 ` [PATCH 83/83]Documentation/networking/packet_mmap.txt update web address Justin P. Mattock
2010-07-21  4:55 ` [PATCH 84/84]Documentation/networking/ipddp.txt " Justin P. Mattock
2010-07-21  4:55 ` [PATCH 85/85]Documentation/networking/README.ipw2100 " Justin P. Mattock
2010-07-21  9:16   ` Thomas Weber [this message]
2010-07-21 13:32     ` Justin P. Mattock
2010-07-21  4:55 ` [PATCH 86/86]Documentation/networking/README.sb1000 " Justin P. Mattock
2010-07-21  4:55 ` [PATCH 87/87]Documentation/networking/wavelan.txt " Justin P. Mattock
2010-07-21  4:55 ` [PATCH 88/88]Documentation/networking/ray_cs.txt " Justin P. Mattock
2010-07-21  4:55 ` [PATCH 89/89]Documentation/power/basic-pm-debugging.txt " Justin P. Mattock
2010-07-21  4:55 ` [PATCH 90/90]Documentation/power/video.txt " 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=4C46BADB.9080308@corscience.de \
    --to=weber@corscience.de \
    --cc=justinmattock@gmail.com \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.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