Ben noticed that the newly added printk in rsrc_nonstatic is a bit
misleading as the I/O and Memory ranges aren't really available behind
the PCMCIA socket, but the resource areas can be set up somewhere within
these ranges instead. So, clarify this printk.

Signed-off-by: Dominik Brodowski <linux@dominikbrodowski.net>

Index: 2.6.12-rc1/drivers/pcmcia/rsrc_nonstatic.c
===================================================================
--- 2.6.12-rc1.orig/drivers/pcmcia/rsrc_nonstatic.c	2005-03-27 09:52:37.000000000 +0200
+++ 2.6.12-rc1/drivers/pcmcia/rsrc_nonstatic.c	2005-03-27 17:45:00.000000000 +0200
@@ -787,7 +787,7 @@
 		if (res->flags & IORESOURCE_IO) {
 			if (res == &ioport_resource)
 				continue;
-			printk(KERN_INFO "pcmcia: I/O behind socket: 0x%lx - 0x%lx\n",
+			printk(KERN_INFO "pcmcia: parent PCI bridge I/O window: 0x%lx - 0x%lx\n",
 			       res->start, res->end);
 			if (!adjust_io(s, ADD_MANAGED_RESOURCE, res->start, res->end))
 				done |= IORESOURCE_IO;
@@ -797,7 +797,7 @@
 		if (res->flags & IORESOURCE_MEM) {
 			if (res == &iomem_resource)
 				continue;
-			printk(KERN_INFO "pcmcia: Memory behind socket: 0x%lx - 0x%lx\n",
+			printk(KERN_INFO "pcmcia: parent PCI bridge Memory window: 0x%lx - 0x%lx\n",
 			       res->start, res->end);
 			if (!adjust_memory(s, ADD_MANAGED_RESOURCE, res->start, res->end))
 				done |= IORESOURCE_MEM;