ChanServ changed the topic of #dri-devel to: <ajax> nothing involved with X should ever be unable to find a bar
Leopold_ has quit [Remote host closed the connection]
Leopold_ has joined #dri-devel
flynnjiang has joined #dri-devel
<abhinav__>
mlankhorst hi, for msm, we need some changes which went into drm-misc for a feature which we planned to land in 6.9 ... would it be possible to generate another tag so that we can pull in that into our tree and base our changes on that ...
<abhinav__>
these changes were merged after the last tag on 02-22
Hilligans has joined #dri-devel
Company has quit [Quit: Leaving]
co1umbarius has joined #dri-devel
columbarius has quit [Ping timeout: 480 seconds]
<Hilligans>
Hello
bolson has quit [Ping timeout: 480 seconds]
<Hilligans>
Ive come accross a very specific issue that I need help diagnosing
<Hilligans>
I'm working on my own engine currently thats using opengl as the backend that works fine on its own, but when I try to launch it via renderdoc I get a segfault in the driver.
<Hilligans>
I then compiled mesa on my system with debug symbols enabled and ran renderdoc via gdb to find the exact line causing the segfault, which is
<Hilligans>
I don't really know where to go from here and I dont really know where the issue lies or what piece of code is at fault for it so any tips or things I should do would be great.
Jeremy_Rand_Talos_ has quit [Remote host closed the connection]
Jeremy_Rand_Talos_ has joined #dri-devel
<kisak>
failing everything else, you could ask the renderdoc dev(s) if it makes sense to thm or if they've seen similar
<Hilligans>
thats true ill do that
<airlied>
probably useful to get a proper backtrace
<sima>
it's just around -rc6 it should be all sorted and at least the pr out so there's enough time to merge and shake things out before the merge window opens
<sima>
since by then it should be all ready
<sima>
this also because iirc some subtrees aren't in linux-next
<tzimmermann>
i see. i thought that we have reached -rc6 and only fixes should go into drm-next.
<sima>
although we've tried to get that fixed
<sima>
tzimmermann, always some judgement calls
<sima>
imo the important one is that drm-misc-next is always open for patches, so that people don't feel like they have to rush in patches due to a 1 month long no-merge window
<sima>
which most other subsystems have, and that part imo sucks for contributors
<tzimmermann>
makes sense; got it
<sima>
anyway I'll go pr processing, I'll ping you when it's done including -rc6 backmerge
<javierm>
sima: also, some ocasional may not be tracking the release process that closely and even know whether wer are in the -rc cycle or the merge window
<javierm>
*ocarionsal contributors
<tzimmermann>
sima, BTW i've been doing quite a bit of fbdev work recently. i was wondering, should we merge the fbdev tree into drm-tip as well?
<sima>
javierm, yeah
<sima>
tzimmermann, so core fbdev is all officially in drm-misc, I've done the MAINTAINERS patch for that
* sima
checks
<tzimmermann>
yes
<javierm>
sima: yeah, but is a good point tzimmermann to prevent conflicts or at least detect it earlier
<sima>
lol fb_defio.c is officially maintained by some random arc fbdev driver person :-)
<sima>
prooooobably outdated
<sima>
tzimmermann, for anything else I'd say drm-misc is also ok, especially if it's any kind of refactoring
<sima>
or one of the fw drivers we care about still
<tzimmermann>
quite a lot of driver patches go through helge's fbdev tree. i've been working on kernel graphics basics (such as sysfb) and htat naturally affects drm and fbdev. sometimes non-drm patchsets go into fbdev.git, even though they might affect drm as well
<sima>
if you want to be polite, maybe ask helge for an ack
<sima>
tzimmermann, yeah imo big refactorings just smash them all through drm-misc
<sima>
it's what the thing is there for
<sima>
I've pushed vt stuff through there too (but with gregkh's ack) in the past
<tzimmermann>
well, ok. i sometimes had to juggle some patches around until trees git sync'ed again.
<sima>
tzimmermann, tbf I give helge another 1-2 years before he gives up, that's usually how long fbdev volunteers stick around
<tzimmermann>
:D
<sima>
tzimmermann, yeah for anything cross-tree just ask for ack and land in drm-misc
<sima>
I made it pretty clear to helge that I don't see the point of a separate tree and invited him to drm-misc, and agreement is that he won't interfere
<sima>
so if the separate tree intereferes, just land it all through drm-misc
<tzimmermann>
helge mostly collects patches, it's mostly not much of a problem
<tzimmermann>
maybe i make a patch for the drm-tip repo and post it to the lists
itoral_ has joined #dri-devel
<sima>
airlied, just noticed that tzimmermann -next pull is after the amdgpu one, just lore websearch lists them the other way round somehow
lynxeye has joined #dri-devel
itoral has quit [Ping timeout: 480 seconds]
<marex>
sima: about that ^ xe error message , I hope I didn't break drm-misc-next ?
<sima>
marex, which xe error message?
<marex>
I was just pushing $ dim push-branch drm-misc-next and got this
<marex>
did I miss anything or screw anything up ?
<marex>
sima: ^ this
<sima>
hm I thought dim would ask you to auto-add in that case ...
<sima>
did it not?
<marex>
Enter a name to auto-add this remote, leave blank to abort: drm-xe
<marex>
ah ... I missed that one
<marex>
so, all is fine ?
<sima>
yeah so if you hit enter and it continued, it should be all fine
<sima>
otherwise you'll hit this again, and drm-tip won't be updated
<marex>
well, whew, that is good news, thanks
<sima>
marex, if you want to check, make sure your drm-tip was pushed
<marex>
it was
<sima>
then you're all good
<marex>
sima: I was concerned it might have been pushed somehow incorrectly, but it seems OK
<marex>
sima: thanks
qflex has joined #dri-devel
mripard has joined #dri-devel
vliaskov has joined #dri-devel
bmodem has quit [Ping timeout: 480 seconds]
kts_ has joined #dri-devel
jfalempe has joined #dri-devel
kts has quit [Ping timeout: 480 seconds]
<airlied>
sima: I only get PRs from patchwork mostly now, though I didn't get to process -next today like I should have
kxkamil has quit []
kts_ has quit [Ping timeout: 480 seconds]
jfalempe has quit [Remote host closed the connection]
jfalempe has joined #dri-devel
rasterman has joined #dri-devel
kxkamil has joined #dri-devel
Company has joined #dri-devel
rsalvaterra has quit []
rsalvaterra has joined #dri-devel
cmichael has joined #dri-devel
jsa has joined #dri-devel
surajkandpal has quit [Ping timeout: 480 seconds]
sgruszka has quit [Ping timeout: 480 seconds]
kts_ has joined #dri-devel
kts_ has quit [Ping timeout: 480 seconds]
<sima>
airlied, tzimmermann backmerge pushed
<sima>
demarchi, hwentlan_ drm-tip rerere sorted out some trivial stuff in xe and amdgpu, maybe check
cmichael has quit [Remote host closed the connection]
cmichael has joined #dri-devel
cmichael has quit []
jmondi has joined #dri-devel
<jmondi>
I very seldom send patches for drm/kms, and when I have to do so I constantly fail to remember which tree/branch I am supposed to develop patches against
<CounterPillow>
Judging by "base-commit:" in some of the submitted patchsets to the dri-devel mailing list, you'll want drm-tip https://cgit.freedesktop.org/drm-tip/
<CounterPillow>
Though if you're submitting patchset for a specific large-ish driver like those of intel or amd, they might have their own driver specific -next repositories, but if they want you to rebase on those they'll tell you when you submit
<jmondi>
it's just about adding a new image format to the uAPI
<mripard>
jmondi: yeah, generally speaking we follow pretty much the same pattern: latest release unless being told otherwise?
<jmondi>
mripard: of drm-misc ? or just drm ?
<mripard>
of linux? drm-misc or drm doesn't do releases
<jmondi>
linux yes
<jmondi>
or linux-next ?
<jmondi>
is this documented somewhere and I have missed it ?
<javierm>
jmondi: yeah, I usually use linux-next for my kernel work when I don't know what is the correct tree / branch to target
<CounterPillow>
"Note, however, that you may not want to develop against the mainline tree directly. Most subsystem maintainers run their own trees and want to see patches prepared against those trees. See the T: entry for the subsystem in the MAINTAINERS file to find that tree, or simply ask the maintainer if the tree is not listed there."
<CounterPillow>
run ./scripts/get_maintainer.pl --scm fileyou'remodifyinghere
<jmondi>
for DRM DRIVERS in MAINTAINERS
<mripard>
jmondi: really, just use the latest linux release and start from there. Just like you would for v4l2 :)
<CounterPillow>
./scripts/get_maintainer.pl --scm include/drm/drm_fourcc.h shows git git://anongit.freedesktop.org/drm/drm-misc as the first tree
<javierm>
jmondi: answering your question, for drm in particular I use drm-misc-next if is a new feature for the next release or drm-misc-fixes if is a fix for the currenty -rc cycle
<CounterPillow>
as you can tell by the multitude of answers, it really doesn't matter as long as it is recent
<CounterPillow>
if you get it wrong according to the maintainer, a rebase is easy, and you get to tell the maintainer to update the T: in MAINTAINERS then
kts_ has joined #dri-devel
kts_ has quit []
<jmondi>
mripard: for v4l2 I use the staging tree :) I thought it was documented in the maintainer-entry-profile file, but it's not
<jmondi>
will use -next, thank you all fro your answers
<javierm>
jmondi: for v4l2 I use -next btw :)
loki_val has quit []
<mripard>
sima: we had a discussion with emersion last week and I couldn't remember (or find it in the doc), are drm-misc committers supposed to cherry-pick, or only maintainers should?
<jmondi>
javierm: I guess 'whatever works' is the right way of doing it ;)
<emersion>
sima: hope you got back from your trip with less trouble than last time :P
<javierm>
jmondi: yeah :)
<emersion>
re cherry-pick: the question is about what committers are supposed to do when they messed up
<emersion>
and pushed to the -next tree instead of the -fixes tree
<javierm>
sima: yeah, something like this after the COMMANDS FOR MAINTAINERS "NOTE:
<sima>
reason is that cherry-picks tend to cause conflicts, so usually need to make maintainers aware anyway
<javierm>
ups, press enter too son. "NOTE: the following commands are for drm-misc maintainers and should not be used by people with drm-misc commit rights"
<emersion>
i see
<sima>
javierm, well those are for maintainers in general, I'd just add something to the drm-misc committer docs specifically
<emersion>
so i should've asked for a maintainer to do the cherry-pick, is the answer
<sima>
general = drm-intel and xe and all those trees
<emersion>
indeed the cherry-picked caused a conflict which i had to resolve
<emersion>
pick*
<mripard>
sima: yeah, that was my recollection too but it wasn't in the doc so I got confused
<sima>
yeah, they do that :-)
<mripard>
I'll send a doc patch
crabbedhaloablut has joined #dri-devel
<emersion>
ty!
<sima>
mripard, yeah I think the last time around we discussed this it got way too heated in private and everyone just wanted to settle it all for good :-/
<javierm>
mripard: that would be great. Thanks!
<javierm>
sima: now that you mention, is the first time I notice that the dim commands had sections for contributors and maintainers
<sima>
javierm, writing actually good docs that get the point across is hard ...
kts_ has joined #dri-devel
kts_ has quit [Remote host closed the connection]
<javierm>
sima: agreed. Sorry if it sounded as if I was complaining, I just meant that is nice that mripard will clarify even more, to prevent us contributors to make mistakes
<javierm>
because in the past I did cherry-pick and pushed, thinking that it was something that contributors were supposed to handle
kts has quit [Ping timeout: 480 seconds]
<sima>
javierm, yeah it's not one of the things which reliably results in pain, but it can, so we didn't yet get around to clarifying this properly
<sima>
but it also has lead to some serious pain in the past
<sima>
it's one of these "it's complicated" topics
<javierm>
sima: yeah
jkrzyszt has joined #dri-devel
Calandracas_ has joined #dri-devel
Calandracas has quit [Ping timeout: 480 seconds]
Calandracas_ has quit [Remote host closed the connection]
<sima>
mripard, also the licensing issues for built-in fw is when you don't allow redistribution
<sima>
since we allow these as built-in already (but in other form) that shouldn't be an issue
<sima>
so it's not a general restriction for fw, it's just that most fw has proprietary licensing making it impossible to include in the gpl'ed kernel binary in any form
<sima>
which is why fw-in-C-file-constants got removed from the kernel, it doesn't matter in which form you include these binaries if licensing is incompatible
<sima>
s/redistribution/have open source source that's gpl compatible/
<mripard>
oh, right
cmichael has quit []
cmichael has joined #dri-devel
junaid has quit [Remote host closed the connection]
itoral_ has quit [Remote host closed the connection]
fab has quit [Quit: fab]
fab has joined #dri-devel
junaid has joined #dri-devel
junaid has quit [Remote host closed the connection]
minecrell has quit [Quit: Ping timeout (120 seconds)]
minecrell has joined #dri-devel
agd5f has joined #dri-devel
glennk has quit [Ping timeout: 480 seconds]
alyssa has joined #dri-devel
<sima>
mripard, lgtm but maybe get acks from tzimmermann or mlankhorst?
<tzimmermann>
mripard, ack
<sima>
mripard, -fixes stuck on -rc1 I just noticed ...
<demarchi>
sima: is git:// preferred for the pull request or could we just switch globally to https:// ?
<sima>
I thought https was less efficient than git ...
<sima>
or is that outdated info?
<demarchi>
sima: asking because we don't have a git:// one for xe. I ended up using ssh:// with a local change to get the pull request done, but after checking the email I see it was not really ideal
<demarchi>
sima: shouldn't matter these days and git:// is disabled now in several forges
<mripard>
sima: I'll update drm-misc-fixes
<demarchi>
I know github disabled it completely, need to check if gitlab disabled it too
<mripard>
sima: and also, I can't merge a branch in maintainer-tools :)
<sima>
mripard, pls ping me when you're done since I'm in the process of applying a patch
<sima>
mripard, uh
<sima>
demarchi, can you press the button for mripard? my ubikey is somewhere but not where it should be rn ...
<DemiMarie>
demarchi: git:// is deprecated and hilariously insecure
<demarchi>
we are having a problem running pipelines from forked repos, so I can't merge neither
<mripard>
demarchi, sima: thanks!
<demarchi>
mripard: can you just push? the pipeline will just timeout and not run
<mripard>
I'm not sure I have the rights to, but I'll try
<demarchi>
mripard: I can push it if you don´t
<sima>
demarchi, I guess we need to move drm-misc and get everyone there added to the fdo-ci group so ci works?
<demarchi>
nonetheless we should fix the pipeline integration. Not sure if related, but we shouldn't really be using a container with fedora 28 for that
<sima>
oh lol
<sima>
it's been a while I've done the the dim ci :-)
<sima>
demarchi, xe committers should also get added to the fdo ci group, if they aren't yet
<demarchi>
sima: what do you mean by moving drm-misc?
<sima>
from legacy git to gitlab.fd.o
<mripard>
demarchi: yeah, I'm not allowed to push
<demarchi>
mripard: I will push that one for you
<mripard>
sima: I guess you didn't really watch your mails recently ? :)
<sima>
not sure, maybe should rebuild the images and move them over to fdo gitlab ci scripts
<sima>
mripard, for moving drm.git I guess just do it and then tell airlied&me
<sima>
as long as the mirror is there it shouldn't impact any in-flight pr to linus
<daniels>
yeah, that's because igt still isn't using the fd.o ci-templates, so it relies on either a) people running the container build themselves manually and pushing, or b) the person who submitted the MR to have rights to merge things to igt (since that causes the job to run in the project namespace rather than the user namespace)
<daniels>
sima: right, should be pretty straightforward
<sima>
daniels, also is that the one that people should fork?
bmodem has joined #dri-devel
<sima>
mripard, ^^
kts has quit [Ping timeout: 480 seconds]
YuGiOhJCJ has quit [Quit: YuGiOhJCJ]
<daniels>
sima: that's currently autosyncing from nowhere and up-to-date with nothing :)
<daniels>
but will eventually become the place you push and be mirrored out to anongit/drm/drm
<sima>
daniels, I'm just wondering why it's so up-to-date with last week :-)
<sima>
daniels, I guess if you have some time to disable write-access to the cgit drm.git somewhen I can then just shuffle it over
<daniels>
sima: oh yeah, because that's when we started creating all the stuff :P
<sima>
it's just a few pushes really
bmodem has quit [Ping timeout: 480 seconds]
<daniels>
sima: sure, can do that tomorrow
<sima>
I ditched a few branches from the cgit one, I'll drop them from the gitlab one too
<sima>
also just updated the description to hopefully steer people away from it aside from using it as a fork source
<sima>
daniels, btw on the gitlab fork tree, did you reparent all the random forks we have to drm/kernel already?
<sima>
since I guess that's the plan, or different again?
<sima>
or maybe more a question for bentiss on #freedesktop
<daniels>
sima: yeah, so the only thing I'd done with drm/kernel was to create it and start reparenting the forks; I got as far as breaking quite a few kernel forks before ETIME, and trying to get back to that hopefully tonight
<mripard>
sima: drm-misc-fixes is up-to-date
<sima>
daniels, aye
<sima>
daniels, airlied I've disabled issues and made merge requests members only, to avoid confusing people too badly
<sima>
mripard, yeah just noticed, thx
<mripard>
sima: so, if we were to migrate drm.git, when would be the best time?
<mripard>
I'd assume that during the merge window like for drm-misc is probably not great?
<sima>
mripard, tomorrow, if daniels has time :-)
<sima>
mripard, it's just two people plus telling linus that "btw it moved, don't freak out"
<sima>
we sign the tags anyway
<sima>
only thing that matters is that legacy git gets disabled so sfr and airlied don't miss it
<mripard>
sima: uh, ok
<mripard>
that works for me
<mripard>
daniels: ^ ?
<daniels>
yeah no prob
<daniels>
legacy git disabled or mirroring?
robmur01 has joined #dri-devel
<sima>
daniels, disabling writing is imo the important one, mirror is nice but not sure whether needed really
<sima>
mripard, oh I guess a really big MAINTAINERS patch is then also needed?
<mripard>
sima: our initial plan was to setup the cgit repo as a mirror, so it was needed but not urgent
<mripard>
but yeah, that's on the TODO list too
<sima>
mripard, yeah, simplest probably is if you base it on top of drm-next for all repo moves and then I just merge it directly
<mripard>
merge the MAINTAINERS patch you mean?
<sima>
yeah
<mripard>
ack
<sima>
demarchi, btw I guess you can delete drm/xe from the legacy git server?
<sima>
also not sure why the fw repo there is still in use when we have the new one
<demarchi>
sima: I'd remove the drm/xe from legacy git server if I knew how....
<demarchi>
sima: as for firmware... unfortunately it's still being used. I'm poking people updating that repo to stop and migrate to the new one
<sima>
demarchi, I think this needs server admin powers ... daniels?
<sima>
demarchi, also for fw repo you can just delete, that _will_ move the people :-)
<daniels>
demarchi: I can nuke it now if it helps
<demarchi>
sima: that's probably more effective than my method, although there will be drama and people yelling
<sima>
blame me, I'll take it :-)
<sima>
also, updating a git remote is a one-liner
<demarchi>
sima: there's also a process change
<sima>
demarchi, so if you ack, daniels can nuke drm-xe and drm-firmware from cgit
<sima>
demarchi, oh CI still looks at the old one?
<demarchi>
sima: yep
<sima>
ugh, then maybe mirroring is needed for drm-firmware :-/
<demarchi>
I´d just make it read-only
<sima>
demarchi, and force ci to update on the next fw push?
<demarchi>
then we don't lose the previous refs. But force people to migrate to the new one
<sima>
so delete drm-xe, make drm-firmware read-only?
<demarchi>
sima: yes.... we just merged the last firmwares we needed for the next release, so we probably have some time for people to adapt
<demarchi>
sima: ack
<sima>
mripard, ^^ maybe record that in your newly acquired 5yo issue :-)
<sima>
daniels, ^^
heat has quit [Remote host closed the connection]
heat has joined #dri-devel
<daniels>
done
<sima>
thx a bunch!
<mripard>
daniels: for both the drm-xe deletion and the drm-firmware being set as read-only?
<mripard>
(it's also not clear to me what the different between cgit.fd.o/drm/drm-firmware and gitlab.fd.o/drm/firmware is)
kzd has joined #dri-devel
<danylo>
scan_clusters.macro
<daniels>
mripard: yeah, both; I guess both repos are up-to-date now but there's no mirroring
<mripard>
daniels, sima: so, do we want to keep the old repo around in r/o or do we want to set it up as a mirror?
heat is now known as Guest1055
heat has joined #dri-devel
<sima>
mripard, imo r/o should be good enough for drm.git
<mripard>
I'm asking because igt and libdrm are setup as mirrors
<mripard>
and we probably want to be consistent
Guest1055 has quit [Read error: Connection reset by peer]
<sima>
yeah, but there's a lot more people using that with contributors and all that
<mripard>
ok
<sima>
otoh mirroring probably better for smooth transition
<sima>
and then just delete it
<sima>
I think once linus, srf and rerere/nightly.conf are all updated, everyone who matters should have moved
<sima>
*sfr
glennk has joined #dri-devel
tristianc6704 has quit []
balrog_ has quit []
tristianc6704 has joined #dri-devel
balrog has joined #dri-devel
u-amarsh04 has quit []
warpme has joined #dri-devel
<warpme>
guys: is current mesa (24.0.1) working out-of-box on rpi5 (v3d v7) with mainline 6.8-rc6?
<abhinav__>
tzimmermann mripard hi, for msm, we need some changes which went into drm-misc for a feature which we planned to land in 6.9 ... would it be possible to generate another tag so that we can pull in that into our tree and base our changes on that ... these changes were merged after the last tag on 02-22
aravind has quit [Ping timeout: 480 seconds]
u-amarsh04 has joined #dri-devel
gouchi has joined #dri-devel
gouchi has quit []
warpme has quit []
anujp has joined #dri-devel
hansg has joined #dri-devel
Duke`` has joined #dri-devel
bolson has joined #dri-devel
kts has joined #dri-devel
Haaninjo has joined #dri-devel
junaid has quit [Quit: Lost terminal]
simondnnsn has quit [Ping timeout: 480 seconds]
ninjaaaaa has quit [Ping timeout: 480 seconds]
junaid has joined #dri-devel
mdnavare__ has quit []
mdnavare__ has joined #dri-devel
mdnavare__ has quit []
mdnavare_ has joined #dri-devel
simondnnsn has joined #dri-devel
ninjaaaaa has joined #dri-devel
junaid has quit [Remote host closed the connection]
warpme has joined #dri-devel
cmichael has quit [Quit: Leaving]
guludo has joined #dri-devel
guludo has left #dri-devel [WeeChat 4.2.1]
guludo has joined #dri-devel
<bbrezillon>
mripard, sima: How would you feel about merging panthor in drm-misc-next (the underlying question being, when is the drm-misc-next MR for 6.9 supposed to happen, and do you think it'd be preferable to wait for 6.9-rc1 to land before merging the driver)?
<bbrezillon>
dliviu: ^
<bbrezillon>
as a side note, this is a new driver for unsupported HW, so no risk of regression here
ninjaaaaa has quit [Read error: Connection reset by peer]
simondnnsn has quit [Read error: Connection reset by peer]
ninjaaaaa has joined #dri-devel
simondnnsn has joined #dri-devel
fab has quit [Ping timeout: 480 seconds]
lynxeye has quit [Quit: Leaving.]
macromorgan_ has quit [Read error: Network is unreachable]
macromorgan_ has joined #dri-devel
tarceri_ has quit [Remote host closed the connection]
halves has quit [Quit: Ping timeout (120 seconds)]
tarceri_ has joined #dri-devel
KetilJohnsen has quit [Remote host closed the connection]
halves has joined #dri-devel
Shibe has quit []
Shibe has joined #dri-devel
aswar002 has quit [Remote host closed the connection]
KetilJohnsen has joined #dri-devel
aswar002 has joined #dri-devel
dviola has quit [Remote host closed the connection]
mattst88 has quit [Remote host closed the connection]
tzimmermann has quit [Quit: Leaving]
mattst88 has joined #dri-devel
a-865 has quit [Ping timeout: 480 seconds]
diego has joined #dri-devel
Jeremy_Rand_Talos__ has joined #dri-devel
ndufresne1 has joined #dri-devel
jkrzyszt_ has joined #dri-devel
nashpa has joined #dri-devel
fireburn_ has joined #dri-devel
tales-aparecida27 has joined #dri-devel
tarceri__ has joined #dri-devel
vals_ has joined #dri-devel
glennk has quit [charon.oftc.net helix.oftc.net]
heat has quit [charon.oftc.net helix.oftc.net]
robmur01 has quit [charon.oftc.net helix.oftc.net]
rasterman has quit [charon.oftc.net helix.oftc.net]
mripard has quit [charon.oftc.net helix.oftc.net]
krei-se- has quit [charon.oftc.net helix.oftc.net]
lemonzest has quit [charon.oftc.net helix.oftc.net]
Jeremy_Rand_Talos_ has quit [charon.oftc.net helix.oftc.net]
DavidHeidelberg has quit [charon.oftc.net helix.oftc.net]
fireburn has quit [charon.oftc.net helix.oftc.net]
tango_ has quit [charon.oftc.net helix.oftc.net]
DodoGTA has quit [charon.oftc.net helix.oftc.net]
dliviu has quit [charon.oftc.net helix.oftc.net]
tales-aparecida2 has quit [charon.oftc.net helix.oftc.net]
minecrell has quit [charon.oftc.net helix.oftc.net]
jkrzyszt has quit [charon.oftc.net helix.oftc.net]
cr0n has quit [charon.oftc.net helix.oftc.net]
danylo has quit [charon.oftc.net helix.oftc.net]
Stary has quit [charon.oftc.net helix.oftc.net]
qflex has quit [charon.oftc.net helix.oftc.net]
sravn has quit [charon.oftc.net helix.oftc.net]
q66 has quit [charon.oftc.net helix.oftc.net]
ndufresne has quit [charon.oftc.net helix.oftc.net]
paulk has quit [charon.oftc.net helix.oftc.net]
vyivel has quit [charon.oftc.net helix.oftc.net]
larunbe has quit [charon.oftc.net helix.oftc.net]
Omax has quit [charon.oftc.net helix.oftc.net]
mwalle has quit [charon.oftc.net helix.oftc.net]
jadahl has quit [charon.oftc.net helix.oftc.net]
pinchartl has quit [charon.oftc.net helix.oftc.net]
KunalAgarwal[m][m] has quit [charon.oftc.net helix.oftc.net]
pedrohlc[m] has quit [charon.oftc.net helix.oftc.net]
gallo[m] has quit [charon.oftc.net helix.oftc.net]
cwfitzgerald[m] has quit [charon.oftc.net helix.oftc.net]
siddh has quit [charon.oftc.net helix.oftc.net]
ofirbitt[m] has quit [charon.oftc.net helix.oftc.net]
marmarek[m] has quit [charon.oftc.net helix.oftc.net]
daniliberman[m] has quit [charon.oftc.net helix.oftc.net]
tak2hu[m] has quit [charon.oftc.net helix.oftc.net]
ram15[m] has quit [charon.oftc.net helix.oftc.net]
dcbaker has quit [charon.oftc.net helix.oftc.net]
Wallbraker has quit [charon.oftc.net helix.oftc.net]
Mis012[m] has quit [charon.oftc.net helix.oftc.net]
bubblethink[m] has quit [charon.oftc.net helix.oftc.net]
koki23[m] has quit [charon.oftc.net helix.oftc.net]
FL4SHK[m] has quit [charon.oftc.net helix.oftc.net]
vdavid003[m] has quit [charon.oftc.net helix.oftc.net]
aura[m] has quit [charon.oftc.net helix.oftc.net]
kusma has quit [charon.oftc.net helix.oftc.net]
Adrinael has joined #dri-devel
QiuWenbo[m] has quit [charon.oftc.net helix.oftc.net]
K0bin[m] has quit [charon.oftc.net helix.oftc.net]
PiGLDN[m] has quit [charon.oftc.net helix.oftc.net]
AlexisHernndezGuzmn[m] has quit [charon.oftc.net helix.oftc.net]
enick_416 has quit [charon.oftc.net helix.oftc.net]
swick[m] has quit [charon.oftc.net helix.oftc.net]
sre has quit [charon.oftc.net helix.oftc.net]
libv has quit [charon.oftc.net helix.oftc.net]
Namarrgon has quit [charon.oftc.net helix.oftc.net]
samuelig has quit [charon.oftc.net helix.oftc.net]
aissen has quit [charon.oftc.net helix.oftc.net]
moxie has quit [charon.oftc.net helix.oftc.net]
Guest360 has quit [charon.oftc.net helix.oftc.net]
bnieuwenhuizen has quit [charon.oftc.net helix.oftc.net]
shadeslayer has quit [charon.oftc.net helix.oftc.net]
tjaalton has quit [charon.oftc.net helix.oftc.net]
lemonzest has joined #dri-devel
krei-se has joined #dri-devel
moxie has joined #dri-devel
Adrinael is now known as Guest1074
Omax has joined #dri-devel
tarceri_ has quit [Read error: Connection reset by peer]
nashpa is now known as dliviu
heat has joined #dri-devel
alarumbe has joined #dri-devel
robmur01 has joined #dri-devel
danylo has joined #dri-devel
minecrell has joined #dri-devel
mripard has joined #dri-devel
rasterman has joined #dri-devel
qflex has joined #dri-devel
DavidHeidelberg has joined #dri-devel
cr0n has joined #dri-devel
Stary has joined #dri-devel
gallo[m] has joined #dri-devel
sravn has joined #dri-devel
paulk has joined #dri-devel
mwalle has joined #dri-devel
q66 has joined #dri-devel
cwfitzgerald[m] has joined #dri-devel
siddh has joined #dri-devel
daniliberman[m] has joined #dri-devel
ofirbitt[m] has joined #dri-devel
marmarek[m] has joined #dri-devel
ram15[m] has joined #dri-devel
dcbaker has joined #dri-devel
KunalAgarwal[m][m] has joined #dri-devel
pedrohlc[m] has joined #dri-devel
tak2hu[m] has joined #dri-devel
Wallbraker has joined #dri-devel
bubblethink[m] has joined #dri-devel
koki23[m] has joined #dri-devel
FL4SHK[m] has joined #dri-devel
aura[m] has joined #dri-devel
vdavid003[m] has joined #dri-devel
K0bin[m] has joined #dri-devel
QiuWenbo[m] has joined #dri-devel
AlexisHernndezGuzmn[m] has joined #dri-devel
PiGLDN[m] has joined #dri-devel
kusma has joined #dri-devel
enick_416 has joined #dri-devel
swick[m] has joined #dri-devel
Namarrgon has joined #dri-devel
sre has joined #dri-devel
libv has joined #dri-devel
samuelig has joined #dri-devel
aissen has joined #dri-devel
bnieuwenhuizen has joined #dri-devel
tjaalton has joined #dri-devel
shadeslayer has joined #dri-devel
Mis012[m] has joined #dri-devel
vyivel has joined #dri-devel
Namarrgon has quit [Ping timeout: 532 seconds]
pinchartl has joined #dri-devel
a-865 has joined #dri-devel
jadahl has joined #dri-devel
minecrell2 has joined #dri-devel
sre5 has joined #dri-devel
vyivel_ has joined #dri-devel
vyivel_ has quit [Remote host closed the connection]
vyivel_ has joined #dri-devel
mripard_ has joined #dri-devel
vyivel has quit [Read error: Connection reset by peer]
sre has quit [Read error: Connection reset by peer]
danylo has quit [Read error: Connection reset by peer]
danylo has joined #dri-devel
vyivel_ has quit [Remote host closed the connection]
vyivel has joined #dri-devel
glennk has joined #dri-devel
Namarrgon has joined #dri-devel
heat is now known as Guest1104
heat has joined #dri-devel
ungeskriptet is now known as Guest1106
ungeskriptet has joined #dri-devel
minecrell has quit [Ping timeout: 480 seconds]
mripard has quit [Ping timeout: 480 seconds]
Guest1104 has quit [Ping timeout: 480 seconds]
Guest1106 has quit [Ping timeout: 480 seconds]
ndufresne1 is now known as ndufresne
Guest1074 is now known as Adrinael
<sima>
bbrezillon, drm-misc-next is always open
<sima>
and yeah I think it'd fit into drm-misc, since usually after the initial drop activity tends to quiet down
<sima>
maybe get some acks from drm-misc maintainers
<sima>
wrt 6.9, the freeze already happened, so if you absolutely want to get it in, do a dedicated pull just for that, but with the MAINTAINERS entry pointing at the drm-misc git repo
<sima>
would still need to happen sooner than later, so that you can push bugfixes through drm-misc-next-fixes
<sima>
or drm-misc maintainers just ack that you drop the entire thing into drm-misc-next-fixes
<sima>
bbrezillon, for your actual question, the last drm-misc-next pr for 6.9 just happened last week, and I just merged it into drm-next today
<sima>
around -rc6 is the usual cutoff
kts has quit [Ping timeout: 480 seconds]
<bbrezillon>
sima: I don't necessarily need it in 6.9
junaid has joined #dri-devel
<bbrezillon>
just wanted to have it in linux-next for a few weeks, so that's perfect timing in the end
DodoGTA has joined #dri-devel
<sima>
bbrezillon, so drm-misc-next is not in linux-next during the feature freeze, so from roughly -rc6 to -rc1
<sima>
but you can still just land it
<bbrezillon>
that's fine, as long as it's in linux-next when -rc1 is out
<bbrezillon>
mripard_, mind giving me a ack on v5?
<abhinav__>
mripard_ hi, for msm, we need some changes which went into drm-misc for a feature which we planned to land in 6.9 ... would it be possible to generate another tag so that we can pull in that into our tree and base our changes on that ... these changes were merged after the last tag on 02-22 .... OR by any change will there be another PR from
<abhinav__>
drm-misc?
<alyssa>
bbrezillon: woohoo!
<bbrezillon>
hehe
<bbrezillon>
finally...
<airlied>
bbrezillon: are you aiming for 6.10?
<bbrezillon>
yes
<airlied>
ah cool
qflex has quit [Ping timeout: 480 seconds]
rasterman has quit [Quit: Gettin' stinky!]
warpme has quit []
simon-perretta-img has quit [Ping timeout: 480 seconds]
simon-perretta-img has joined #dri-devel
warpme has joined #dri-devel
KetilJohnsen has quit [Ping timeout: 480 seconds]
mbrost has joined #dri-devel
iive has joined #dri-devel
qflex has joined #dri-devel
qflex has quit [Ping timeout: 480 seconds]
simon-perretta-img has quit [Ping timeout: 480 seconds]
simon-perretta-img has joined #dri-devel
tursulin has quit [Ping timeout: 480 seconds]
qflex has joined #dri-devel
jhli has joined #dri-devel
mbrost has quit [Ping timeout: 480 seconds]
Duke`` has quit [Ping timeout: 480 seconds]
qflex has quit [Ping timeout: 480 seconds]
sima has quit [Ping timeout: 480 seconds]
qflex has joined #dri-devel
mbrost has joined #dri-devel
qflex has quit [Ping timeout: 480 seconds]
junaid has quit [Remote host closed the connection]
qflex has joined #dri-devel
mbrost has quit [Remote host closed the connection]
mbrost has joined #dri-devel
krushia has quit [Quit: Konversation terminated!]
qflex has quit [Ping timeout: 480 seconds]
sarthakbhatt has joined #dri-devel
jkrzyszt_ has quit [Ping timeout: 480 seconds]
qflex has joined #dri-devel
hansg has quit [Remote host closed the connection]
warpme has quit []
qflex has quit [Ping timeout: 480 seconds]
qflex has joined #dri-devel
qflex has quit [Ping timeout: 480 seconds]
mbrost has quit [Remote host closed the connection]
mbrost has joined #dri-devel
qflex has joined #dri-devel
krushia has joined #dri-devel
mbrost has quit [Remote host closed the connection]
mbrost has joined #dri-devel
qflex has quit [Ping timeout: 480 seconds]
iive has quit [Read error: Connection reset by peer]
Marcand has joined #dri-devel
mvlad has quit [Remote host closed the connection]
qflex has joined #dri-devel
iive has joined #dri-devel
qflex has quit [Ping timeout: 480 seconds]
qflex has joined #dri-devel
qflex has quit [Ping timeout: 480 seconds]
qflex has joined #dri-devel
Haaninjo has quit [Quit: Ex-Chat]
Marcand has quit [Ping timeout: 480 seconds]
qflex has quit [Ping timeout: 480 seconds]
qflex has joined #dri-devel
qflex has quit [Ping timeout: 480 seconds]
mbrost has quit [Ping timeout: 480 seconds]
qflex has joined #dri-devel
iive has quit [Quit: They came for me...]
rz has quit [Ping timeout: 480 seconds]
rz has joined #dri-devel
qflex has quit [Ping timeout: 480 seconds]
letsgofrom has joined #dri-devel
<letsgofrom>
karolherbst: you take steroids again i hear, we released a new product that you could consume after your dream in anal ways, cause you have not gone past the anal stage in your life, normally it happens after 3years old according to freud, but does not look you made it through, you are still a hero, some might consider you even a big gun, roll your german rrrrr's it's fair to say you are an idiot like 50 line java trace you used to read,
<letsgofrom>
puppet.
<letsgofrom>
next century you even might get to opencl 2.1
<letsgofrom>
at your current speed of solving things