From: "J . A . Magallon" <jamagallon@able.es>
To: Linus Torvalds <torvalds@transmeta.com>
Cc: Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Linux 2.4.15-pre4 - merge with Alan
Date: Tue, 13 Nov 2001 00:43:03 +0100 [thread overview]
Message-ID: <20011113004303.C1531@werewolf.able.es> (raw)
In-Reply-To: <Pine.LNX.4.33.0111121056260.1078-100000@penguin.transmeta.com>
In-Reply-To: <Pine.LNX.4.33.0111121056260.1078-100000@penguin.transmeta.com>; from torvalds@transmeta.com on Mon, Nov 12, 2001 at 20:01:56 +0100
On 20011112 Linus Torvalds wrote:
>
>Ok, this kernel hopefully contains all the high-priority merges with Alan,
>which means that as far as that is concerned, I'm done with 2.4.x and
>ready to pass it on to Marcelo.
>
>Which means that I'd also like people to double-check that there are no
>embarrassing missing pieces due to the merge (or other patches).
>
This bit is in Alan's but not in your tree (also is in original aic-6.2.4):
diff -u -r -N linux-2.4.12.virgin/drivers/scsi/scsi_error.c linux-2.4.12/drivers/scsi/scsi_error.c
--- linux-2.4.12.virgin/drivers/scsi/scsi_error.c Sun Sep 9 11:52:35 2001
+++ linux-2.4.12/drivers/scsi/scsi_error.c Thu Oct 11 13:57:36 2001
@@ -1009,13 +1009,7 @@
SCpnt->flags &= ~IS_RESETTING;
goto maybe_retry;
}
- /*
- * Examine the sense data to figure out how to proceed from here.
- * If there is no sense data, we will be forced into the error
- * handler thread, where we get to examine the thing in a lot more
- * detail.
- */
- return scsi_check_sense(SCpnt);
+ return SUCCESS;
default:
return FAILED;
}
Is really needed ?
--
J.A. Magallon # Let the source be with you...
mailto:jamagallon@able.es
Mandrake Linux release 8.2 (Cooker) for i586
Linux werewolf 2.4.15-pre3-beo #1 SMP Mon Nov 12 00:04:41 CET 2001 i686
next prev parent reply other threads:[~2001-11-12 23:43 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-12 19:01 Linux 2.4.15-pre4 - merge with Alan Linus Torvalds
2001-11-12 19:18 ` Trever L. Adams
2001-11-13 11:14 ` Christoph Rohland
2001-11-12 19:26 ` Matthew Dharm
2001-11-12 20:09 ` Martin Dalecki
2001-11-12 20:42 ` Greg KH
2001-11-12 23:43 ` J . A . Magallon [this message]
2001-11-13 1:11 ` Alan Cox
2001-11-12 23:45 ` J . A . Magallon
2001-11-12 23:48 ` J . A . Magallon
2001-11-13 0:14 ` Christoph Hellwig
2001-11-13 0:25 ` J . A . Magallon
2001-11-13 0:42 ` J . A . Magallon
2001-11-13 7:43 ` Christoph Hellwig
2001-11-13 5:17 ` Keith Owens
2001-11-13 10:43 ` David S. Miller
2001-11-13 17:27 ` Chad N. Tindel
2001-11-13 17:58 ` Chad N. Tindel
2001-11-13 5:54 ` Neil Brown
2001-11-13 6:02 ` Jeff Garzik
2001-11-13 9:41 ` Alan Cox
2001-11-13 6:03 ` David S. Miller
2001-11-13 6:16 ` Keith Owens
2001-11-13 6:23 ` David S. Miller
2001-11-13 8:17 ` Jeff Garzik
2001-11-13 6:18 ` Keith Owens
2001-11-13 14:10 ` Horst von Brand
2001-11-13 15:21 ` Thorsten Kukuk
2001-11-14 4:57 ` David S. Miller
2001-11-14 6:28 ` Thorsten Kukuk
2001-11-14 6:31 ` David S. Miller
2001-11-14 12:59 ` Horst von Brand
2001-11-13 15:37 ` [PATCH] " Russell King
2001-11-15 9:25 ` Problem with Linux 2.4.15-pre4 on an IBM ThinkPad Martin Persson
2001-11-15 11:57 ` Keith Owens
-- strict thread matches above, loose matches on Subject: below --
2001-11-12 21:10 Linux 2.4.15-pre4 - merge with Alan Robert Cantu
2001-11-13 13:20 ` Andrey Savochkin
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=20011113004303.C1531@werewolf.able.es \
--to=jamagallon@able.es \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.com \
/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