From: James Bottomley <James.Bottomley@SteelEye.com>
To: Matthias Andree <ma@dt.e-technik.uni-dortmund.de>
Cc: Jeff Garzik <jgarzik@pobox.com>, Andrew Morton <akpm@osdl.org>,
Linus Torvalds <torvalds@osdl.org>,
SCSI Mailing List <linux-scsi@vger.kernel.org>,
Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: [BK PATCH] SCSI -rc1 fixes
Date: 14 Nov 2004 18:04:58 -0600 [thread overview]
Message-ID: <1100477105.24921.3.camel@mulgrave> (raw)
In-Reply-To: <m3hdnsvvfd.fsf@merlin.emma.line.org>
On Sun, 2004-11-14 at 17:54, Matthias Andree wrote:
> Still wondering about SuSE's hwscan issue. Has someone managed to figure
> if it uses some ioctl that chokes the sym2 driver or if it hacks the
> hardware?
Well, I think we're stuck on that one. SUSE doesn't seem willing to
debug hwscan enough to give a coherent description of the problem or a
non hwscan test case and no-one else wants to take hwscan apart to find
out exactly what it is doing.
James
next prev parent reply other threads:[~2004-11-15 0:04 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-14 21:20 [BK PATCH] SCSI -rc1 fixes James Bottomley
2004-11-14 23:05 ` Jeff Garzik
2004-11-14 23:09 ` James Bottomley
2004-11-14 23:54 ` Matthias Andree
2004-11-15 0:04 ` James Bottomley [this message]
2004-11-15 1:09 ` SuSE hwinfo/yast2 still confusing SYM53C8XX, killing tape backups (was: [BK PATCH] SCSI -rc1 fixes) Matthias Andree
2004-11-22 10:35 ` Steffen Winterfeldt
2004-11-22 11:17 ` Jens Axboe
2004-11-22 11:21 ` Steffen Winterfeldt
2004-11-22 11:23 ` Jens Axboe
2004-11-22 11:33 ` Steffen Winterfeldt
2004-11-22 11:37 ` Jens Axboe
2004-11-22 12:02 ` SuSE hwinfo/yast2 still confusing SYM53C8XX, killing tape backups Matthias Andree
2004-11-22 13:05 ` Steffen Winterfeldt
2004-11-22 13:30 ` Matthew Wilcox
2004-11-22 14:05 ` Matthias Andree
2004-11-26 14:16 ` Steffen Winterfeldt
2004-11-27 0:40 ` Matthias Andree
2004-11-29 11:16 ` Steffen Winterfeldt
2004-11-29 11:24 ` Matthias Andree
2004-12-03 22:35 ` Matthias Andree
2004-11-22 12:06 ` Douglas Gilbert
2004-11-22 13:07 ` Steffen Winterfeldt
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=1100477105.24921.3.camel@mulgrave \
--to=james.bottomley@steeleye.com \
--cc=akpm@osdl.org \
--cc=jgarzik@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=ma@dt.e-technik.uni-dortmund.de \
--cc=torvalds@osdl.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.