ChanServ changed the topic of #dri-devel to: <ajax> nothing involved with X should ever be unable to find a bar
mbrost_ has joined #dri-devel
hays has quit [Remote host closed the connection]
hays has joined #dri-devel
mbrost_ has quit []
rcf has quit [Quit: WeeChat 3.4.1]
YuGiOhJCJ has joined #dri-devel
<zmike>
DavidHeidelberg[m]: I think today might be the last day that zink dominates the ci fail charts
<DavidHeidelberg[m]>
zmike: 🎊
rcf has joined #dri-devel
<HdkR>
zmike: Zink is finally going to lose at something?
<HdkR>
What is this reality?
sarnex has quit [Ping timeout: 480 seconds]
sarnex has joined #dri-devel
<daniels>
zmike: don't talk yourself down like that, you can get right back to the top of the charts in no time
<zmike>
daniels: thanks, that's the kind of pep talk I needed to motivate myself into adding even more subtle flakes to fail merge jobs
rcf has quit [Quit: WeeChat 3.4.1]
rcf has joined #dri-devel
yuq825 has joined #dri-devel
mbrost has joined #dri-devel
ioldoortdddddeotm^ has quit [Remote host closed the connection]
co1umbarius has joined #dri-devel
columbarius has quit [Ping timeout: 480 seconds]
mbrost has quit [Ping timeout: 480 seconds]
shoragan has quit [Quit: quit]
Zopolis4 has joined #dri-devel
Danct12 has joined #dri-devel
mbrost has joined #dri-devel
rcf has quit [Quit: WeeChat 3.8]
mbrost has quit [Remote host closed the connection]
mbrost has joined #dri-devel
rcf has joined #dri-devel
mbrost has quit [Remote host closed the connection]
mbrost has joined #dri-devel
aravind has joined #dri-devel
yuq825 has quit []
bmodem has joined #dri-devel
YuGiOhJCJ has quit [Quit: YuGiOhJCJ]
Danct12 has quit [Remote host closed the connection]
Danct12 has joined #dri-devel
heat has quit [Ping timeout: 480 seconds]
bgs has quit [Remote host closed the connection]
lemonzest has quit [Quit: WeeChat 3.6]
lemonzest has joined #dri-devel
Zopolis4 has quit []
Danct12 has quit [Quit: WeeChat 3.8]
mbrost_ has joined #dri-devel
mbrost has quit [Read error: Connection reset by peer]
mbrost_ has quit [Remote host closed the connection]
kts has joined #dri-devel
mbrost_ has joined #dri-devel
kts has quit []
mbrost_ has quit [Read error: Connection reset by peer]
mbrost has joined #dri-devel
kts has joined #dri-devel
mbrost has quit [Read error: Connection reset by peer]
godvino has joined #dri-devel
dsrt^ has joined #dri-devel
yuq825 has joined #dri-devel
Company has quit [Quit: Leaving]
rcf has quit [Quit: WeeChat 3.8]
kzd has quit [Ping timeout: 480 seconds]
hansg has joined #dri-devel
rcf has joined #dri-devel
djbw has quit [Read error: Connection reset by peer]
a-865 has quit [Ping timeout: 480 seconds]
godvino has quit [Ping timeout: 480 seconds]
rmckeever has quit [Quit: Leaving]
danvet has joined #dri-devel
tzimmermann has joined #dri-devel
kts has quit [Quit: Konversation terminated!]
a-865 has joined #dri-devel
djbw has joined #dri-devel
Kayden has joined #dri-devel
fab has joined #dri-devel
sghuge has quit [Remote host closed the connection]
sghuge has joined #dri-devel
chipxxx has joined #dri-devel
chipxxx has quit [Remote host closed the connection]
godvino has joined #dri-devel
shoragan has joined #dri-devel
alanc has quit [Remote host closed the connection]
alanc has joined #dri-devel
dsrt^ has quit [Remote host closed the connection]
urja has quit [Ping timeout: 480 seconds]
sgruszka_ has joined #dri-devel
fab has quit [Quit: fab]
pochu has joined #dri-devel
tursulin has joined #dri-devel
ice9 has joined #dri-devel
fab has joined #dri-devel
godvino has quit [Quit: WeeChat 3.6]
<danvet>
mlankhorst, should we do backmerge dance after -rc4 because -misc-next is still on -rc1?
<danvet>
that's always a bit a wobbly one :-)
<danvet>
rodrigovivi, ^^ maybe intel-next needs that too?
hansg has quit [Quit: Leaving]
pcercuei has joined #dri-devel
lynxeye has joined #dri-devel
smilessh has quit [Ping timeout: 480 seconds]
Haaninjo has joined #dri-devel
hays has quit [Remote host closed the connection]
dtmrzgl has joined #dri-devel
Haaninjo has quit [Quit: Ex-Chat]
rosefromthedead has joined #dri-devel
apinheiro has joined #dri-devel
psykose has quit [Remote host closed the connection]
vliaskov has joined #dri-devel
Ahuj has joined #dri-devel
rasterman has joined #dri-devel
<danvet>
tzimmermann, mlankhorst, mripard: what's your thoughts on expanding the drm-misc MAINTAINER entry to essentially match drm?
<danvet>
would essentially officiate drm-misc's role as the fallback place
<danvet>
currently lost patches are stuck for a long time until it bubbles all the way to airlied&me
<danvet>
(for drivers at least)
<danvet>
but also doing that means you get a ton more mails
<danvet>
or well, cc'ed on a ton more mails
<danvet>
currently the file match tries to limit to just shared code
<danvet>
I think ideal would be if we auto-label lost patches after a month or so, but that's a level of semantics that a mailing list doesn't support
hays has joined #dri-devel
<danvet>
I think ideal would be if somehow drm-misc maintainers would get auto-added for every path that's listing drm-misc.git as the repo
<danvet>
and not for all of drm
<danvet>
so that the big driver trees like amd/intel/msm... aren't included
<danvet>
but I have no idea how that could work (except manually, which is just ... ugh)
<mripard>
danvet: on principle, I'm fine with it
<mripard>
I wonder if it's not going to have the opposite outcome if amd, intel and so on are added
<danvet>
mripard, yeah if the result is that you just get flooded like airlied&me and only look when the shouting is too loud, it's probably not useful
<mripard>
like I'm pretty sure I'll just archive most of those patches without even fully reading them because there's too many mails, and it doesn't look like something for drm-misc
<danvet>
yeah
<danvet>
limiting to only what's explicitly in drm-misc would cut down
<danvet>
but not in a really substantial amount
<mripard>
but there will probably be a lot of false negatives
<danvet>
in the end mailing lists for tracking submissions are just not great
<mripard>
does get_maintainer support blocklist?
<danvet>
like some bot that pings you when a timer runs out might work
<danvet>
blocklist?
<danvet>
oh negative entries you mean
<javierm>
danvet: there's a X: field in the MAINTAINERS file to exclude some paths
<mripard>
if so, we could just say for drm-misc we maintain everything but amd, intel and msm
<danvet>
mripard, yeah it has exclude patterns
<javierm>
so you could for example add a 'X: drivers/gpu/drm/amd/'
<mripard>
and whatever else we want to exclude
<mripard>
let's do this then
<danvet>
mripard, yeah that sounds good
<danvet>
that way even the trees which are nominally maintained, but not at the same level as these tree would be included
<danvet>
it's still a shit ton of mails though :-(
<danvet>
mripard, I guess up to you three whether you want to try or not
<danvet>
try as in sign up for this flood :-)
<danvet>
but with the X: patterns for the big driver subtrees it should be workable I guess
<mripard>
yeah well
<mripard>
we could also start to use patchwork
<mripard>
but I have the feeling it's just a different can of worms
<danvet>
yeah it is
<danvet>
the trouble is that you still have no one marking old stuff as deprecated
<danvet>
and it's out-of-line metadata too
<javierm>
danvet: I do for my patches btw :) we could enforce that
<javierm>
got used to that when contributed to media/v4l2 because they make proper use of patchwork
<danvet>
and there's not even basic stuff like tagging so could do some meaningful-ish searches
<danvet>
javierm, yeah I guess if people only pick up patches from pw it might work
<danvet>
but we have a ton of committers
<javierm>
danvet: yes, but we could integrate with dim
<javierm>
and mark as merged patches that matches the subject line for example
<danvet>
javierm, oh that happens already
<danvet>
server-side even
<danvet>
the trouble is when you revise patches and patchwork doesn't realize that it's superseeded on its own
<javierm>
oh, I didn't know that
<danvet>
or when you drop a patch set
<javierm>
danvet: yeah, there's some work that submitters would need to do to make sure that their own patch series are up-to-date
<javierm>
or delegate to someone to do the cleanup. I belive the latter is what v4l2 folks do
urja has joined #dri-devel
<danvet>
javierm, that tends to run into the "m-l is awesome because you don't need an account" argument
<javierm>
danvet: hmm...
<javierm>
any sentence that starts with "m-l is awesome..." probably isn't true anyways :)
<danvet>
and at that point we might as well just do gitforge mr :-)
<danvet>
but yeah, dunno
<danvet>
tbh I'm also ok with the continuing fine tradition of just dropping stuff on the floor
<danvet>
it's kinda what you get
<javierm>
yeah, specially since probably quite old patches won't apply cleanly anymore so at the very least needs a rebase and re-test
<mripard>
danvet: iirc, b4 can tag the patches it applies as such on pw
<danvet>
oh I'd say after a full release/quarter you just auto-close and wait for the rebase
<mripard>
we could just use b4 in dim, and every committer would use it.
<danvet>
mripard, it's not the patches that you apply, but the ones that are outdated/superseeded/invalid that clog the gears
<mripard>
ok
<danvet>
atm we just age them out after 2 weeks in reality
<danvet>
which is the same crack all the lost stuff disappears in
tagr_ is now known as tagr
<javierm>
I think 2 weeks is too soon btw, I always have to search on patchwork with archive=both
<tagr>
danvet: regarding that host1x fix, looks like Linus picked that up already a few days ago
<danvet>
oh
<danvet>
oh well it's in both trees now
<tagr>
sorry about that, I've had it in the for-next branch for Tegra for a while but forgot to send a PR
<tagr>
timing was a bit weird because I left during the merge window for a couple of weeks and then got back after -rc3
<tagr>
I should've just sent during the merge window
<tagr>
danvet: but like I said in the mail, it's probably best at this point to move Tegra to drm-misc fully, the overhead of the separate tree is no longer justifiable I think
<danvet>
tagr, yeah don't worry about this patch, we loose things through cracks fairly regularly
<danvet>
just good to ponder whether there's anything obvious we can do to do better
<danvet>
I think at least fixes in drm-misc is probably the obvious one to avoid patches lost in branches without a pr
<tagr>
yeah
<tagr>
to be honest, I'm a bit surprised how the original patch made it through in the first place because I do run build tests and this should've shown up
<tagr>
unless perhaps it's hidden behind some flag that I don't happen to enable
<tagr>
uninitialized variables really should be flagged by default, though
<danvet>
tagr, apparently it's clang that noticed it
<danvet>
and somehow gcc didn't
<tagr>
danvet: ugh...
<tagr>
guess I'm going to have to start doing builds with both then
JohnnyonFlame has quit [Ping timeout: 480 seconds]
smilessh has joined #dri-devel
aravind has quit [Ping timeout: 480 seconds]
kts has joined #dri-devel
psykose has joined #dri-devel
jdavies has joined #dri-devel
jdavies is now known as Guest8737
jdavies_ has joined #dri-devel
Guest8737 has quit [Ping timeout: 480 seconds]
bgs has joined #dri-devel
camus has quit []
jdavies_ has quit [Remote host closed the connection]
fab has quit [Quit: fab]
kts has quit [Quit: Konversation terminated!]
pochu has quit [Quit: leaving]
kzd has joined #dri-devel
fxkamd has quit []
fxkamd has joined #dri-devel
yuq825 has left #dri-devel [#dri-devel]
chipxxx has joined #dri-devel
chipxxx has quit [Remote host closed the connection]
chipxxx has joined #dri-devel
paulk-bis has joined #dri-devel
paulk has quit [Read error: Connection reset by peer]
gouchi has quit [Remote host closed the connection]
MoeIcenowy has joined #dri-devel
agneli has quit [Remote host closed the connection]
agneli has joined #dri-devel
Ahuj has quit [Ping timeout: 480 seconds]
Guest8656 is now known as ybogdano
dcbaker has joined #dri-devel
<dcbaker>
doras: that commit is specifically tagged as a fixing a commit in the 23.0 branch, but the other two commits are not.
<dcbaker>
I'd guess that this is a case where the previous commit always provoked an existing bug, but it was possible to hit regardless
<MrCooper>
doras: you're not authenticated with NickServ, so your messages aren't coming through to IRC
<dcbaker>
Also, PSA: I'm still very behind on releases, whatever I can get pulled into the staging/23.0 branch today (and green in CI) will be released tonight (PDT). There will likely be stuff tagged that will not be in this release, I apologize for how long it's taking
mbrost has quit [Ping timeout: 480 seconds]
lynxeye has quit [Quit: Leaving.]
paulk has quit [Ping timeout: 480 seconds]
paulk has joined #dri-devel
tzimmermann has quit [Quit: Leaving]
<doras>
Thanks MrCooper. I guess lack of SASL authentication in OFTC is making this harder than it needs to be.
mbrost has joined #dri-devel
<doras>
dcbaker: I mostly meant that "nir: use xyzw order for precise fdot" is marked with resolution "1" by the commit that I linked, but the relevant commit wasn't actually cherry-picked to `staging/23.0`.
<dcbaker>
doras: ah, I'll have to look to be sure, but I think it's causing regressions in the radv traces
<dcbaker>
hmm, yeah, that did get marked as commited even though it wasn't...