From: "Justin P. Mattock" <justinmattock@gmail.com>
To: trivial@kernel.org
Cc: linux-kernel@vger.kernel.org,
"Justin P. Mattock" <justinmattock@gmail.com>
Subject: [PATCH]firmware/keyspan_pda/ Update brokwn web addresses.
Date: Fri, 10 Sep 2010 18:45:40 -0700 [thread overview]
Message-ID: <1284169540-6225-1-git-send-email-justinmattock@gmail.com> (raw)
The patch below updates the broken web addresses(but not really broken, just not there)
to the proper address.(from reading anchorchips is now cypress semiconductor).
Signed-off-by: Justin P. Mattock <justinmattock@gmail.com>
---
firmware/keyspan_pda/keyspan_pda.S | 2 +-
firmware/keyspan_pda/xircom_pgs.S | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/firmware/keyspan_pda/keyspan_pda.S b/firmware/keyspan_pda/keyspan_pda.S
index 418fe69..f3acc19 100644
--- a/firmware/keyspan_pda/keyspan_pda.S
+++ b/firmware/keyspan_pda/keyspan_pda.S
@@ -74,7 +74,7 @@
* recognizes the new device ID and glues it to the real serial driver code.
*
* USEFUL DOCS:
- * EzUSB Technical Reference Manual: <http://www.anchorchips.com>
+ * EzUSB Technical Reference Manual: <http://www.cypress.com/>
* 8051 manuals: everywhere, but try www.dalsemi.com because the EzUSB is
* basically the Dallas enhanced 8051 code. Remember that the EzUSB IO ports
* use totally different registers!
diff --git a/firmware/keyspan_pda/xircom_pgs.S b/firmware/keyspan_pda/xircom_pgs.S
index 05d99dd..0b79bbf 100644
--- a/firmware/keyspan_pda/xircom_pgs.S
+++ b/firmware/keyspan_pda/xircom_pgs.S
@@ -74,7 +74,7 @@
* recognizes the new device ID and glues it to the real serial driver code.
*
* USEFUL DOCS:
- * EzUSB Technical Reference Manual: <http://www.anchorchips.com>
+ * EzUSB Technical Reference Manual: <http://www.cypress.com/>
* 8051 manuals: everywhere, but try www.dalsemi.com because the EzUSB is
* basically the Dallas enhanced 8051 code. Remember that the EzUSB IO ports
* use totally different registers!
--
1.7.2.1
reply other threads:[~2010-09-11 1:45 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1284169540-6225-1-git-send-email-justinmattock@gmail.com \
--to=justinmattock@gmail.com \
--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
all inboxes | Powered by JetHome®