From: Christoph Hellwig <hch@infradead.org>
To: Willem Riede <osst@riede.org>
Cc: Christoph Hellwig <hch@lst.de>, linux-scsi@vger.kernel.org
Subject: Re: osst changes required to move forward to block request
Date: Tue, 7 Feb 2006 09:12:55 +0000 [thread overview]
Message-ID: <20060207091254.GA11691@infradead.org> (raw)
In-Reply-To: <1139274141l.7464l.1l@athena.riede.org>
On Mon, Feb 06, 2006 at 08:02:21PM -0500, Willem Riede wrote:
> On 02/06/2006 08:19:44 AM, Christoph Hellwig wrote:
> >Hi Willem,
> >
> >do you still maintain the osst driver? We're moving forward to
> >completly get rid of the scsi_request structure in the scsi midlayer,
> >and osst is the only upper level driver still using it. I've tried to
> >convert it similar to st, but gave up. The biggest problem for me is
> >the scsi_request reuse over the driver where a pointer to a pointer to
> >a scsi_request is passed along all the callchain, and I have a really
> >hard time to find out whether the functions actually looks it, or only
>
> "looks it"?? don't understand :-(
sorry, should have read "looks at it" as in examines fields in the request
or looks at the result of performing the scsi command.
> But I will certainly help retire scsi_request. And anything else that is
> needed to keep up with proper kernel style. Let me know what those are, if
> you would? I'll start looking at how st has changed, and will be back with
> any questions I may have.
right now the above is the most urgent bit. What would be nice but not
required is a conversion to the sense handling helpers, similar to what
st got (aka using the *normalize_sense functions and then dealing with the
parsed sense buffer instead of the raw sense data)
next prev parent reply other threads:[~2006-02-07 9:12 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-06 13:19 osst changes required to move forward to block request Christoph Hellwig
2006-02-07 1:02 ` Willem Riede
2006-02-07 9:12 ` Christoph Hellwig [this message]
2006-02-11 19:46 ` Willem Riede
2006-02-14 19:24 ` Christoph Hellwig
2006-02-19 20:27 ` Willem Riede
2006-03-07 11:59 ` Christoph Hellwig
2006-03-07 21:53 ` James Bottomley
2006-03-07 22:16 ` Willem Riede
2006-03-07 22:43 ` Christoph Hellwig
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=20060207091254.GA11691@infradead.org \
--to=hch@infradead.org \
--cc=hch@lst.de \
--cc=linux-scsi@vger.kernel.org \
--cc=osst@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