From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: Kai Makisara <Kai.Makisara@kolumbus.fi>
Cc: linux-scsi@vger.kernel.org, Arne Wiebalck <arne.wiebalck@cern.ch>
Subject: Re: [RFC, PATCH v2] SCSI tape: MTIOCSENSE ioctl to return the sense data from errors
Date: Mon, 21 Jul 2008 11:30:40 -0500 [thread overview]
Message-ID: <1216657840.3433.38.camel@localhost.localdomain> (raw)
In-Reply-To: <alpine.LNX.1.10.0807131723510.16437@kai.makisara.local>
On Sun, 2008-07-13 at 17:24 +0300, Kai Makisara wrote:
> Here is the second version of the proposed MTIOCSENSE patch. The changes from
> the first version are:
>
> 1. The command descriptor block (up to 16 bytes) is included in the
> result. The cost is small but the exact command can be useful in
> interpretation of the sense data.
>
> 2. The residual from the HBA is included in the returned data.
>
> 3. Randy's documentation fix.
>
> 4. Computation of the length field uses also the additional length field in
> the sense data.
>
> The stsense utility at URL http://www.kolumbus.fi/kai.makisara/st.html has
> been updated to use the new ioctl definition.
>
> The patch below this text applies to 2.6.26-rc9 plus the two bug fixes I have
> sent to linux-scsi (applies with offsets without these fixes).
You listed this as an RFC, so I haven't done anything with it but if you
want this in for 2.6.27 you'd better change that to a proper PATCH
before the merge window closes.
James
next prev parent reply other threads:[~2008-07-21 16:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-11 13:57 [RFC, PATCH] SCSI tape: MTIOCSENSE ioctl to return the sense data from errors Kai Makisara
2008-07-11 18:07 ` Randy Dunlap
2008-07-13 14:24 ` [RFC, PATCH v2] " Kai Makisara
2008-07-21 16:30 ` James Bottomley [this message]
2008-07-21 19:27 ` 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=1216657840.3433.38.camel@localhost.localdomain \
--to=james.bottomley@hansenpartnership.com \
--cc=Kai.Makisara@kolumbus.fi \
--cc=arne.wiebalck@cern.ch \
--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