diff options
| author | wiz <wiz@NetBSD.org> | 2001-06-19 13:45:52 +0000 |
|---|---|---|
| committer | wiz <wiz@NetBSD.org> | 2001-06-19 13:45:52 +0000 |
| commit | ac951736bc46f73736efef400a89133eaac980b1 (patch) | |
| tree | 8caf4e63a3d4139492808d5b95603d6572f7a8a3 /sys/dev | |
| parent | 3f9984fc90e813844e16f5bfbd6d419b847da028 (diff) | |
`response', not `responce'
Diffstat (limited to 'sys/dev')
| -rw-r--r-- | sys/dev/ic/rrunner.c | 4 | ||||
| -rw-r--r-- | sys/dev/microcode/aic7xxx/aic7xxx.seq | 4 |
2 files changed, 4 insertions, 4 deletions
diff --git a/sys/dev/ic/rrunner.c b/sys/dev/ic/rrunner.c index f1725ef3b61..db07f8a01e3 100644 --- a/sys/dev/ic/rrunner.c +++ b/sys/dev/ic/rrunner.c @@ -1,4 +1,4 @@ -/* $NetBSD: rrunner.c,v 1.23 2001/06/19 12:59:17 wiz Exp $ */ +/* $NetBSD: rrunner.c,v 1.24 2001/06/19 13:45:56 wiz Exp $ */ /* * Copyright (c) 1997, 1998 The NetBSD Foundation, Inc. @@ -844,7 +844,7 @@ esh_fpopen(dev, oflags, devtype, p) * Create the ring: * * XXX: HTF are we gonna deal with the fact that we don't know - * if the open succeeded until we get a responce from + * if the open succeeded until we get a response from * the event handler? I guess we could go to sleep waiting * for the interrupt, and get woken up by the eshintr * case handling it. diff --git a/sys/dev/microcode/aic7xxx/aic7xxx.seq b/sys/dev/microcode/aic7xxx/aic7xxx.seq index a61e28a0560..466b6a07cec 100644 --- a/sys/dev/microcode/aic7xxx/aic7xxx.seq +++ b/sys/dev/microcode/aic7xxx/aic7xxx.seq @@ -1,4 +1,4 @@ -/* $NetBSD: aic7xxx.seq,v 1.11 2000/03/15 02:09:11 fvdl Exp $ */ +/* $NetBSD: aic7xxx.seq,v 1.12 2001/06/19 13:45:57 wiz Exp $ */ /* * Adaptec 274x/284x/294x device driver firmware for Linux and FreeBSD. @@ -1061,7 +1061,7 @@ p_status: * This is done to allow the host to send messages outside of an identify * sequence while protecting the seqencer from testing the MK_MESSAGE bit * on an SCB that might not be for the current nexus. (For example, a - * BDR message in responce to a bad reselection would leave us pointed to + * BDR message in response to a bad reselection would leave us pointed to * an SCB that doesn't have anything to do with the current target). * * Otherwise, treat MSG_OUT as a 1 byte message to send (abort, abort tag, |
