Re: [PATCH] Remove MODULE_ALIAS() calls that take undefined macro

2019-05-08 Thread Lee Jones
On Tue, 07 May 2019, Masahiro Yamada wrote: > These files do not define (USBHS_)DRIVER_NAME. Yet, they can be > successfully compiled because they are never built as a module by > anyone, i.e, the MODULE_ALIAS() calls are always no-op. > > A problem showed up when a patch "moduleparam: Save infor

Re: [PATCH] Remove MODULE_ALIAS() calls that take undefined macro

2019-05-06 Thread Tony Lindgren
* Daniel Lezcano [190506 17:40]: > On 06/05/2019 19:28, Masahiro Yamada wrote: > > These files do not define (USBHS_)DRIVER_NAME. Yet, they can be > > successfully compiled because they are never built as a module by > > anyone, i.e, the MODULE_ALIAS() calls are always no-op. > > > > A problem sh

Re: [PATCH] Remove MODULE_ALIAS() calls that take undefined macro

2019-05-06 Thread Daniel Lezcano
On 06/05/2019 19:28, Masahiro Yamada wrote: > These files do not define (USBHS_)DRIVER_NAME. Yet, they can be > successfully compiled because they are never built as a module by > anyone, i.e, the MODULE_ALIAS() calls are always no-op. > > A problem showed up when a patch "moduleparam: Save inform

[PATCH] Remove MODULE_ALIAS() calls that take undefined macro

2019-05-06 Thread Masahiro Yamada
These files do not define (USBHS_)DRIVER_NAME. Yet, they can be successfully compiled because they are never built as a module by anyone, i.e, the MODULE_ALIAS() calls are always no-op. A problem showed up when a patch "moduleparam: Save information about built-in modules in separate file" is appl