Re: [PATCH] omap2: hsmmc: fix logic to call either omap_hsmmc_init or omap_hsmmc_late_init but not both

2017-09-19 Thread Tony Lindgren
* H. Nikolaus Schaller [170918 13:34]: > Hi Tony, > is still there on 4.14-rc1. Applying into omap-for-v4.14/fixes thanks. Tony

Re: [PATCH] omap2: hsmmc: fix logic to call either omap_hsmmc_init or omap_hsmmc_late_init but not both

2017-09-19 Thread Tony Lindgren
* H. Nikolaus Schaller [170918 13:34]: > Hi Tony, > is still there on 4.14-rc1. Applying into omap-for-v4.14/fixes thanks. Tony

Re: [PATCH] omap2: hsmmc: fix logic to call either omap_hsmmc_init or omap_hsmmc_late_init but not both

2017-09-18 Thread H. Nikolaus Schaller
Hi Tony, is still there on 4.14-rc1. BR, Nikolaus > Am 08.09.2017 um 21:15 schrieb H. Nikolaus Schaller : > > With 4.13 kernel I get this boot message: > > [1.051727] [ cut here ] > [1.051818] WARNING: CPU: 0 PID: 1 at fs/sysfs/dir.c:31 >

Re: [PATCH] omap2: hsmmc: fix logic to call either omap_hsmmc_init or omap_hsmmc_late_init but not both

2017-09-18 Thread H. Nikolaus Schaller
Hi Tony, is still there on 4.14-rc1. BR, Nikolaus > Am 08.09.2017 um 21:15 schrieb H. Nikolaus Schaller : > > With 4.13 kernel I get this boot message: > > [1.051727] [ cut here ] > [1.051818] WARNING: CPU: 0 PID: 1 at fs/sysfs/dir.c:31 >