From: James Bottomley <James.Bottomley@SteelEye.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Kern Sibbald <kern@sibbald.com>,
Kai Makisara <Kai.Makisara@kolumbus.fi>,
linux-scsi@vger.kernel.org, Willem Riede <wrlk@riede.org>
Subject: Re: Linux tape drivers
Date: Tue, 03 Apr 2007 17:15:41 -0500 [thread overview]
Message-ID: <1175638541.3645.57.camel@mulgrave.il.steeleye.com> (raw)
In-Reply-To: <20070403145728.d8f83320.akpm@linux-foundation.org>
On Tue, 2007-04-03 at 14:57 -0700, Andrew Morton wrote:
> If it's purely a driver problem then it's presumably not relevant to the
> scsi developers. Raising a report at bugzilla.kernel.org would probably be
> appropriate - I will then route it to the appropriate developer (if any)
> and we'll at least know that we have an issue to be addressed.
Actually, that does depend on the kernel. If it's a SATAPI device, then
it will be using the st driver. Likewise, if it's one of the new PATA
things moved under drivers/ata, it should also be using st ... it's only
the legacy PATA devices that use ide-tape now.
Do we know what the kernel and device (and IDE controller) are?
James
next prev parent reply other threads:[~2007-04-03 22:16 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200704031508.37222.kern@sibbald.com>
2007-04-03 20:39 ` Linux tape drivers Andrew Morton
2007-04-03 21:30 ` Kern Sibbald
2007-04-03 21:57 ` Andrew Morton
2007-04-03 22:15 ` James Bottomley [this message]
2007-04-04 3:00 ` Willem Riede
2007-04-04 14:26 ` Kern Sibbald
2007-04-04 18:55 ` Andrew Morton
2007-04-04 19:21 ` Kern Sibbald
2007-04-04 20:37 ` Andrew Morton
2007-04-04 19:22 ` Willem Riede
2007-04-04 20:39 ` Andrew Morton
2007-04-04 21:31 ` Bartlomiej Zolnierkiewicz
2007-04-04 21:43 ` Andrew Morton
2007-04-04 18:46 ` Kai Makisara
2007-04-04 19:50 ` Douglas Gilbert
2007-04-04 20:58 ` Kern Sibbald
2007-04-04 21:54 ` Kai Makisara
2007-04-05 8:32 ` Kern Sibbald
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=1175638541.3645.57.camel@mulgrave.il.steeleye.com \
--to=james.bottomley@steeleye.com \
--cc=Kai.Makisara@kolumbus.fi \
--cc=akpm@linux-foundation.org \
--cc=kern@sibbald.com \
--cc=linux-scsi@vger.kernel.org \
--cc=wrlk@riede.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox