<krzk>
That's great idea, but that patchset is 2 months old, there were no new versions, and it does not even apply
<krzk>
So I do not see any reasonable way how I can rebase both on newest tree and on that patchset. Second issue is that such dependency on unreviewed/unmerged patchset makes sm8750 also non-mergeable in any reasonable feature
srinik has quit [Remote host closed the connection]
srinik has joined #linux-msm
<krzk>
but still the first thing is the problem - no way to rebase it :/
mripard_ has joined #linux-msm
mripard has quit [Ping timeout: 480 seconds]
ungeskriptet_ has joined #linux-msm
ungeskriptet has quit [Ping timeout: 480 seconds]
ungeskriptet_ is now known as ungeskriptet
mripard has joined #linux-msm
mripard_ has quit [Ping timeout: 480 seconds]
srinik has quit [Ping timeout: 480 seconds]
zstas_ has quit [Ping timeout: 480 seconds]
jnn is now known as jn
pespin has quit [Remote host closed the connection]
<abhinav__>
krzk there are some open items on that series - on my side to finish reviews but also discuss the open items of moving away from feature bits which i wrote here https://lore.kernel.org/all/7dc1f356-b1e0-4bca-bfb9-8de3717407bc@quicinc.com/ , i am especially unsure of using just < for some of the patches, there will certainly be other chipsets which
<abhinav__>
might not even have some of the hw blocks so we will need >= and < everywhere .... if sm8750 dpu side changes are targetted for this cycle, IMO we shouldnt block on feature bits removal and just go ahead and post it on top of current msm-next, lumag WDYT
srinik has joined #linux-msm
jhovold has quit [Ping timeout: 480 seconds]
srinik has quit [Remote host closed the connection]