Re: [PATCH] populate platform device at late init

2016-08-25 Thread Anshuman Gupta
>You should generally test with something not ancient, It has been tested with 4.7 kernel too, board was booted but it can not verified further as 4.7 vanilla kernel does not launched shell prompt with udoo board, well this can be done. >Sorry, but this approach is never going to be accepted.

Re: [PATCH] populate platform device at late init

2016-08-25 Thread Anshuman Gupta
>You should generally test with something not ancient, It has been tested with 4.7 kernel too, board was booted but it can not verified further as 4.7 vanilla kernel does not launched shell prompt with udoo board, well this can be done. >Sorry, but this approach is never going to be accepted.

Re: [PATCH] populate platform device at late init

2016-08-22 Thread kbuild test robot
Hi Anshuman, [auto build test ERROR on v4.8-rc2] [also build test ERROR on next-20160822] [cannot apply to glikely/devicetree/next] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] [Suggest to use git(>=2.9.0) format-patch --base= (or --base=auto

Re: [PATCH] populate platform device at late init

2016-08-22 Thread kbuild test robot
Hi Anshuman, [auto build test ERROR on v4.8-rc2] [also build test ERROR on next-20160822] [cannot apply to glikely/devicetree/next] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] [Suggest to use git(>=2.9.0) format-patch --base= (or --base=auto

Re: [PATCH] populate platform device at late init

2016-08-22 Thread kbuild test robot
Hi Anshuman, [auto build test ERROR on v4.8-rc2] [also build test ERROR on next-20160819] [cannot apply to glikely/devicetree/next] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] [Suggest to use git(>=2.9.0) format-patch --base= (or --base=auto

Re: [PATCH] populate platform device at late init

2016-08-22 Thread kbuild test robot
Hi Anshuman, [auto build test ERROR on v4.8-rc2] [also build test ERROR on next-20160819] [cannot apply to glikely/devicetree/next] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] [Suggest to use git(>=2.9.0) format-patch --base= (or --base=auto

[PATCH] populate platform device at late init

2016-08-18 Thread Anshuman Gupta
This patch enables to populate platform devices from device tree at late-init As of now linux kernel has late-init call infrastructure which make a driver/module init call at late-init.it is not specific to a platform device. This patch make a platform device to be probe at late-init, without

[PATCH] populate platform device at late init

2016-08-18 Thread Anshuman Gupta
This patch enables to populate platform devices from device tree at late-init As of now linux kernel has late-init call infrastructure which make a driver/module init call at late-init.it is not specific to a platform device. This patch make a platform device to be probe at late-init, without

Re: [PATCH] populate platform device at late init

2016-08-18 Thread Rob Herring
On Thu, Aug 18, 2016 at 1:55 PM, Anshuman Gupta wrote: > This patch enables to populate platform devices from device tree at late-init > As of now linux kernel has late-init call infrastructure which make a > driver/module > init call at late-init.it is not specific to a

Re: [PATCH] populate platform device at late init

2016-08-18 Thread Rob Herring
On Thu, Aug 18, 2016 at 1:55 PM, Anshuman Gupta wrote: > This patch enables to populate platform devices from device tree at late-init > As of now linux kernel has late-init call infrastructure which make a > driver/module > init call at late-init.it is not specific to a platform device. > This