alyssa changed the topic of #panfrost to: Panfrost - FLOSS Mali Midgard & Bifrost - - Logs - <daniels> avoiding X is a huge feature
stikonas has quit [Remote host closed the connection]
jernej has quit [Quit: Free ZNC ~ Powered by LunarBNC:]
jernej has joined #panfrost
<alyssa> HdkR: Incidentally I have a patch on the list for that, I think?
<alyssa> What's the ettiquette on a list for expressing that you *don't* want a patch, you know, without going on a profanity-laced rant or anything?
<HdkR> NAK plus an explanation as to why you don't want it
<hanetzer> a linus-like rant? :P
<HdkR> I didn't realize alyssa Was commenting on something Nvidia related
<alyssa> HdkR: But it's always Nvidia relaetd!
chewitt has joined #panfrost
<alyssa> Okay woah why are we recompiling 460 files all of a sudden
<alyssa> Oh, it's because apt decided to upgrade behind my back. *blinks*
<alyssa> Did I accidentally install Windows when I wasn't paying attention?
<HdkR> destroy unattended-upgrades package
<alyssa> Why on earth does early enabling of AFBC for colour buffers not work, but late enabling is fine
_whitelogger has joined #panfrost
_whitelogger has joined #panfrost
_whitelogger has joined #panfrost
chewitt has quit [Read error: Connection reset by peer]
chewitt has joined #panfrost
chewitt has quit [Read error: Connection reset by peer]
chewitt has joined #panfrost
chewitt has quit [Read error: Connection reset by peer]
_whitelogger has joined #panfrost
<alyssa> +afbc_size = ALIGN(n_superblocks * AFBC_HEADER_SIZE, 128);
<alyssa> I.e. note to self, we're supposed to be 128-aligning the metadata_size (I guess they call it the header)
ric96 has quit [*.net *.split]
Elpaulo has quit [Quit: Elpaulo]
stikonas has joined #panfrost
* hanetzer winks with both eys
raster has joined #panfrost
ric96 has joined #panfrost
_whitelogger has joined #panfrost
_whitelogger has joined #panfrost
stikonas has quit [Remote host closed the connection]
raster has quit [Remote host closed the connection]
<alyssa> ...How do I download patches off an ML...?
<alyssa> mutt
<ente> patch(1) strips anything before --- filename
<ente> so if you have the mails already, you can just use git apply or patch(1)?
<alyssa> _download_
<ente> if you don't, mailman sometimes has mailing list archives available in mbox format
<ente> figured because you said mutt you already have the mails, sorry
<ente> in mlmmj you can send a request for an individual mail to and it resends the message to you. might be possible with majordomo or mailman too.
<ente> actually I've been wondering myself how I can mirror mailing list archives, since gmane/ are going out of order one after another
<ente> easiest way imo: get the list archive forwarded by someone who has the entire list :)
pH5 has joined #panfrost
<ente> takes some experimenting every time ~.~
Elpaulo has joined #panfrost
Elpaulo has quit [Client Quit]
Elpaulo has joined #panfrost
BenG has joined #panfrost
BenG83 has quit [Ping timeout: 250 seconds]
stikonas has joined #panfrost
<alyssa> tomeu: You know, I've been trying to push your patches all morning... I think this is a sign nondrm support should be dropped ASAP :P
<alyssa> Upon second thought, I'm just squashing the series.
<alyssa> tomeu: I squashed 2-8 to preserve bisectability without losing my sanity, but it's all pushed. nice!
BenG83 has joined #panfrost
<ezequielg> alyssa: if patches are in patchwork, I strongly suggest you use git-pw.
Elpaulo has quit [Quit: Elpaulo]
<alyssa> ezequielg: That requires a patchwork account
<alyssa> No?
BenG83 has quit [Client Quit]
<ezequielg> it might, i guess.
<ezequielg> not too problematic. and hugely useful if you start picking patches oftenly.
<ezequielg> specially with new patchwork, which allows to pick series.
BenG83 has joined #panfrost
<alyssa> Also kdJSGsjafgdashkj
<alyssa> Why is git-am such a pain
<alyssa> This is not okay
<ezequielg> pain how?
<ezequielg> i think most developers (including myself) forget to state clearly where patches apply. without a clear base, applying patches is a pain, git-am or not.
<alyssa> I don't get how to deal with conflicts
<alyssa> And now I just tried to merge and that worked but now I have a merge commit and mesa says that's strictly wrong
<alyssa> I have written 0 code today and all I managed to do is fight with git for hours
<ezequielg> git am (conflicts) then git apply --reject, you fix manually and add, and then git am --cont.
<ezequielg> painful but it is what it is
<alyssa> ?
<ezequielg> that is how you deal with conflicts: git am and then git apply --reject
<ezequielg> to get rid of a merge commit, git rebase and then deal again with the same conflicts.
<ezequielg> painful, yes, welcome to our daily world.
<alyssa> What the heck I thought I /quit'd this
<alyssa> I guess I need to wack the bouncer
<alyssa> Regardless, I will not be solving this. Somebody else can merge my patches on the mailing list. I don't want to play maintaininer; I just want to write code. That's not too much to ask for, though then again, but it is.
alyssa has quit [Quit: ZNC 1.7.2+deb1 -]
pH5 has quit [Ping timeout: 244 seconds]
pH5 has joined #panfrost
pH5 has quit [Quit: -_-]
raster has joined #panfrost
indy has quit [Quit: ZNC -]
indy has joined #panfrost
raster has quit [Remote host closed the connection]
BenG has quit [Quit: Leaving]