<z3ntu>
then I can't really fix much upstream for you
<aka_[m]>
+ changing compats
<aka_[m]>
'+'
<z3ntu>
but 8939 looks to be affected I think.. they have an unusual apcs setup there though
<z3ntu>
8916 not because gcc uses xo_board, 8974 no gcc reference in apcs, 8939 probably as above, 8953 no gcc reference in apcs, 8976 neither upstream as above, 8994 no gcc reference in apcs
<z3ntu>
Anyone here with msm8939 who could test latest linux-next? ^
<bamse>
aka_[m]: switching to b4 is not required, but i'd highly recommend it...it removes a bunch of manual work and reduces the chance of making some common mistakes...
junari has quit [Ping timeout: 480 seconds]
<aka_[m]>
one of mistakes i cannot easily undone is me lol
<aka_[m]>
well whatever will wait till monday and we might see how v3 will go
<bamse>
aka_[m]: it does protect you from yourself in some cases at least ;)
<aka_[m]>
and do you configure b4 somehow?
<aka_[m]>
ok b4.docs.kernel.org says it tries to use sendmail git config
<aka_[m]>
to get stuff moved from old OS i guess i copy .gitconfig and .git-credentials?
<bamse>
sounds about right
<bamse>
alternatively there's a https-based path for b4, to avoid having to maintain smtp configuration
<DavidHeidelberg>
konradybcio: thanks! I looked at it, I think I can set it to reg 0x80000000 and memory@80000000 with 0 size (as some devices has 1 - 2 G)
<DavidHeidelberg>
so for the purpose of DTS warning it will be fine, otherwise no change