From: "J.E.J. Bottomley" <James.Bottomley@steeleye.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: torvalds@transmeta.com, James.Bottomley@SteelEye.com,
linux-kernel@vger.kernel.org
Subject: Re: BOGUS: megaraid changes
Date: Sun, 10 Nov 2002 09:53:23 -0500 [thread overview]
Message-ID: <200211101453.gAAErOb10864@localhost.localdomain> (raw)
> Linus - will you please stop merging plain dangerous "lets pretend we
> never have errors" patches. I've got proper fixes for megaraid to use
> the new_eh if you want them, but merging stuff so that people don't
> even notice the problem is *WRONG*
This one came in through my scsi tree. How about we fix the issue in a
different way: I can add an option in SCSI to check for the new eh methods
and if it doesn't find any at all, panic the system saying that this driver
has no error handling but if you reboot with the scsi_no_error_handling option
it won't panic again?
James
next reply other threads:[~2002-11-10 14:46 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-10 14:53 J.E.J. Bottomley [this message]
2002-11-10 16:47 ` Alan Cox
2002-11-10 16:32 ` J.E.J. Bottomley
2002-11-10 17:08 ` Alan Cox
2002-11-10 18:43 ` Linus Torvalds
2002-11-10 19:04 ` J.E.J. Bottomley
2002-11-10 19:11 ` Linus Torvalds
2002-11-10 19:18 ` J.E.J. Bottomley
2002-11-10 19:37 ` Sam Ravnborg
2002-11-10 20:11 ` Alan Cox
[not found] ` <1037052584.12335.6.camel@dell_ss3.pdx.osdl.net>
[not found] ` <1037055810.4648.68.camel@irongate.swansea.linux.org.uk>
2002-11-12 22:44 ` Megaraid SCSI problems Stephen Hemminger
[not found] <200211070603.gA763cX03676@hera.kernel.org>
2002-11-10 14:47 ` BOGUS: megaraid changes Alan Cox
-- strict thread matches above, loose matches on Subject: below --
2002-11-10 14:46 Matt_Domsch
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=200211101453.gAAErOb10864@localhost.localdomain \
--to=james.bottomley@steeleye.com \
--cc=alan@lxorguk.ukuu.org.uk \
--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
Powered by JetHome