Nick, please drop this patch. It doesn't make any sense -- after my fix that you have later in your series, tcm_loop works perfectly well built-in (and in fact is useful for quick debugging, along with "qemu -kernel"). - R. On Thu, Jul 21, 2011 at 12:04 AM, Nicholas A. Bellinger <nab@xxxxxxxxxxxxxxx> wrote: > From: Stefan Hajnoczi <stefanha@xxxxxxxxxxxxxxxxxx> > > The tcm_loop must be built as a module. It cannot be built in. > > Signed-off-by: Stefan Hajnoczi <stefanha@xxxxxxxxxxxxxxxxxx> > Signed-off-by: Nicholas A. Bellinger <nab@xxxxxxxxxxxxxxxxxxxxx> > --- > drivers/target/loopback/Kconfig | 3 ++- > 1 files changed, 2 insertions(+), 1 deletions(-) > > diff --git a/drivers/target/loopback/Kconfig b/drivers/target/loopback/Kconfig > index 57dcbc2..1bd6a65 100644 > --- a/drivers/target/loopback/Kconfig > +++ b/drivers/target/loopback/Kconfig > @@ -1,7 +1,8 @@ > config LOOPBACK_TARGET > tristate "TCM Virtual SAS target and Linux/SCSI LDD fabric loopback module" > + depends on m > help > - Say Y here to enable the TCM Virtual SAS target and Linux/SCSI LLD > + Say M here to enable the TCM Virtual SAS target and Linux/SCSI LLD > fabric loopback module. > > config LOOPBACK_TARGET_CDB_DEBUG > -- > 1.7.6 > > -- > To unsubscribe from this list: send the line "unsubscribe target-devel" in > the body of a message to majordomo@xxxxxxxxxxxxxxx > More majordomo info at http://vger.kernel.org/majordomo-info.html > -- To unsubscribe from this list: send the line "unsubscribe linux-scsi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
