Re: [PATCH] bus: arm-ccn: Fix module autoload

2017-02-09 Thread Javier Martinez Canillas
Hello Pawel, On 02/06/2017 10:05 AM, Pawel Moll wrote: > On Fri, 2017-02-03 at 18:31 -0300, Javier Martinez Canillas wrote: >> On 01/02/2017 10:02 AM, Javier Martinez Canillas wrote: >>> >>> If the driver is built as a module, autoload won't work because the module >>> alias information is not fil

Re: [PATCH] bus: arm-ccn: Fix module autoload

2017-02-06 Thread Pawel Moll
On Fri, 2017-02-03 at 18:31 -0300, Javier Martinez Canillas wrote: > On 01/02/2017 10:02 AM, 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 w

Re: [PATCH] bus: arm-ccn: Fix module autoload

2017-02-06 Thread Pawel Moll
On Fri, 2017-02-03 at 18:31 -0300, Javier Martinez Canillas wrote: > On 01/02/2017 10:02 AM, 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 wi

Re: [PATCH] bus: arm-ccn: Fix module autoload

2017-02-03 Thread Javier Martinez Canillas
Hello, On 01/02/2017 10:02 AM, 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 u

[PATCH] bus: arm-ccn: Fix module autoload

2017-01-02 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