Is this a problem that we need to get resolved in .33, or older kernels,
or just for .34?
thanks,
greg k-h
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majo...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
This allows MFD's to register/bind drivers for their sub devices while
still being compiled as a module.
Signed-off-by: Michael Hennerich <michael....@analog.com>
Signed-off-by: Mike Frysinger <vap...@gentoo.org>
---
drivers/base/platform.c | 1 +
1 files changed, 1 insertions(+), 0 deletions(-)
diff --git a/drivers/base/platform.c b/drivers/base/platform.c
index 9d2ee25..58efaf2 100644
--- a/drivers/base/platform.c
+++ b/drivers/base/platform.c
@@ -441,6 +441,7 @@ error:
platform_device_put(pdev);
return ERR_PTR(retval);
}
+EXPORT_SYMBOL_GPL(platform_device_register_data);
static int platform_drv_probe(struct device *_dev)
{
--
1.6.5.4
the functionality is in place now, so it could be used in .33. but it
isnt that big of a deal to simply say the mfd core cant be built as a
module right now.
so, it'd be nice for .33, but if it's too much hassle, .34 is OK.
-mike
Ok, I'll queue it up for .33, as it keeps an in-kernel driver from
working properly now.
thanks,
greg k-h