From 01085cc3df9c29c8a33ddbd2247ca78ceb10d7e4 Mon Sep 17 00:00:00 2001 From: Kenneth R Westerback Date: Sat, 3 Dec 2005 18:09:38 +0000 Subject: The first thing done when XXX_scsi_cmd() returns TRY_AGAIN_LATER is to set xs->error to XS_BUSY. So it is pointless and misleading to set xs->error to XS_TIMEOUT, XS_DRIVER_STUFFUP or XS_BUSY just before returning TRY_AGAIN_LATER. No functional change. ok miod@ --- sys/arch/mvme88k/dev/vs.c | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) (limited to 'sys/arch/mvme88k') diff --git a/sys/arch/mvme88k/dev/vs.c b/sys/arch/mvme88k/dev/vs.c index 3c570d1384f..67e12f21828 100644 --- a/sys/arch/mvme88k/dev/vs.c +++ b/sys/arch/mvme88k/dev/vs.c @@ -1,4 +1,4 @@ -/* $OpenBSD: vs.c,v 1.55 2005/04/27 14:09:45 miod Exp $ */ +/* $OpenBSD: vs.c,v 1.56 2005/12/03 18:09:37 krw Exp $ */ /* * Copyright (c) 2004, Miodrag Vallat. @@ -370,7 +370,6 @@ vs_scsicmd(struct scsi_xfer *xs) } else { cqep = vs_getcqe(sc); if (cqep == 0) { - xs->error = XS_DRIVER_STUFFUP; return (TRY_AGAIN_LATER); } iopb = vs_getiopb(sc); -- cgit v1.2.3