why does x86 "make defconfig" build a single, lonely module?

  not a big deal, but is there a reason that a "make defconfig" on my
x86 system ends up selecting and building a single module?

  Building modules, stage 2.
  MODPOST 1 modules
  CC      drivers/scsi/scsi_wait_scan.mod.o
  LD [M]  drivers/scsi/scsi_wait_scan.ko

is there something special about that module?  just curious.

rday
-- 
========================================================================
Robert P. J. Day
Linux Consulting, Training and Annoying Kernel Pedantry
Waterloo, Ontario, CANADA

http://fsdev.net/wiki/index.php?title=Main_Page
========================================================================
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Follow-Ups:
- Re: why does x86 "make defconfig" build a single, lonely module?
  - From: Dave Jones <[email protected]>
- Re: why does x86 "make defconfig" build a single, lonely module?
  - From: Jan Engelhardt <[email protected]>

Prev by Date: Re: [patch] make pit clocksource continuous
Next by Date: [patch] CFS scheduler, -v12
Previous by thread: [PATCH] allow kernel module exclusion on load
Next by thread: Re: why does x86 "make defconfig" build a single, lonely module?
Index(es):
- Date
- Thread

[Index of Archives] [Kernel Newbies] [Netfilter] [Bugtraq] [Photo] [Stuff] [Gimp] [Yosemite News] [MIPS Linux] [ARM Linux] [Linux Security] [Linux RAID] [Video 4 Linux] [Linux for the blind] [Linux Resources]