Re: [PATCH v2] usb: phy: don't mark usb_bind_phy as __init

2013-04-23 Thread Arnd Bergmann
On Tuesday 23 April 2013, Felipe Balbi wrote: > On Tue, Apr 23, 2013 at 09:07:21PM +0200, Arnd Bergmann wrote: > > It makes no sense for a symbol to be both exported and marked __init, > > because any users in modules would be calling this function after > > it gets discarded. Further, this patch r

Re: [PATCH v2] usb: phy: don't mark usb_bind_phy as __init

2013-04-23 Thread Felipe Balbi
On Tue, Apr 23, 2013 at 09:07:21PM +0200, Arnd Bergmann wrote: > It makes no sense for a symbol to be both exported and marked __init, > because any users in modules would be calling this function after > it gets discarded. Further, this patch revolves a section mismatch > warning from usbhs_init_p

[PATCH v2] usb: phy: don't mark usb_bind_phy as __init

2013-04-23 Thread Arnd Bergmann
It makes no sense for a symbol to be both exported and marked __init, because any users in modules would be calling this function after it gets discarded. Further, this patch revolves a section mismatch warning from usbhs_init_phys(), which is intentionally not marked __init: WARNING: vmlinux.o(.t