linux-kernel - [PATCH 190/223]drivers/staging/comedi/drivers/pcl711.c Update broken web addresses.

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Thu,  9 Sep 2010 15:44:08 -0700
From:	"Justin P. Mattock" <justinmattock@...il.com>
To:	trivial@...nel.org
Cc:	linux-kernel@...r.kernel.org,
	"Justin P. Mattock" <justinmattock@...il.com>
Subject: [PATCH 190/223]drivers/staging/comedi/drivers/pcl711.c Update broken web addresses.

Below you will find an Update to a broken web address.
Please let me know if this needs to be changed.

Signed-off-by: Justin P. Mattock <justinmattock@...il.com>

---
 drivers/staging/comedi/drivers/pcl711.c |    2 +-
 1 files changed, 1 insertions(+), 1 deletions(-)

diff --git a/drivers/staging/comedi/drivers/pcl711.c b/drivers/staging/comedi/drivers/pcl711.c
index b44386a..b86dda1 100644
--- a/drivers/staging/comedi/drivers/pcl711.c
+++ b/drivers/staging/comedi/drivers/pcl711.c
@@ -41,7 +41,7 @@ supported.
    driver for the PCL-711.  I used a few ideas from his driver
    here.  His driver also has more comments, if you are
    interested in understanding how this driver works.
-   http://tech.buffalostate.edu/~dave/driver/
+   http://web.archive.org/web/*/http://tech.buffalostate.edu/~dave/driver/ 
 
    The ACL-8112 driver was hacked from the sources of the PCL-711
    driver (the 744 chip used on the 8112 is almost the same as
-- 
1.7.2.1

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/