amitk has joined #linux-exynos
ssk has joined #linux-exynos
ssk has quit [Ping timeout: 264 seconds]
ssk has joined #linux-exynos
ssk has quit [Ping timeout: 248 seconds]
ssk has joined #linux-exynos
ssk has quit [Ping timeout: 250 seconds]
ssk has joined #linux-exynos
zombah has joined #linux-exynos
ssk has quit [Ping timeout: 250 seconds]
ssk has joined #linux-exynos
si1v3r has quit [Ping timeout: 256 seconds]
si1v3r has joined #linux-exynos
ssk has quit [Ping timeout: 245 seconds]
afaerber_ has joined #linux-exynos
afaerber has quit [Ping timeout: 246 seconds]
zombah has quit [Quit: Leaving]
amitk has quit [Quit: leaving]
zombah has joined #linux-exynos
<ojn> javier__: I bisected the fails overnight of pit/pi down to your commit "ARM: dts: Enable wifi power-on for exynos5250-snow"
<ojn> Oh, nevermind. this might not be the case, it's hitting different failures at different times int he bisect, because exynos is always so f*cking broken.
<si1v3r> ... /topic exynos is always so f*cking broken.
<si1v3r> It has been a very fun ride though. :)
<Wizzup> meh
<Wizzup> it's not too bad
<si1v3r> I just repeating in my head: It's not a 686....
<si1v3r> and I can't words today it seems. neat.
<javier__> ojn: I bisected to commit 6261b06de565 ("regulator: Defer lookup of supply to regulator_get")
<javier__> or rather, I was not able to reproduce it anymore with that commit reverted
<javier__> ojn: and yes, bisecting exynos is always painful due so many issues masking the one you want to track down :-(
<javier__> I'll continue digging at this tomorrow