ChanServ changed the topic of #linux-msm to:
marvin24 has joined #linux-msm
marvin24_ has quit [Ping timeout: 480 seconds]
cxl000_ has joined #linux-msm
cxl000 has quit [Ping timeout: 480 seconds]
cxl000_ has quit [Quit: Leaving]
cxl000 has joined #linux-msm
telent7 has joined #linux-msm
telent has quit [Read error: Connection reset by peer]
telent7 is now known as telent
<aka_[m]> noone able to provide any review for these?
<aka_[m]> i have run bindings check and its throw error at not existing interconnect driver, which is a case, but if its not there should i delete it and add it to yaml once interconnect provider is added?
<aka_[m]> but i cannot see any yaml having additons after initial submission
<aka_[m]> and i would like to 🐑 it asap
Daanct12 has quit [Ping timeout: 480 seconds]
telent7 has joined #linux-msm
telent has quit [Read error: Connection reset by peer]
telent7 is now known as telent
underpantsgnome[m] has quit []
<aka_[m]> nice, rob's dt-schema ci throw errors >_>.
<aka_[m]> Bindings_check succeed however >_>
<aka_[m]> maybe fact i base on next not rc
<aka_[m]> konradybcio i guess these notes also apply to your 6350 stuff
<aka_[m]> well, i will leave it for tomorrow so maybe i can get others to comment
<Mis012[m]> I mean... worst case it's probably better to have a subject that's over 80 chars than to leave out which SoC it's relating to? xD
<Mis012[m]> aka_: seems that's all indeed
<aka_[m]> well
<aka_[m]> i had it
<aka_[m]> in second line
<Mis012[m]> didn't look into why the bot complains, but I assume it's not needed
<aka_[m]> and it was cut off
<aka_[m]> will just make it shorter so it fits
<aka_[m]> but feedback from others would be good, because as you know when i send v2 there will be someone else finding something else wrong
<Mis012[m]> well, better than having noone reply to you for a month...
<Mis012[m]> just sayin'
<Mis012[m]> actionable nitpicks are fine
anholt_ has quit [Ping timeout: 480 seconds]
mal has quit [Ping timeout: 480 seconds]
mal has joined #linux-msm