From: Vladislav Bolkhovitin <vst@vlnb.net>
To: "Jeff V. Merkey" <jmerkey@wolfmountaingroup.com>
Cc: Linux kernel <linux-kernel@vger.kernel.org>
Subject: Re: scst support for kernels above 2.6.15
Date: Tue, 05 Dec 2006 20:53:35 +0300 [thread overview]
Message-ID: <4575B21F.9030202@vlnb.net> (raw)
In-Reply-To: <4575AC4B.4060008@wolfmountaingroup.com>
Jeff V. Merkey wrote:
> Vladislav Bolkhovitin wrote:
>
>
>>Jeff V. Merkey wrote:
>>
>>
>>
>>>I have noticed that scsi_do_req has apparently been obsoleted in 2.6.18
>>>and above. Is scst and target support for FC-AL going to
>>>remain supported and/or merged at some point? If so, what is planned
>>>for scst support for later kernels?
>>>
>>>
>>
>>Jeff, I don't know why you ask here and not in scst-devel mailing list,
>>but SCST has beed updated to use scsi_execute_async() instead of
>>scsi_do_req() in 2.6.18+ for quite a while. Yes, scst is going to be
>>supported in the future.
>>
>>Vlad
>>
>>
>
> The code is not at sourceforge on your project site with these updates
> for 2.6.18. Where is the 2.6.18 version currently hosted?
It is there on http://sourceforge.net/projects/scst
(http://scst.sourceforge.net/). See 0.9.5 release version as well as
development code in the SVN.
Vlad
> P.S. I will post this to the scsi list in the future.
For scst only questions scst-devel on lists.sourceforge.net would be better.
> Thanks
>
> Jeff
>
>
>>
>>
>>
>>>Jeff
>>>-
>>>To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
>>>the body of a message to majordomo@vger.kernel.org
>>>More majordomo info at http://vger.kernel.org/majordomo-info.html
>>>Please read the FAQ at http://www.tux.org/lkml/
>>>
>>>
>>>
>>
>>
>>
>>
>
>
>
next prev parent reply other threads:[~2006-12-05 17:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-04 23:13 scst support for kernels above 2.6.15 Jeff V. Merkey
2006-12-05 10:47 ` Vladislav Bolkhovitin
2006-12-05 17:28 ` Jeff V. Merkey
2006-12-05 17:53 ` Vladislav Bolkhovitin [this message]
2006-12-05 17:41 ` Jeff V. Merkey
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=4575B21F.9030202@vlnb.net \
--to=vst@vlnb.net \
--cc=jmerkey@wolfmountaingroup.com \
--cc=linux-kernel@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