linux-next: Tree for May 5
Subsystems (4)
Hi all,
Changes since 20100504:
Dropped trees: tmio-mmc (long unresolved conflicts and unable to fetch)
hwlat (at the maintainer's request)
----------------------------------------------------------------------------
I have created today's linux-next tree atgit://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
(patches at http://www.kernel.org/pub/linux/kernel/v2.6/next/ ). If you are tracking the linux-next tree using git, you should not use "git pull" to do so as that will try to merge the new linux-next release with the old one. You should use "git fetch" as mentioned in the FAQ on the wiki (see below).
You can see which trees have been included by looking in the Next/Trees file in the source. There are also quilt-import.log and merge.log files in the Next directory. Between each merge, the tree was built with a ppc64_defconfig for powerpc and an allmodconfig for x86_64. After the final fixups (if any), it is also built with powerpc allnoconfig (32 and 64 bit), ppc44x_defconfig and allyesconfig (minus CONFIG_PROFILE_ALL_BRANCHES - this fails its final link) and i386, sparc and sparc64 defconfig. These builds also have CONFIG_ENABLE_WARN_DEPRECATED, CONFIG_ENABLE_MUST_CHECK and CONFIG_DEBUG_INFO disabled when necessary.
Below is a summary of the state of the merge.
We are up to 162 trees (counting Linus' and 22 trees of patches pending for Linus' tree), more are welcome (even if they are currently empty). Thanks to those who have contributed, and to those who haven't, please do.
Status of my local build tests will be at
http://kisskb.ellerman.id.au/linux-next . If maintainers want to give advice about cross compilers/configs that work, we are always open to add more builds.
Thanks to Jan Dittmer for adding the linux-next tree to his build tests at http://l4x.org/k/ , the guys at http://test.kernel.org/ and Randy Dunlap for doing many randconfig builds.
There is a wiki covering stuff to do with linux-next at
http://linux.f-seidel.de/linux-next/pmwiki/ . Thanks to Frank Seidel.
Signature · 229 lines
Cheers, Stephen Rothwell [email protected] $ git checkout master $ git reset --hard stable Merging origin/master Merging fixes/fixes Merging arm-current/master Merging m68k-current/for-linus Merging powerpc-merge/merge Merging sparc-current/master Merging scsi-rc-fixes/master Merging net-current/master Applying: ar9170: fix for driver-core ABI change Merging sound-current/for-linus Merging pci-current/for-linus Merging wireless-current/master Merging kbuild-current/for-linus Merging quilt/driver-core.current Merging quilt/tty.current Merging quilt/usb.current Merging quilt/staging.current Applying: staging: update gfp/slab.h includes Merging cpufreq-current/fixes Merging input-current/for-linus Merging md-current/for-linus Merging audit-current/for-linus Merging crypto-current/master Merging ide-curent/master Merging dwmw2/master Merging gcl-current/merge Merging arm/devel Applying: arm: update gfp/slab.h includes Merging davinci/davinci-next Applying: davinci: update gfp/slab.h includes Merging i.MX/for-next Merging msm/for-next CONFLICT (content): Merge conflict in arch/arm/mach-msm/Kconfig Merging omap/for-next Merging pxa/for-next Merging samsung/next-samsung Merging avr32/avr32-arch Merging blackfin/for-linus Merging cris/for-next Merging ia64/test Merging m68k/for-next Merging m68knommu/for-next Merging microblaze/next Merging mips/mips-for-linux-next Merging parisc/next Merging powerpc/next Merging 4xx/next Merging 52xx-and-virtex/next Merging galak/next Merging s390/features Merging sh/master Merging genesis/master Merging sparc/master Merging xtensa/master Merging ceph/for-next Merging cifs/master Merging configfs/linux-next Merging ecryptfs/next Merging ext3/for_next Merging ext4/next Merging fatfs/master Merging fuse/for-next Merging gfs2/master Merging jfs/next Merging logfs/master Merging nfs/linux-next Merging nfsd/nfsd-next Merging nilfs2/for-next Merging ocfs2/linux-next Applying: ocfs2: update gfp/slab.h includes Merging squashfs/master Merging udf/for_next Merging v9fs/for-next CONFLICT (content): Merge conflict in fs/9p/vfs_super.c Merging ubifs/linux-next Merging xfs/master Merging vfs/for-next CONFLICT (content): Merge conflict in fs/cifs/file.c CONFLICT (content): Merge conflict in fs/namei.c CONFLICT (content): Merge conflict in fs/nfs/inode.c CONFLICT (content): Merge conflict in fs/nfsd/nfs4xdr.c CONFLICT (content): Merge conflict in fs/nfsd/vfs.c CONFLICT (content): Merge conflict in fs/ufs/inode.c CONFLICT (content): Merge conflict in fs/xfs/linux-2.6/xfs_super.c CONFLICT (content): Merge conflict in security/tomoyo/realpath.c Merging pci/linux-next Merging hid/for-next Merging quilt/i2c Merging bjdooks-i2c/next-i2c Merging quilt/jdelvare-hwmon Merging quilt/kernel-doc Merging v4l-dvb/master Applying: v4l-dvb: update gfp/slab.h includes Merging kbuild/for-next Merging kconfig/for-next Merging ide/master Merging libata/NEXT Merging infiniband/for-next Merging acpi/test Applying: acpi: update gfp/slab.h includes Merging ieee1394/for-next Merging ubi/linux-next Merging kvm/linux-next Merging dlm/next Merging ibft/master Merging scsi/master Merging async_tx/next Merging net/master CONFLICT (content): Merge conflict in drivers/scsi/iscsi_tcp.c Merging wireless/master CONFLICT (content): Merge conflict in drivers/net/wireless/libertas_tf/cmd.c CONFLICT (content): Merge conflict in drivers/net/wireless/libertas_tf/main.c Applying: wireless: update gfp/slab.h includes Merging mtd/master CONFLICT (content): Merge conflict in drivers/mtd/mtdcore.c Applying: mtd: update gfp/slab.h includes Merging crypto/master CONFLICT (content): Merge conflict in arch/arm/mach-omap2/devices.c Merging sound/for-next Merging cpufreq/next Merging quilt/rr CONFLICT (content): Merge conflict in drivers/net/virtio_net.c CONFLICT (content): Merge conflict in include/linux/mod_devicetable.h CONFLICT (content): Merge conflict in scripts/mod/file2alias.c Merging mmc/next Merging input/next Merging lsm/for-next Merging block/for-next CONFLICT (content): Merge conflict in fs/ext3/fsync.c CONFLICT (content): Merge conflict in fs/ext4/fsync.c Merging quilt/device-mapper Merging embedded/master Merging firmware/master Merging pcmcia/master CONFLICT (content): Merge conflict in drivers/net/pcmcia/3c589_cs.c CONFLICT (content): Merge conflict in drivers/net/wireless/orinoco/orinoco_cs.c CONFLICT (content): Merge conflict in drivers/net/wireless/orinoco/spectrum_cs.c Merging battery/master Merging leds/for-mm Merging backlight/for-mm Merging kgdb/kgdb-next Applying: kgdb: update for sysrq handling change Applying: kdb: update gfp/slab.h includes Merging slab/for-next Merging uclinux/for-next Merging md/for-next Merging mfd/for-next CONFLICT (content): Merge conflict in drivers/dma/Makefile CONFLICT (add/add): Merge conflict in drivers/dma/timb_dma.c Merging hdlc/hdlc-next Merging drm/drm-next CONFLICT (content): Merge conflict in drivers/gpu/drm/i915/i915_drv.h CONFLICT (content): Merge conflict in drivers/gpu/drm/radeon/r300.c Merging viafb/viafb-next Merging voltage/for-next Merging security-testing/next Merging lblnet/master Merging agp/agp-next Merging uwb/for-upstream Merging watchdog/master Merging bdev/master Merging dwmw2-iommu/master Merging cputime/cputime Merging osd/linux-next Merging jc_docs/docs-next Merging nommu/master Merging trivial/for-next Merging audit/for-next Merging quilt/aoe Merging suspend/linux-next Merging bluetooth/master Merging fsnotify/for-next Applying: fsnotify: update gfp/slab.h includes Merging irda/for-next CONFLICT (content): Merge conflict in drivers/net/irda/irda-usb.c Merging drbd/for-jens Merging catalin/for-next Merging alacrity/linux-next CONFLICT (content): Merge conflict in include/linux/Kbuild CONFLICT (content): Merge conflict in lib/Kconfig Applying: vbus: use of kzalloc/kfree requires the include of slab.h Applying: vbus: update gfp/slab.h includes Merging i7core_edac/linux_next Merging devicetree/next-devicetree Merging spi/next-spi Merging omap_dss2/for-next Merging tip/auto-latest CONFLICT (content): Merge conflict in Documentation/feature-removal-schedule.txt Applying: lockdep: Fix redundant_hardirqs_on incremented with irqs enabled Merging edac-amd/for-next Merging oprofile/for-next Merging percpu/for-next Merging workqueues/for-next Merging sfi/sfi-test Merging asm-generic/next Merging hwpoison/hwpoison Merging sysctl/master Merging bkl-core/bkl/core Merging bkl-procfs/bkl/procfs Merging bkl-ioctl/bkl/ioctl CONFLICT (content): Merge conflict in arch/cris/arch-v10/drivers/ds1302.c CONFLICT (content): Merge conflict in drivers/block/pktcdvd.c Merging quilt/driver-core CONFLICT (content): Merge conflict in drivers/base/platform.c CONFLICT (content): Merge conflict in drivers/staging/comedi/drivers/quatech_daqp_cs.c Applying: md: fixup for sysfs_get_dirent API change Merging quilt/tty CONFLICT (content): Merge conflict in include/linux/tty.h Merging quilt/usb CONFLICT (content): Merge conflict in drivers/input/tablet/acecad.c CONFLICT (content): Merge conflict in drivers/input/tablet/kbtab.c CONFLICT (content): Merge conflict in drivers/input/tablet/wacom_sys.c CONFLICT (delete/modify): sound/usb/usbaudio.c deleted in HEAD and modified in quilt/usb. Version quilt/usb of sound/usb/usbaudio.c left in tree. $ git rm -f sound/usb/usbaudio.c Applying: usb: update gfp/slab.h includes Applying: sound: fixup for usb_buffer_alloc/free rename Merging staging-next/staging-next CONFLICT (content): Merge conflict in drivers/staging/arlan/arlan-main.c CONFLICT (content): Merge conflict in drivers/staging/comedi/drivers/cb_das16_cs.c CONFLICT (content): Merge conflict in drivers/staging/cx25821/cx25821-alsa.c CONFLICT (content): Merge conflict in drivers/staging/dt3155/dt3155_drv.c CONFLICT (content): Merge conflict in drivers/staging/netwave/netwave_cs.c Merging slabh/slabh Merging scsi-post-merge/master
PATCH 1/1 media: fix vivi build error
From: Randy Dunlap <[email protected]>
vivi uses find_font(), which is only available when FONTS is enabled, so make vivi depend on FONTS.
ERROR: "find_font" [drivers/media/video/vivi.ko] undefined!
--- drivers/media/video/Kconfig | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
drivers/media/video/Kconfig +1 -1
@@ -559,7 +559,7 @@ config VIDEO_DAVINCI_VPIF config VIDEO_VIVI tristate "Virtual Video Driver" - depends on VIDEO_DEV && VIDEO_V4L2 && !SPARC32 && !SPARC64 + depends on VIDEO_DEV && VIDEO_V4L2 && !SPARC32 && !SPARC64 && FONTS select FONT_8x16 select VIDEOBUF_VMALLOC default n
PATCH 1/1 usb gadget webcam: depends on VIDEO_DEV
In reply to Stephen RothwellFrom: Randy Dunlap <[email protected]>
g_webcam uses v4l[2] interfaces, so it should depend on VIDEO_DEV.
ERROR: "v4l2_event_unsubscribe" [drivers/usb/gadget/g_webcam.ko] undefined!
ERROR: "v4l2_event_queue" [drivers/usb/gadget/g_webcam.ko] undefined!
ERROR: "video_device_release" [drivers/usb/gadget/g_webcam.ko] undefined!
ERROR: "video_usercopy" [drivers/usb/gadget/g_webcam.ko] undefined!
ERROR: "v4l2_event_dequeue" [drivers/usb/gadget/g_webcam.ko] undefined!
ERROR: "video_register_device" [drivers/usb/gadget/g_webcam.ko] undefined!
ERROR: "video_device_alloc" [drivers/usb/gadget/g_webcam.ko] undefined!
ERROR: "v4l2_event_subscribe" [drivers/usb/gadget/g_webcam.ko] undefined!
ERROR: "video_unregister_device" [drivers/usb/gadget/g_webcam.ko] ndefined!
ERROR: "v4l2_event_pending" [drivers/usb/gadget/g_webcam.ko] undefined!
ERROR: "v4l2_fh_init" [drivers/usb/gadget/g_webcam.ko] undefined!
ERROR: "v4l2_event_init" [drivers/usb/gadget/g_webcam.ko] undefined!
ERROR: "video_devdata" [drivers/usb/gadget/g_webcam.ko] undefined!
ERROR: "v4l2_event_alloc" [drivers/usb/gadget/g_webcam.ko] undefined!
ERROR: "v4l2_fh_add" [drivers/usb/gadget/g_webcam.ko] undefined!
ERROR: "v4l2_fh_del" [drivers/usb/gadget/g_webcam.ko] undefined!
ERROR: "v4l2_fh_exit" [drivers/usb/gadget/g_webcam.ko] undefined!
--- drivers/usb/gadget/Kconfig | 1 + 1 file changed, 1 insertion(+)
drivers/usb/gadget/Kconfig +1 -0
@@ -879,6 +879,7 @@ config USB_G_HID # or video class gadget drivers), or specific hardware, here. config USB_G_WEBCAM tristate "USB Webcam Gadget" + depends on VIDEO_DEV help The Webcam Gadget acts as a composite USB Audio and Video Class device. It provides a userspace API to process UVC control requests
[email protected]
Appliedpatch usb-gadget-webcam-depends-on-video_dev.patch added to gregkh-2.6 tree
This is a note to let you know that I've just added the patch titled
Subject: USB: gadget webcam: depends on VIDEO_DEV
to my gregkh-2.6 tree. Its filename is
usb-gadget-webcam-depends-on-video_dev.patch
This tree can be found at
http://www.kernel.org/pub/linux/kernel/people/gregkh/gregkh-2.6/patches/
Quoted 1 line
From [email protected] Wed May 5 16:12:11 2010
From: Randy Dunlap <[email protected]>
Date: Wed, 5 May 2010 15:46:26 -0700
Subject: USB: gadget webcam: depends on VIDEO_DEV
To: Stephen Rothwell <[email protected]>, lud <[email protected]>
Cc: [email protected], LKML <[email protected]>, David Brownell <[email protected]>, [email protected]
Message-ID: <[email protected]>
From: Randy Dunlap <[email protected]>
g_webcam uses v4l[2] interfaces, so it should depend on VIDEO_DEV.
ERROR: "v4l2_event_unsubscribe" [drivers/usb/gadget/g_webcam.ko] undefined!
ERROR: "v4l2_event_queue" [drivers/usb/gadget/g_webcam.ko] undefined!
ERROR: "video_device_release" [drivers/usb/gadget/g_webcam.ko] undefined!
ERROR: "video_usercopy" [drivers/usb/gadget/g_webcam.ko] undefined!
ERROR: "v4l2_event_dequeue" [drivers/usb/gadget/g_webcam.ko] undefined!
ERROR: "video_register_device" [drivers/usb/gadget/g_webcam.ko] undefined!
ERROR: "video_device_alloc" [drivers/usb/gadget/g_webcam.ko] undefined!
ERROR: "v4l2_event_subscribe" [drivers/usb/gadget/g_webcam.ko] undefined!
ERROR: "video_unregister_device" [drivers/usb/gadget/g_webcam.ko] ndefined!
ERROR: "v4l2_event_pending" [drivers/usb/gadget/g_webcam.ko] undefined!
ERROR: "v4l2_fh_init" [drivers/usb/gadget/g_webcam.ko] undefined!
ERROR: "v4l2_event_init" [drivers/usb/gadget/g_webcam.ko] undefined!
ERROR: "video_devdata" [drivers/usb/gadget/g_webcam.ko] undefined!
ERROR: "v4l2_event_alloc" [drivers/usb/gadget/g_webcam.ko] undefined!
ERROR: "v4l2_fh_add" [drivers/usb/gadget/g_webcam.ko] undefined!
ERROR: "v4l2_fh_del" [drivers/usb/gadget/g_webcam.ko] undefined!
ERROR: "v4l2_fh_exit" [drivers/usb/gadget/g_webcam.ko] undefined!
--- drivers/usb/gadget/Kconfig | 1 + 1 file changed, 1 insertion(+)
drivers/usb/gadget/Kconfig +1 -0
@@ -879,6 +879,7 @@ config USB_G_HID # or video class gadget drivers), or specific hardware, here. config USB_G_WEBCAM tristate "USB Webcam Gadget" + depends on VIDEO_DEV help The Webcam Gadget acts as a composite USB Audio and Video Class device. It provides a userspace API to process UVC control requests
Re: [PATCH -next] usb gadget webcam: depends on VIDEO_DEV
In reply to Randy DunlapHi Randy,
Quoted 13 lines · On Thursday 06 May 2010 00:46:26 Randy Dunlap wrote:
From: Randy Dunlap <[email protected]>
g_webcamuses v4l[2] interfaces, so it should depend onVIDEO_DEV.ERROR: "
v4l2_event_unsubscribe" [drivers/usb/gadget/g_webcam.ko] undefined!
ERROR: "v4l2_event_queue" [drivers/usb/gadget/g_webcam.ko] undefined!
ERROR: "video_device_release" [drivers/usb/gadget/g_webcam.ko] undefined!
ERROR: "video_usercopy" [drivers/usb/gadget/g_webcam.ko] undefined!
ERROR: "v4l2_event_dequeue" [drivers/usb/gadget/g_webcam.ko] undefined!
ERROR: "video_register_device" [drivers/usb/gadget/g_webcam.ko] undefined!
ERROR: "video_device_alloc" [drivers/usb/gadget/g_webcam.ko] undefined!
ERROR: "v4l2_event_subscribe" [drivers/usb/gadget/g_webcam.ko] undefined!
ERROR: "video_unregister_device" [drivers/usb/gadget/g_webcam.ko] ndefined!
Quoted 8 lines
ERROR: "
v4l2_event_pending" [drivers/usb/gadget/g_webcam.ko] undefined!
ERROR: "v4l2_fh_init" [drivers/usb/gadget/g_webcam.ko] undefined!
ERROR: "v4l2_event_init" [drivers/usb/gadget/g_webcam.ko] undefined!
ERROR: "video_devdata" [drivers/usb/gadget/g_webcam.ko] undefined!
ERROR: "v4l2_event_alloc" [drivers/usb/gadget/g_webcam.ko] undefined!
ERROR: "v4l2_fh_add" [drivers/usb/gadget/g_webcam.ko] undefined!
ERROR: "v4l2_fh_del" [drivers/usb/gadget/g_webcam.ko] undefined!
ERROR: "v4l2_fh_exit" [drivers/usb/gadget/g_webcam.ko] undefined!
Oops, my bad. Thanks for the patch.
Quoted 1 line
Signed-off-by Randy Dunlap <[email protected]>
Signature · 3 lines
Regards, Laurent Pinchart
PATCH 1/1 staging/rar_register: depends on PCI
In reply to Stephen RothwellFrom: Randy Dunlap <[email protected]>
rar_register driver uses PCI interfaces and PCI devices, so it should depend on PCI.
Also format the Kconfig help text as normally done.
drivers/staging/rar_register/rar_register.c:623: error: implicit declaration of function 'pci_dev_get' drivers/staging/rar_register/rar_register.c:623: warning: assignment makes pointer from integer without a cast
Note: The memrar driver selects this driver's Kconfig symbol, even when PCI is not enabled. That select could be changed to
select RAR_REGISTER if PCI
but that would still result in build errors when PCI is not enabled, namely:drivers/built-in.o: In function `memrar_fini_rar_resources':
memrar_handler.c:(.text+0x2391b7): undefined reference to unregister_rar' drivers/built-in.o: In function memrar_registration_callback':
memrar_handler.c:(.text+0x23925a): undefined reference to rar_get_address' drivers/built-in.o: In function memrar_init':
memrar_handler.c:(.init.text+0x12c7b): undefined reference to register_rar' memrar_handler.c:(.init.text+0x12c97): undefined reference to register_rar'
Does anyone have suggestions for this?
--- drivers/staging/rar_register/Kconfig | 28 ++++++++++++------------- 1 file changed, 14 insertions(+), 14 deletions(-)
drivers/staging/rar_register/Kconfig +14 -14
@@ -8,23 +8,23 @@ menu "RAR Register Driver" # config RAR_REGISTER tristate "Restricted Access Region Register Driver" + depends on PCI default n ---help--- - This driver allows other kernel drivers access to the - contents of the restricted access region control - registers. + This driver allows other kernel drivers access to the + contents of the restricted access region control registers. - The restricted access region control registers - (rar_registers) are used to pass address and - locking information on restricted access regions - to other drivers that use restricted access regions + The restricted access region control registers + (rar_registers) are used to pass address and + locking information on restricted access regions + to other drivers that use restricted access regions. - The restricted access regions are regions of memory - on the Intel MID Platform that are not accessible to - the x86 processor, but are accessible to dedicated - processors on board peripheral devices. + The restricted access regions are regions of memory + on the Intel MID Platform that are not accessible to + the x86 processor, but are accessible to dedicated + processors on board peripheral devices. - The purpose of the restricted access regions is to - protect sensitive data from compromise by unauthorized - programs running on the x86 processor. + The purpose of the restricted access regions is to + protect sensitive data from compromise by unauthorized + programs running on the x86 processor. endmenu
Re: [PATCH -next] staging/rar_register: depends on PCI
Quoted 22 lines · On Wed, 5 May 2010 15:45:22 -0700 Randy Dunlap <[email protected]> wrote:
From: Randy Dunlap <[email protected]>
rar_registerdriver uses PCI interfaces and PCI devices, so it should depend on PCI.Also format the
Kconfighelp text as normally done.
drivers/staging/rar_register/rar_register.c:623: error: implicit declaration of function 'pci_dev_get'drivers/staging/rar_register/rar_register.c:623: warning: assignment makes pointer from integer without a castNote: The memrar driver selects this driver's
Kconfigsymbol, even when PCI is not enabled. That select could be changed to
selectRAR_REGISTERif PCI
but that would still result in build errors when PCI is not enabled, namely:drivers/built-in.o: In function `memrar_fini_rar_resources':
memrar_handler.c:(.text+0x2391b7): undefined reference tounregister_rar' drivers/built-in.o: In functionmemrar_registration_callback':
memrar_handler.c:(.text+0x23925a): undefined reference torar_get_address' drivers/built-in.o: In functionmemrar_init':
memrar_handler.c:(.init.text+0x12c7b): undefined reference toregister_rar' memrar_handler.c:(.init.text+0x12c97): undefined reference toregister_rar'
Quoted 1 line
Does anyone have suggestions for this?
Yes - memrar should depend upon the RAR_REGISTER
Quoted 2 lines
Signed-off-by Randy Dunlap <[email protected]>
Re: [PATCH -next] staging/rar_register: depends on PCI
Quoted 25 lines · Alan Cox
Quoted 22 lines · On Wed, 5 May 2010 15:45:22 -0700 Randy Dunlap <[email protected]> wrote:
From: Randy Dunlap <[email protected]>
rar_registerdriver uses PCI interfaces and PCI devices, so it should depend on PCI.Also format the
Kconfighelp text as normally done.
drivers/staging/rar_register/rar_register.c:623: error: implicit declaration of function 'pci_dev_get'drivers/staging/rar_register/rar_register.c:623: warning: assignment makes pointer from integer without a castNote: The memrar driver selects this driver's
Kconfigsymbol, even when PCI is not enabled. That select could be changed to
selectRAR_REGISTERif PCI
but that would still result in build errors when PCI is not enabled, namely:drivers/built-in.o: In function `memrar_fini_rar_resources':
memrar_handler.c:(.text+0x2391b7): undefined reference tounregister_rar' drivers/built-in.o: In functionmemrar_registration_callback':
memrar_handler.c:(.text+0x23925a): undefined reference torar_get_address' drivers/built-in.o: In functionmemrar_init':
memrar_handler.c:(.init.text+0x12c7b): undefined reference toregister_rar' memrar_handler.c:(.init.text+0x12c97): undefined reference toregister_rar'
Quoted 3 lines
Quoted 1 line
Does anyone have suggestions for this?
Yes - memrar should depend upon the
RAR_REGISTER
memrar currently selects RAR_REGISTER, but I'll be happy to change that to depends on...
Signature · 2 lines
~Randy *** Remember to use Documentation/SubmitChecklist when testing your code ***