On Tue, 2007-03-20 at 12:19 -0700, Andrew Vasquez wrote: > SCSI_SCAN_ASYNC was compiled non-modularly before merging the latest > scsi-misc-2.6.git tree. After the merge, and a rebuild of the kernel, > was getting 'unknown symbol' failures during link as SCSI_WAIT_SCAN > was now forced to be built as a module. 'select'ion of SCSI_WAIT_SCAN > based on SCSI_SCAN_SYNC (a consumer) appeared to be the most natural > way to address the problem.
There's something else going on here. The only piece of code in the entire tree that depends on SCSI_SCAN_ASYNC is this one (in scsi_scan.c): #ifdef CONFIG_SCSI_SCAN_ASYNC #define SCSI_SCAN_TYPE_DEFAULT "async" #else #define SCSI_SCAN_TYPE_DEFAULT "sync" #endif There should be no way that setting this parameter to Y or N can have the effects you describe ... could you debug a bit further? Is MODULE set to 'n'? It looks like the symbol export is guarded by #ifdef MODULE for some reason ... other than that, I can't explain this. Thanks, James - To unsubscribe from this list: send the line "unsubscribe linux-scsi" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
