Re: [PATCH 2/2] mmc: sdhci-of-at91: Fix module autoload

2016-10-21 Thread Ulf Hansson
On 17 October 2016 at 18:13, Javier Martinez Canillas wrote: > If the driver is built as a module, autoload won't work because the module > alias information is not filled. So user-space can't match the registered > device with the corresponding module. > > Export the module alias information usin

Re: [PATCH 2/2] mmc: sdhci-of-at91: Fix module autoload

2016-10-21 Thread Adrian Hunter
On 21/10/16 09:48, Ludovic Desroches wrote: > On Mon, Oct 17, 2016 at 01:13:45PM -0300, Javier Martinez Canillas wrote: >> If the driver is built as a module, autoload won't work because the module >> alias information is not filled. So user-space can't match the registered >> device with the corre

Re: [PATCH 2/2] mmc: sdhci-of-at91: Fix module autoload

2016-10-20 Thread Ludovic Desroches
On Mon, Oct 17, 2016 at 01:13:45PM -0300, Javier Martinez Canillas wrote: > If the driver is built as a module, autoload won't work because the module > alias information is not filled. So user-space can't match the registered > device with the corresponding module. > > Export the module alias inf

[PATCH 2/2] mmc: sdhci-of-at91: Fix module autoload

2016-10-17 Thread Javier Martinez Canillas
If the driver is built as a module, autoload won't work because the module alias information is not filled. So user-space can't match the registered device with the corresponding module. Export the module alias information using the MODULE_DEVICE_TABLE() macro. Before this patch: $ modinfo drive