From: Mike Christie <mikenc@us.ibm.com>
To: Mark Haverkamp <markh@osdl.org>
Cc: Mike Christie <michaelc@cs.wisc.edu>,
linux-scsi <linux-scsi@vger.kernel.org>
Subject: Re: [PATCH 6/10][RFC] linux-iscsi driver
Date: Wed, 12 Jan 2005 15:22:20 -0800 [thread overview]
Message-ID: <41E5B12C.2030802@us.ibm.com> (raw)
In-Reply-To: <1105570966.21043.6.camel@markh1.pdx.osdl.net>
Mark Haverkamp wrote:
> On Wed, 2005-01-12 at 14:57 -0800, Mike Christie wrote:
>
>>Mark Haverkamp wrote:
>>
>>>On Mon, 2005-01-10 at 15:01 -0800, Mike Christie wrote:
>>>
>>>
>>>>The attached patch implememts the IO functions for
>>>>the driver. They are built upon the network
>>>>subsystem's socket functions, so any ideas about
>>>>how to handle OOM situations when using that
>>>>layer would be greatly appreciated.
>>>
>>>
>>>I get:
>>>
>>> BUILD arch/i386/boot/bzImage
>>>Root device is (3, 3)
>>>Boot sector 512 bytes.
>>>Setup is 5215 bytes.
>>>System is 2530 kB
>>>Kernel: arch/i386/boot/bzImage is ready
>>> Building modules, stage 2.
>>> MODPOST
>>>*** Warning: "__scsi_print_sense" [drivers/scsi/iscsi-sfnet/iscsi_sfnet.ko] undefined!
>>>
>>>
>>>when building the iscsi module in the latest kernel BK view.
>>>
>>>
>>
>>just to make sure, when you open drivers/scsi/constants.c
>>you see
>>EXPORT_SYMBOL(__scsi_print_sense);
>>right?
>
>
> I don't see __scsi_print_sense in constants.c, just scsi_print_sense and
> it has a different arg list than your usage of __scsi_print_sense.
>
> Mark.
>
In the newest constants.c in scsi-misc it looks like it is there
http://linux-scsi.bkbits.net:8080/scsi-misc-2.6/anno/drivers/scsi/constants.c@1.22?nav=index.html|src/|src/drivers|src/drivers/scsi
Same for http://linux.bkbits.net:8080/linux-2.5
http://linux.bkbits.net:8080/linux-2.5/anno/drivers/scsi/constants.c@1.22?nav=index.html|src/|src/drivers|src/drivers/scsi
next prev parent reply other threads:[~2005-01-12 23:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-10 23:01 [PATCH 6/10][RFC] linux-iscsi driver Mike Christie
2005-01-12 22:41 ` Mark Haverkamp
2005-01-12 22:57 ` Mike Christie
2005-01-12 23:02 ` Mark Haverkamp
2005-01-12 23:22 ` Mike Christie [this message]
2005-01-12 23:59 ` Mark Haverkamp
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=41E5B12C.2030802@us.ibm.com \
--to=mikenc@us.ibm.com \
--cc=linux-scsi@vger.kernel.org \
--cc=markh@osdl.org \
--cc=michaelc@cs.wisc.edu \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.