08:42 <konradybcio> fixed already

12:40 <flamingradian[m]> oh, must be out-of-date next

12:43 <flamingradian[m]> sorry to bother you

15:01 <aka_[m]> uh

15:02 <aka_[m]> why next is so weird

15:02 <aka_[m]> i tried to reapply patch on latest next

15:02 <aka_[m]> and seems like rpmpd moved into different directory

15:02 <aka_[m]> history says it was 07-14 while on 0724 it was not even there

15:02 <aka_[m]> seems like maintainers picked such patch

15:09 <Marijn[m]> That's how next works, commits get added, removed, and/or reworked all the time

15:09 <Marijn[m]> It is after all a temporary overview of what the next pull window may become

15:26 <aka_[m]> lumag: if i rebase patch with your r-b and it file changes its location should i drop rb or keep it?

18:07 <aka_[m]> Tooniis: is A530 also so sad lately?

18:18 <lumag> aka_[m], up to you If you feel that it changed significantly, then it might be better to drop it. If not, it's fine to keep the rb

18:19 <aka_[m]> ok its pretty much same

18:19 <aka_[m]> just driver went from soc->genpd

18:21 <Tooniis[m]> <aka_[m]> "Tooniis: is A530 also so sad..." <- always has been

18:21 <aka_[m]> well a530 is sad for quite long time already

18:21 <aka_[m]> indeed

18:21 <aka_[m]> some says noblit works okish

18:21 <aka_[m]> and software rendering

18:28 <Tooniis[m]> it's been somewhat usable with the extra ring buffers disabled

18:29 <Tooniis[m]> but then it spams kernel log with iommu errors because it wants to access 0x00000000 so bad

22:03 <lumag> Tooniis[m], aka_[m]: which kernel/workload is that? I have been testing code on a530 / msm8996.

22:04 <lumag> but not on the -next