From: James Bottomley <James.Bottomley@SteelEye.com>
To: Alex Aizman <itn780@yahoo.com>
Cc: SCSI Mailing List <linux-scsi@vger.kernel.org>,
Linux Kernel <linux-kernel@vger.kernel.org>,
Christoph Hellwig <hch@lst.de>
Subject: Re: [ANNOUNCE 0/7] Open-iSCSI/Linux-iSCSI-5 High-Performance Initiator
Date: Sat, 30 Jul 2005 12:32:42 -0500 [thread overview]
Message-ID: <1122744762.5055.10.camel@mulgrave> (raw)
In-Reply-To: <429E15CD.2090202@yahoo.com>
On Wed, 2005-06-01 at 13:08 -0700, Alex Aizman wrote:
> This is open-iscsi/linux-iscsi-5 Initiator. This submission is ready for
> inclusion into mainline kernel.
OK, I tried to put this into scsi-misc.
FIB has taken your netlink number, so I changed it to 32
__nlm_put() has had an updated prototype, which I can fix (although I'm
not sure you're supposed to be using this function...)
I can't fix up the compile errors in iscsi_tcp.c:
CC [M] drivers/scsi/iscsi_tcp.o
drivers/scsi/iscsi_tcp.c: In function `iscsi_hdr_extract':
drivers/scsi/iscsi_tcp.c:160: warning: implicit declaration of function
`iscsi_cnx_error'
drivers/scsi/iscsi_tcp.c:161: error: `ISCSI_ERR_PDU_GATHER_FAILED'
undeclared (first use in this function)
drivers/scsi/iscsi_tcp.c:161: error: (Each undeclared identifier is
reported only once
drivers/scsi/iscsi_tcp.c:161: error: for each function it appears in.)
drivers/scsi/iscsi_tcp.c: In function `iscsi_tcp_state_change':
drivers/scsi/iscsi_tcp.c:1005: error: `ISCSI_ERR_CNX_FAILED' undeclared
(first use in this function)
drivers/scsi/iscsi_tcp.c: In function `iscsi_sendhdr':
drivers/scsi/iscsi_tcp.c:1092: error: `ISCSI_ERR_CNX_FAILED' undeclared
(first use in this function)
drivers/scsi/iscsi_tcp.c: In function `iscsi_sendpage':
drivers/scsi/iscsi_tcp.c:1141: error: `ISCSI_ERR_CNX_FAILED' undeclared
(first use in this function)
drivers/scsi/iscsi_tcp.c: In function `iscsi_data_xmit_more':
drivers/scsi/iscsi_tcp.c:1707: error: `STOP_CNX_RECOVER' undeclared
(first use in this function)
drivers/scsi/iscsi_tcp.c: At top level:
[...]
Do you have an updated driver that will work in the current tree?
Thanks,
James
next prev parent reply other threads:[~2005-07-30 17:32 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-01 20:08 [ANNOUNCE 0/7] Open-iSCSI/Linux-iSCSI-5 High-Performance Initiator Alex Aizman
2005-06-01 20:54 ` Patrick McFarland
2005-06-01 21:08 ` Alex Aizman
2005-06-01 21:10 ` Ming Zhang
2005-07-30 17:32 ` James Bottomley [this message]
2005-07-30 18:36 ` Alex Aizman
2005-07-30 18:38 ` Christoph Hellwig
2005-07-30 19:53 ` David S. Miller
2005-07-30 19:53 ` David S. Miller
2005-07-30 20:23 ` James Bottomley
2005-07-30 21:25 ` Dmitry Yusupov
2005-07-31 0:33 ` David S. Miller
2005-08-02 17:18 ` Mike Christie
2005-07-31 0:34 ` David S. Miller
2005-08-06 20:46 ` Patrick McHardy
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=1122744762.5055.10.camel@mulgrave \
--to=james.bottomley@steeleye.com \
--cc=hch@lst.de \
--cc=itn780@yahoo.com \
--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