From: James Bottomley <James.Bottomley@SteelEye.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: John Stoffel <john@stoffel.org>,
fujita.tomonori@lab.ntt.co.jp, linux-kernel@vger.kernel.org,
linux-scsi@vger.kernel.org, Boaz Harrosh <bharrosh@panasas.com>
Subject: Re: 2.6.24-rc5: tape drive not responding
Date: Mon, 17 Dec 2007 15:52:28 -0600 [thread overview]
Message-ID: <1197928348.3204.14.camel@localhost.localdomain> (raw)
In-Reply-To: <20071217134344.3f024461.akpm@linux-foundation.org>
On Mon, 2007-12-17 at 13:43 -0800, Andrew Morton wrote:
> On Mon, 17 Dec 2007 16:02:02 -0500
> "John Stoffel" <john@stoffel.org> wrote:
>
> >
> > Just to confirm, the propsed patch to st.c fixes the issue with
> > 2.6.24-rc5 as well at 2.6.24-rc5-mm1 with access to my DLT tape
> > drives.
>
> err, what patch to st.c?
That's this one:
http://git.kernel.org/?p=linux/kernel/git/jejb/scsi-misc-2.6.git;a=commit;h=acdd0b1c371b2fbb4b6110a51ba69cb0af9e6f45
> So it seems that 2.6.24 (and presumably 2.6.23?) need
Not 2.6.23 .. the scatterlist changes causing the st problems are local
to 2.6.24.
> 1: Alan's "initio: fix conflict when loading driver" (currently stocuk
> in git-scsi-misc)
Yes, I'm moving this into scsi-rc-fixes
> 2: Boaz's "initio: initio_build_scb() fix" (my name for it)
And applying this ... although I'd still appreciate confirmation from
someone that the initio driver works after this.
> 3: The mystery st.c fix.
>
> yes?
James
next prev parent reply other threads:[~2007-12-17 21:52 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-17 1:05 2.6.24-rc5: tape drive not responding John Stoffel
2007-12-17 2:25 ` FUJITA Tomonori
2007-12-17 11:15 ` Andrew Morton
2007-12-17 18:57 ` John Stoffel
2007-12-17 20:08 ` John Stoffel
2007-12-17 21:02 ` John Stoffel
2007-12-17 21:43 ` Andrew Morton
2007-12-17 21:46 ` Jean-Louis Dupond
2007-12-17 21:52 ` James Bottomley [this message]
2007-12-17 23:47 ` John Stoffel
2007-12-18 20:18 ` Kai Makisara
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=1197928348.3204.14.camel@localhost.localdomain \
--to=james.bottomley@steeleye.com \
--cc=akpm@linux-foundation.org \
--cc=bharrosh@panasas.com \
--cc=fujita.tomonori@lab.ntt.co.jp \
--cc=john@stoffel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.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